• To start off- this isn’t about plugins breaking due to the upgrade. I just upgraded from 1.5 to 2.0 and things are going well, but when I went to install the Tiger plugin, well, it didn’t work. When I added the folder to my plugins directory it should have shown up in my plugins page on the admin section, but it didn’t. It’s like WordPress is reporting that it couldn’t find any reference to the plugin.

    I thought it was a problem just with that particular plugin, but it doesn’t appear to be so. I went into some of the stock plugins I had and changed the header- added some test words to the description, to the title, that type of thing. WordPress didn’t reflect those changes in the plugin section- it’s like I didn’t change anything at all. I also browsed around for a couple of plugins that I knew worked for 2.0 and saved them in my plugins folder but none of those worked either- once again, they didn’t show up in my plugins page. It’s not about being able to activate or deactive the plugin- it doesn’t even show me the option since the plugin doesn’t show on the page.

    Any help would really be appreciated. Everything else seems to be working fine so far save for the plugins. I’ve tried everything I can think of- I’ve recursively set permissions of 777 on my whole wp-content folder, so I wouldn’t think it would be a matter of permissions. Thanks for your time, I appreciate it.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Are you sure that you’re plugin directory is the one that WordPress is using? I’ve just checked this under 2.0 and the changes to the plugin header appeared immediatly.

    Thread Starter lo0ol

    (@lo0ol)

    Wow, I’m kind of embarassed to type this, heh. I was using the wrong plugin directory. I could have sworn… oh well. Things are working now. It’s actually a fairly legitimate mistake- in upgrading I had moved the old 1.5 directory up a step in my file hierarchy outside of my publicly-accessible directory and then I think I lost my (sometimes unreliable) wireless internet connection, and when I ssh’ed in again I didn’t go that one step further into the proper plugins directory. Dumb mistake that I probably should have caught on to, but I guess it’s not too unforseeable. Anyway… thanks a lot, jaredquinn, for setting me on track faster! ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Upgrade to 2.0: Plugins Don’t Work’ is closed to new replies.