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
Session save path error | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › Session save path error

Session save path error

Posted: December 29, 2013 at 6:23 am

Viewing 1 reply thread


Darryn Hope

December 29, 2013 at 6:23 am

Hi There,
When i run the System Status Module I have the following error:
“Session save path: does not exist – contact your host to resolve the problem”.

How do I resolve this error?

I am hosted with Godaddy and have followed this support article; http://support.godaddy.com/groups/go-daddy-customers/forum/topic/session-save_path-error-on-my-wordpress-website/
but am still getting the error.

-my php status can be viewed here http://www.kyrona.com/phpinfo.php

Cheers Darryn


Dean

  • Support Staff

    •

December 30, 2013 at 2:41 am

Hi Darryn,

Can you go to Event Espresso > System Status in your admin dashboard and advise what the Session save path says there please as on the phpinfo it is not set which it should be.

If the session path is not writeable you will need to ask your host to make it writeable.
Viewing 1 reply thread

The support post ‘Session save path 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.

Status: closed

Updated by Dean 11 years ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server