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 Two Add-Ons Failing to Acivate: Triggered Fatal Error | Event Espresso - Staging Server
Hello,
I purchased Event Espresso Business yesterday, backed up my website, installed the latest version of WP and installed EE 4.1.5. I’ve had no problems up until I tried to install the Add-Ons. Both the ticketing Add-On and the MailChimp Add-Ons are failing to activate due to the following:
Plugin could not be activated because it triggered a fatal error.
Warning: require_once(EVENT_ESPRESSO_PLUGINFULLPATHincludes/functions/database_install.php): failed to open stream: No such file or directory in /usr/local/pem/vhosts/125925/webspace/httpdocs/blog/wp-content/plugins/espresso-ticketing/espresso-ticketing.php on line 106 Fatal error: require_once(): Failed opening required ‘EVENT_ESPRESSO_PLUGINFULLPATHincludes/functions/database_install.php’ (include_path=’.:/usr/share/pear:/usr/share/php:/usr/local/pem/vhosts/125925/webspace/httpdocs/blog/wp-content/plugins/mailchimp-widget/lib’) in /usr/local/pem/vhosts/125925/webspace/httpdocs/blog/wp-content/plugins/espresso-ticketing/espresso-ticketing.php on line 106
Currently none of Event Espresso 3 Add-ons are compatible with Event Espresso 4.
So if you need the functionality of the Add-on’s you will need to use EE3 for the time being.
Hope that helps.
Viewing 2 reply threads
The support post ‘Two Add-Ons Failing to Acivate: Triggered Fatal Error’ 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.