Upgrade from 2.4.0 to 3.5.1 Fails
How Do I?
I attempted to upgrade my site following the instructions here: https://docs.expressionengine.com/latest/installation/upgrade_from_2.x.html
When I got to step 5 and clicked the upgrade button, I saw it upgrading through the various versions, then suddenly threw this error:
Exception Caught
SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘exp_rte_toolsets’ already exists:
CREATE TABLE exp_rte_toolsets ( toolset_id int(10) UNSIGNED AUTO_INCREMENT, member_id int(10) DEFAULT ‘0’, name varchar(100), tools text, enabled char(1) DEFAULT ‘y’, PRIMARY KEY toolset_id (toolset_id), KEY member_id (member_id), KEY enabled (enabled) ) DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE=InnoDB;
mysqli_connection.php:122
I had to back out of the upgrade. Can anyone tell me what went wrong, and how to make it go right?
A question and a suggestion:
- do you know or remember which update it displayed when it failed?
- I would update to the latest EE 2.x first before trying to update to EE 3.
Thank you so much, TJ Draper. I discovered that this particular error was the result of this being my second attempt to upgrade, thus the tables it was trying to create were already present. Next time, I dropped all tables before restoring the backup, and this allowed me to avoid this error.
I’m not out of the woods yet. I had to comment out some code in the new EE3 ee/legacy/libraries/Typography.php file to eliminate a “Fatal error: Using $this when not in object context” error, and EE3 does not have a mail list manager where fixing a mail list manager error was the whole reason I was told to upgrade to EE3, but as far as this particular error is concerned, I’d say it’s resolved.
I usually try smaller incremental upgrades when getting errors like these - especially when going from EE v2 to v3.