Wolverine

This was attributable to pilot error during the upgrade process on my part. I thought I’d followed the sequence correctly but dicovered that was not the case, I’d misread something important :\. I apologize for the confusion.

I’ve reverted to 2.0 and after tidying things up will perform the upgrade *properly*. Thanks, OtherMichael.

I appreciate your time and input, however there is no need to be rude; this is new territory for me and I am trying to learn.

As stated in my second post, I am able to deactivate my plugins from the Plugin Management screen (and I do have copies of them at the ready).

I also did deactivate all plugins prior to performing the upgrade — however in reviewing the instructions I see where I have likely made a different mistake along the way.

Apologies for the incorrect terminology, this is a learning experience for me. (I had associated that function with the originating Flickr plugin.)

I’m at a loss to understand why or how the problem surfaced, let alone how to go about fixing it. What in the upgrade process could have caused the redundancy when I’ve not changed anything else?

My question is: what is the “Cannot redeclare [plugin name]” error indicative of, and how do I go about fixing it?

The plugins show up in the Plugin Management section of the dashboard, and I’m able to activate or deactivate them there (I’m familiar with how to remove them entirely). The errors occur when I try to access a given plugin’s options individually.

I get the impression that the problem I’m experiencing isn’t due to version incompatibility, but something else…