|
JohnB
|
November 20, 2018 at 9:28 pm
Tried to do update of plugin for Promotions (??)
Appeared to fail as it threw up an error msg. (didn’t save it for you 🙁 )
Now when a person tries to register and goes to first screen of checkout, they get this msg.
An error has occurred:
WordPress database error: [Tablespace for table ‘{database}.{prefix}_esp_promotion_object‘ exists. Please DISCARD the tablespace before IMPORT.]
CREATE TABLE {prefix}_esp_promotion_object ( POB_ID int(10) unsigned NOT NULL AUTO_INCREMENT, PRO_ID int(10) unsigned NOT NULL, OBJ_ID bigint(20) unsigned NOT NULL, POB_type varchar(45) NULL, POB_used smallint(6) NULL, PRIMARY KEY (POB_ID), KEY PRO_ID (PRO_ID), KEY OBJ_ID (OBJ_ID) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci
Stack Trace:#0 /wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(671): EventEspresso\core\services\database\TableManager->createTable(‘esp_promotion_o…’, ‘POB_ID int(10) …’, ‘InnoDB’) #1 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(647): EEH_Activation::create_table(‘esp_promotion_o…’, ‘POB_ID int(10) …’, ‘ENGINE=InnoDB’, false) #2 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(553): EE_Data_Migration_Script_Base->_create_table_and_catch_errors(‘esp_promotion_o…’,
-
This topic was modified 6 years ago by
 Tony.
|
|
Tony
|
November 21, 2018 at 5:27 am
Hi John,
Usually, your host will give you access to some form of error reporting on the control panel they use, could you check that and see if the error shows up in here?
The error you are getting is something your host will need to fix as there’s an issue with the database, the promotions add-on can’t read the promotions table (assuming there already was one as you mentioned you are updating the plugin) and when trying to re-create the tablespace already exists.
Did you already have promotions created in the system?
Before moving forward I recommend creating a full database backup if you don’t already have one (although hopefully you do).
|
|
JohnB
|
November 21, 2018 at 3:41 pm
Tony,
Yes, the web man has found the problem and it appears a duplicate or temporary table or something like that had been created but not deleted at some point.
All sorted and working now.
Thank you.
|
|
Tony
|
November 22, 2018 at 3:57 am
Thanks for the update, I’m glad you got it fixed 🙂
|
