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
error after upgrading from "lite" version to E4 | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › error after upgrading from "lite" version to E4

error after upgrading from "lite" version to E4

Posted: March 19, 2014 at 4:13 pm

Viewing 1 reply thread


carol pecora

March 19, 2014 at 4:13 pm

What does this mean? Everything was working in Event Espresso Lite, then I turned it off and uploaded E4 and now I get the following message:

An error has occurred:
The requested route 3 could not be mapped to any registered modules.
CR-MDLRQSRTR-RESROU-136


Lorenzo Orlando Caum

  • Support Staff

    •

March 19, 2014 at 4:45 pm

Hi Carol,

I have not seen this error before and I’d be happy to help you work through this issue.

Could you confirm that Event Espresso 3 Lite is deactivated through WP Plugins.

Also, did you install Event Espresso 4 manually through SFTP or FTP or did you download it from your Account and upload through WordPress admin –> Plugins?

—
Lorenzo
Viewing 1 reply thread

The support post ‘error after upgrading from "lite" version to E4’ 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.

The original Forum description...

Status: closed

Updated by Lorenzo Orlando Caum 10 years, 10 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server