It seems its not only myself experiencing problems at step 11 of the 2.0.x to 3.2 upgrade, could it possibly be a bug? I receive the following error:
A fatal MySQL error was encountered.
Query: UPDATE efictionfanfiction_in_series SET confirmed = 1
Error: (1146) Table 'halliwell.efictionfanfiction_in_series' doesn't exist
If this is not a bug...let me know 😳
I got this while upgrading from 2.0.7 to 3.2. It is a typo in install/upgrade20.php, line 536. Change fanfiction_in_series to fanfiction_inseries.
Yup, thanks rvbhute that seems to be exactly the problem, now the only problem is step 12:
A fatal MySQL error was encountered.
Query: ALTER TABLE `efictionfanfiction_reviews` CHANGE `sid` `item` INT( 11 ) NOT NULL DEFAULT '0'
Error: (1054) Unknown column 'sid' in 'efictionfanfiction_reviews'
I think you should start the upgrade process from first step if you run into a problem - that means reloading the SQL backup of efiction 2.0.x again. I had to do it two times - once for chmodding config.php and then for the fanfiction_in_series error.
On the other hand, maybe you can check the table in phpMyAdmin. If you see the field item already in place instead of sid (maybe becuase of previous upgrade attempts), simply change the url to say step=13 and go ahead! I tried that one time; though I came back later to fix the typo.
Unfortunately I don't have a SQL backup, so it appears I'm stuck..until I can figure out how to manually update the tables. I seemed to run through most of the steps but I guess I'm stuck with this mess at the moment.
Got the same problem, it's a typo
file: /install/upgrade20.php
line: 536
dbquery("UPDATE ".$tableprefix."fanfiction_in_series SET confirmed = 1");
change it to:
dbquery("UPDATE ".$tableprefix."fanfiction_inseries SET confirmed = 1");
BUT, I don't know if it was a typo when the script was creating the table... 🙄
If it was, all you need to do is change the table's name in the DB
DO NOT CHANGE THE TABLE NAME IN THE DB! It's a typo in the update script. It's been reported in another thread. Senji, do not casually tell people to alter their tables!
So Tammy, then is there any sort of fix that can be applied, since I have an upgrade in suspended animation at the moment, and unfortunately do not have an SQL backup.
Edit the update find "in_series" and replace it with "inseries"
