Thread Starter
brentk
(@brentk)
UPDATE: Activating and deactivating plugins has the same problem. I get the fade-out banner that says a plugin has been deactivated, but its activation status does not change. Activating a plugin produces the “Plugin activated” message, but it doesn’t get activated. Any guesses as to what is misconfigured?
Same problem here, and though I offered him help with file permissions, his response indicates maybe it was something with user permissions…
So check both. :
File permissions: http://codex.wordpress.org/Changing_File_Permissions
And then if you’re not logged in as admin, log in and check your user permissions.
Let me know which thing it actually was if you figure it out! 🙂
Thread Starter
brentk
(@brentk)
Problem solved!
I recently installed the VideoBlogger plugin. It includes the file “upgrade-functions.php”, which contains a bug.
At the top of upgrade-functions.php are two require_once statements:
require_once(ABSPATH . ‘/wp-admin/admin-functions.php’);
require_once(ABSPATH . ‘/wp-admin/upgrade-schema.php’);
This will include “..//wp-admin/admin-functions.php”. Since admin-functions.php already gets included somewhere else, but as “../wp-admin/admin-functions.php”, PHP will die due to redeclared functions.
These lines should be changed to:
require_once(ABSPATH . ‘wp-admin/admin-functions.php’);
require_once(ABSPATH . ‘wp-admin/upgrade-schema.php’);
Cheers,
Brent
Thread Starter
brentk
(@brentk)
Correction. That fixed the videoblogger setup area, but nothing else. I’m continuing to investigate.
wp-includes/cache.php produces an error on line 270:
$stat = stat(ABSPATH.’wp-content’);
Produces a “no such file or directory” error, although wp-content does exist. If I replace ABSPATH with the full system path to wp-content, this error message disappears, but plugin activation and theme switching is still broken.
Thread Starter
brentk
(@brentk)
OK, this time its really solved 🙂
The problem was that the wp-content directory was, at some point, writable by the apache user. When this happens, WordPress creates wp-content/cache. If that directory exists, the result is that you can’t switch themes or activate/deactivate plugins. I removed that directory, and everything works (wp-content is not writable by the webserver now).
This is probably a WordPress bug…
Brent
I don’t think that’s entirely it. My multiple installations of WP are on Apache, I have the cache folder, wp-content is set to 755, and I’m able to switch themes & activate and deactivate plugins randomly as needed… (and have never had an issue with it).
So maybe it was something that was wrongly written to the cache? I don’t know, I’m not quite that technical. 🙂
