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
W3 Total Cache & EE3.x | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium W3 Total Cache & EE3.x

W3 Total Cache & EE3.x

Posted: March 28, 2014 at 12:59 pm

Viewing 2 reply threads


Joseph Guarino

March 28, 2014 at 12:59 pm

Hello,

I’m interested in running EE 3.x (latest) with W3 Total Cache w/ Amazon CloudFront config. Can this be done if I exclude the proper pages as is listed here: https://staging.eventespresso.com/version/ee4/

Or does this only apply to EE 4.x?

Thanks so much!!!


Jonathan Wilson

  • Support Staff

March 28, 2014 at 1:14 pm

Hi Joseph,

Yes. You shouldn’t have any trouble doing that in EE3 also. Just make sure that any page that has an EE shortcode on it is excluded from the caching.


Lorenzo Orlando Caum

  • Support Staff

March 28, 2014 at 4:47 pm

Hello Joseph,

Here are the slugs for a default install of Event Espresso 3:

/event-registration/
/registration-cancelled/
/thank-you/
/transactions/

You can confirm the pages that are in use through WP-admin –> Event Espresso –> General Settings

Be sure to clear your cache for your caching plugin after adding them.


Lorenzo

Viewing 2 reply threads

The support post ‘W3 Total Cache & EE3.x’ 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.

Event Espresso - Staging Server