|
William Tozzo
|
June 26, 2015 at 4:40 pm
Hi Guys:
It seemed to install well and WP said it was successful. But plugin will not activate?
What gives?
Bill
|
|
Garth
|
June 27, 2015 at 10:23 pm
Hi William,
How are you today?
What version of Event Espresso are you running? I think the Promotions beta requires 4.8.
Is there a error message?
|
|
William Tozzo
|
June 29, 2015 at 9:50 am
Hi Garth:
I’m running 4.7 because 4.8 is in beta. But the promo plugin says at least 4.7. If you’re sure I’ll install 4.8. Let me know.
Bill
|
|
Josh
|
June 29, 2015 at 10:04 am
Hi Bill,
The latest version of the promo plugin beta that you can download from the pre-release channel (it’s also a beta) will only activate with Event Espresso 4.8 beta.
|
|
William Tozzo
|
June 30, 2015 at 3:56 am
Ok Josh. I’ll give it a shot now andget back to you guys.
|
|
William Tozzo
|
July 1, 2015 at 3:54 am
Ok, that looks like it did it. I’ll create a promo and test it out. But I ran into another problem. There are 4 messages on the promo page. Should I worry about them or can I dismiss them? Here they are:
atabase table wp_esp_promotion existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? We recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wp_esp_promotion. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from wp_esp_promotion manually then restore to the backup again.
Dismiss
Database table wp_esp_promotion_object existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? We recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wp_esp_promotion_object. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from wp_esp_promotion_object manually then restore to the backup again.
Dismiss
Database table wp_esp_promotion_rule existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? We recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wp_esp_promotion_rule. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from wp_esp_promotion_rule manually then restore to the backup again.
Dismiss
Database table wp_esp_rule existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? We recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wp_esp_rule. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from wp_esp_rule manually then restore to the backup again.
|
|
Josh
|
July 1, 2015 at 12:24 pm
Hi Bill,
It really depends. You’ll want to make sure that those tables aren’t in your backup before you follow the instructions to restore to the backup again.
|
|
William Tozzo
|
July 2, 2015 at 3:37 am
Hi Josh:
Now you’re beyond my scope. I don’t know what you mean. Should I get my web developer to do anything?
Bill
|
|
Josh
|
July 2, 2015 at 8:23 am
Yeah your web developer should be able to follow the instructions that are outlined in those messages.
|
