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
"SAFE MODE Restriction in effect" error after activation | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › "SAFE MODE Restriction in effect" error after activation

"SAFE MODE Restriction in effect" error after activation

Posted: February 2, 2014 at 12:14 am

Viewing 2 reply threads


Paul Warneke

February 2, 2014 at 12:14 am

After activating Event Expresso my site does not load and instead displays two lines of PHO error centring on a “SAFE MODE Restriction in effect” Running the requirements tool does not provide any problems, only a couple of apache file warning. The error refers to not being abler to access /temp folder but changing access to 777 make no difference. The error can be seer herehttp://pedals2perth.deskapades.me/test/
This test site only has event expresso installed on the latest version of WP
Any ideas would be appreciated.


Paul Warneke

February 2, 2014 at 12:17 am

PS – I should add that this test site is running the standard 2014 theme but it also occurs with my commercial theme. Deactivating EE removes the issue and site loads correctly.


Paul Warneke

February 2, 2014 at 1:55 am

Solution turned out to be with my php.ini file.
Adding the line “safe_mode = Off” fixed the issue
No more issue with test or production environments.
Viewing 2 reply threads

The support post ‘"SAFE MODE Restriction in effect" error after activation’ 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 Paul Warneke 10 years, 11 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server