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
Preempting the security error issue with caching plugins | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Preempting the security error issue with caching plugins

Preempting the security error issue with caching plugins

Posted: April 1, 2014 at 8:43 pm

Viewing 3 reply threads


Gregoria Lara

April 1, 2014 at 8:43 pm

Just as a suggestion, to avoid the infamous “security error” issue, and with several of the major caching plugins (W3 Total Cache, WP Super Cache, Quick Cache, etc.) all supporting the same convention to disable caching, could you look into using this:

<code>
define(&#039;DONOTCACHEPAGE&#039;, TRUE)
</code>

Maybe an idea? Thanks!


Gregoria Lara

April 1, 2014 at 8:45 pm

Also, please sanitize your sanitization, LOL :-)


Dean

  • Support Staff

    •

April 7, 2014 at 1:12 am

Hi,

Thanks for your feedback, I will certainly pass this over to be looked at.


Gregoria Lara

April 20, 2014 at 9:05 am

Much appreciated!
Viewing 3 reply threads

The support post ‘Preempting the security error issue with caching plugins’ 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 Gregoria Lara 10 years, 9 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server