Quote from: sottwell at Aug 05, 2013, 01:03 PMWhen you export the old_ tables, you'll have a text file. Simply open it in a text editor and do a search-and-replace for replacing all instances of old_ with new_, then use the modified .sql file for the import.
Thanks Sottwell. Will try that one. Got a clean 2.2.8 up and running.
I am still curious about what went wrong and why a cannot upgrade the my revo site. To summarize - these things went well or are ok.
- file permissions are ok
- config.inc.php paths are ok
In a new prefix in the database i did a:
- clean install of 2.2.4 and it went fine
- upgrade of 2.2.4 to 2.2.8 and it went fine
But something is wrong with the revo site. I tried reuploading 2.2.4 and 2.2.5 but as soon as i hit the next button in the upgrade process i get the 500 error.
My goal is not to tamper to much with the sql file , because the old evo site is running there and is public.
If i did a find and replace, i would end up with duplicates. If i replace _new with _old i would have a database with 2 times the prefix old_ and then i would have to figure out to delete the duplicates.
So i guess my question is: Where else can i look for something wrong, to get the setup/upgrade process up and running ? What could make it stop right after I hit the next button:
"The website encountered an error while retrieving
http://mydomain/setup/index.php?action=options. It may be down for maintenance or configured incorrectly."