I tried to upgrade from 2.0.7 several months ago, but I had problems with the upgrade not pulling any of the existing data from the existing configs or settings. I'm prepping to make another go at this, with the stories and the database backed up. I want to make sure that I'm doing this right, so I have some questions before I actually do this.
1. I upload the 3.3.1 files over the 2.0.7 files, chmod the config.php to 666, and run the upgrade script, yes? Is there anything vital that I need to do in here before I run the script, to make sure it gets the necessary existing information? Last time, it somehow dumped all the information from the config file and couldn't find the database information.
2. If I wanted to perform a clean install of 3.3.1 in a new directory, how would I go about merging the backed up database information into the new tables? Is that possible, or would I have to manually enter it for my 440+ members and almost 200 stories?
3. If my current skin is based on the default skin that came with 2.0.7, will it be affected? It's a simple site and I'm pretty much just upgrading for the co-author function.
ETA: I tried the clean install and the database merge, but I wasn't able to import the old information. I'm going to try the overwrite, since I have everything backed up, anyway.
Dana
I'm about ready to cry. Everything was going along great and then . . . my host's server went down. My server came back up, but now I can't get back into the mySQL panel to fix this. Looks like I have to reupload everything and start over. Again.
ETA The Sequel: Okay, my upgrade has been a comedy of errors. This time, my browser experienced an error and crashed in the middle. *headdesk* I think I'm being told not to upgrade.
Back to my original question #2: *is* there a way to merge an old table into a new one without editing it manually for 500 members and 200+ stories? Because I can install 3.3.1 without a single hitch if it's a clean install, but upgrading keeps having problems (and different ones every single kriffing time!).
Alternatively, is there a way to hack 2.0.7 to allow co-authors?
Oh, my. I don't blame you for being discouraged, but you should probably try again. It sounds like most of the issues are not related to efic...
1. I upload the 3.3.1 files over the 2.0.7 files, chmod the config.php to 666, and run the upgrade script, yes? Is there anything vital that I need to do in here before I run the script, to make sure it gets the necessary existing information? Last time, it somehow dumped all the information from the config file and couldn't find the database information.
Yes, that's right. I'm not sure what would have caused that. The config file for a different purpose so maybe that was it. If it happans again, you can manually edit the config file with the necessary user information. Compare it with your dbconfig file from 2.0.
2. If I wanted to perform a clean install of 3.3.1 in a new directory, how would I go about merging the backed up database information into the new tables? Is that possible, or would I have to manually enter it for my 440+ members and almost 200 stories?
You can't do that. The database structure has changed dramatically from 2.0 to 3.0 and updating the database to the new structure is part of what the upgrade script does.
3. If my current skin is based on the default skin that came with 2.0.7, will it be affected? It's a simple site and I'm pretty much just upgrading for the co-author function.
There will probably be a few changes to make to your skins, but it is fairly easy to update them.
Alternatively, is there a way to hack 2.0.7 to allow co-authors?
No.
Thanks for answering my questions. You confirmed what I was afraid of. *sigh*
The ones I mentioned before were attempts one, three, and four. I did have an attempt yesterday where I ran into the same issue listed here, and when I followed the directions, it stalled me in step four and I got another error concerning the "collate latin1_general_ci", after I removed the references to it in the upgrade20.php. So it produced the same error, just at a later step, while it was doing something with the panels. It also said something at that point about the site key being wrong, which is why I started over with attempt three (the one where the host server crashed on me).
I have to admit I'm at a loss about this. I didn't add any mods; all I changed was the skin on 2.0.7. So I see these mentions of flawless upgrades and have to scratch my head, because it would seem I'm doing something wrong, I just can't for the life of me figure it out. I've tried to upgrade six times now, and aside from some unfortunate server and browser problems, I run into a different error every single time.
