|
Adam Schwartz
|
May 6, 2014 at 3:04 pm
I’m also trying to install on WordPress (3.9). I use the built-in plugin uploader. It says it uploads fine, but then I click to activate it and get a fatal error
Fatal error: Uncaught exception 'EE_Error' with message 'Error inserting values 0,0,email,payment,1,,,1 for columns EVT_ID,MTP_user_id,MTP_messenger,MTP_message_type,MTP
…
Error was Table …'eb_esp_message_template_group' doesn't exist' …
It seems the database tables were never created. I checked in phpmyadmin and in fact they weren’t created. I tried deactivating and reactivating EE but the tables don’t get created and I’m no longer shown the error.
|
|
Lorenzo Orlando Caum
|
May 6, 2014 at 3:39 pm
Hi Adam,
Is this a windows based server?
—
Lorenzo
|
|
Adam Schwartz
|
May 6, 2014 at 3:59 pm
No. It’s a standard Apache server running on linux. Nothing has ever had trouble creating db tables; just EE. Should I get a refund and switch to EE3?
|
|
Lorenzo Orlando Caum
|
May 6, 2014 at 4:14 pm
Try dropping the database tables for Event Espresso using PHPMyAdmin.
They start with:
dbprefix_esp_
Then reactivate through WordPress Plugins.
—
Lorenzo
|
|
Adam Schwartz
|
May 6, 2014 at 5:07 pm
I would drop them, but they were never created. I tried deactivating and reactivating, but that did nothing.
|
|
Adam Schwartz
|
May 6, 2014 at 5:42 pm
I’ve fixed the problem.
Thank you for your prompt assistance.
|
|
Adam Schwartz
|
May 6, 2014 at 6:05 pm
I’ve finished the installation, and Proceeded to create and edit my first event, but upon submitting, I was given this fatal error:
Warning: Invalid argument supplied for foreach() in wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php on line 233
Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php:233) in /home3/jschwart/public_html/K9EF/embed/wp-admin/post.php on line 233
Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/pricing/espresso_events_Pricing_Hooks.class.php:233) in /home3/jschwart/public_html/K9EF/embed/wp-includes/pluggable.php on line 896
-
This reply was modified 10 years, 6 months ago by
 Josh. Reason: removed sensitive server details and irrelevant information
|
|
Josh
|
May 6, 2014 at 7:37 pm
Hi Adam,
That’s not a fatal error, it’s a warning. Can you send temporary admin credentials along via our support contact form here?
We’ll likely need to get some feedback from one of the developers about the issues you are reporting.
|
|
Josh
|
May 6, 2014 at 8:03 pm
A few more things that you can do:
1) Rest the EE4 tables by going to Event Espresso > Maintenance > Reset/Delete Data
2) Check with the host about restarting mySQL, or increasing the timeout and memory allocated to WP.
3) Reactivate EE.
Event Espresso does create a lot of tables (compared to the average WP plugin) so if the script timed out on installation some of the tables wouldn’t have been created. If you try to manually create them later, you could end up with some missing defaults, which looks to be the case based on the PHP warnings you posted.
|
|
Adam Schwartz
|
May 6, 2014 at 9:48 pm
My issue with the database tables wound up being because of mySQL permissions. I re-enabled permissions (to CREATE, etc) and reactivated the plugin. Then it worked.
The issue with the “foreach()” is because the program is expecting a php variable to be an array but it’s not. That was before I had set any datetime tickets for any events, so I believe that’s the cause. I had already successfully activated the plugin and navigated across a couple pages before I encountered this error.
|
|
Josh
|
May 7, 2014 at 7:19 am
When the database installation scripts run there are default values added, which doesn’t look to be the case here because of the warning message. I’d recommend doing that reset then installing again now that you have the mySQL permissions sorted.
|
