PLUGINS DON’T WOFK

wait as not all plugins are compatible with WP2.5 yet.

I think the plug-in situation is becoming quite a mess. There should be some mechanism to turn off plugins that aren’t compatible with upgrades in some type of automated way. To have to go through all your plugins and test each one to find the culprit is an archaic process that is time consuming and problematic. We need a better solution.

In addition, there needs to be a way to activate multiple plugins at once, instead of individually. If you can deactivate all plugins at once, why can’t you activate them all at once as well?

I’d like to see on the WordPress Extend page some type of more obvious flag for a plugin that has been revised to work for 2.5 and another flag for plugins that are offered but not upgraded yet.

There’s got to be a better way. This is becoming a little unruly.

@tonyzeoli nice suggestion. I am also waiting/hoping for the activating/deactivating multiple features at once.

I would just like to be able to use the options on the plugins to configure them to work.

When I click on a configuration option, I get a 404 page not found return.

And no one seems to have a solution or a fix

@gamerz Thanks. I did see that the Plug-Ins section has version numbers related to each Plug-in, but the plug-in authors don’t seem to be keeping up with the latest changes for the WordPress system.

In that case, once WordPress is updated, a plug in may cause a 500 error, which is happening frequently on my blog.

I’m not sure if this is possible, but if someone could build a tool to show you which plug ins were breaking your blog, that would be great.

It’s great that the Plug In system shows me when I need to update a Plug In, but it should also tell me when one is not working right.