Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Worked In Testing, but Not Production | Event Espresso - Staging Server
I was testing the free version in my test system. I moved it over to production and was going to enter a “real” event. I am now getting: WordPress database error: [Unknown column ‘ticket_id’ in ‘field list’] when I click submit new event. I also can’t enter any categories as it continues to give me a “Category Not Saved” message.
I was planning to purchase a copy since I like many of the added features, but this makes me hesitate. My previous testing was done on the last version. It seems like these issues popped up when I went to version 3.1.25.L.
Ok. Did that. I disabled and deleted the plug-in. Went into the database. Deleted the 12 or so tables with wp_Events in front of them.
I then went to wordpress.org, downloaded and installed the plug-in again. That fixed the admin issues in my original post.
But now when I go to an event on the site, fill out the registration and click submit, I get transferred to the Event Registration page, but it is blank. I have the short code: [ESPRESSO_EVENTS] on there (it was installed by the plugin). I have the payment settings configured and the general settings configured. I just get a blank page where I should be doing payments.
Any new ideas?
This reply was modified 12 years, 5 months ago by Scott Ficek.
The support post ‘Worked In Testing, but Not Production’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.