Warnings in Plugin Management

buzz1680
(@buzz1680)

21 years, 1 month ago

Hi all,

I’m having trouble with my Plugin Management. I have installed a couple of plugins into the wp-content/plugins/ folder, however when I go to the Plugin Management section, I get a whole list of warnings, followed by the following note: “couldn’t open plugins directory or there are no plugins available.”

The warnings are:

Warning: file, mail, opendir, readdir, closedir() has been disabled for security reasons in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: implode(): Bad arguments. in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: file, mail, opendir, readdir, closedir() has been disabled for security reasons in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: implode(): Bad arguments. in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: file, mail, opendir, readdir, closedir() has been disabled for security reasons in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: implode(): Bad arguments. in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: file, mail, opendir, readdir, closedir() has been disabled for security reasons in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: implode(): Bad arguments. in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: file, mail, opendir, readdir, closedir() has been disabled for security reasons in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

Warning: implode(): Bad arguments. in d:\hosting\buzz1680\blog\wp-admin\admin-functions.php on line 932

I don’t understand this, as I really haven’t changed anything since installation. Does anyone know what I can do to fix this problem?

Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)

Mark (podz)
(@podz)

21 years, 1 month ago

“Warning: file, mail, opendir, readdir, closedir() has been disabled for security reasons “

Hosting decisions – email them and ask them why they are restricting in this way ?

Thread Starter buzz1680
(@buzz1680)

21 years, 1 month ago

OK, will do. Thanks for that.

Cypher
(@cypher)

21 years, 1 month ago

Wow, very restrictive host. Won’t even allow “mail”?? The others can be potentially abused by bad programs.

Regards

davidchait
(@davidchait)

21 years, 1 month ago

file is really the same as get_file_contents or an fopen/fread/fclose set. mail is just nuts, but I use a third-party library at this point, and WP should too, that uses socket code. the dir functions are used by WP in order to auto-generate lists of things in a folder (like plugins!), and I guess could be abused, but geez.

Seems like a host to move away from, if they need to be that restrictive in order to prevent hacks.

Sounds like maybe the Codex should have a Security section, that describes why certain php/apache features SHOULD be disabled, and arguments against why others shouldn’t…

-d

ColdForged
(@coldforged)

21 years, 1 month ago

Krikey, that is limited. Next thing you know we’ll see:

Warning: echo, print has been disabled for security reasons.

Thread Starter buzz1680
(@buzz1680)

21 years, 1 month ago

I know…it’s very frustrating! I’m using Go Daddy, which is a widely used host, so I don’t know what’s wrong, and furthermore when I sent an email to support, they said that they can’t help without sending it to one of their “experts”, and this ‘may’ incur a fee! Arrrggghhh!!

Is there anything you guys can suggest? What questions should I ask them specifically, as I am an absolute newbie to the weblog scene, and my knowledge of php is zero. Perhaps they misunderstood my problem as I explained it to them…hmmm, though they should be experts, heh?

Thanks!