Strange upgrade problem...

Greetings all.

I just finished upgrading from 1.5.1 to 2.0.2. I followed the upgrade instructions precisely.

At first, I got an "Website is down until the upgrade is complete" (or something like that) on both the front and back ends, and was never directed to an "Upgrade your database" message. Then I tried to his the /admin/plugins directory and up popped the upgrade screen. I clicked on "upgrade" and suddenly everything worked.

I started poking around my site--everything looked pretty good. All my data was there, the "Thanks, Roy" theme looked mostly okay, and I was even able to edit and delete a few items.

Then I went to the plugins page. I was informed that COiNS needed updating, so I did it--no problem.

Then I clicked on the "Activate" button for the "Collection Tree" plugin, which I had copied over from my previous installation and which now appeared in the 2.0.2 site. Bad move. The site crashed and says the site may be down for maintenance or configured incorrectly ("HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.").

Now, neither the front nor back end come up at all. It seems odd that trying to Activate the Collection Tree plugin would take down the entire site.

Can anyone give me some suggestions for getting back up and running?

Thanks in Advance,

ken.

There's a 2.0 compatible version of the CollectionTree plugin.

Replacing the old plugin files with the new ones should get you back up and running (you can just delete the old CollectionTree folder and replace it with the new one).

Many thanks, John!

For others who might run into this:

I went through the list online of all the plugins with 2.0 compatability, unzipped and uploaded the (sometimes double embedded) directories after renaming the old plugin directories, and voila: the site was back up.

All I had to do was go through the new plugin and click the "upgrade" button that now appeared on the plugins page of my site and I was back up.

Cheers!

ken.