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 not found | Event Espresso - Staging Server
I’m on GoDaddy hosting — I know you don’t like it, but it’s what it is and I’m stuck with it — and I’ve got the green light on everything except the Session Save Path. The error is “does not exist – contact your host to resolve the problem”.
Did that… They added a php5.ini to my server root and attempted to configure it. It got as far as changing the backend error to a folder like “/sessionsavepath” or (attempt 2) “../tmp does not exist” and had the unfortunate side effect of causing multiple EventEspresso errors at the head of the site, and in another plugin on a different site on the same server. These seemed to be mostly related to function session save or some such. I changed the name of the php5.ini so the default php.ini (that I do not have access to) would take over again.
Back to square one.
Can you please advise as to a fix for this?
Thanks,
Bobby
WP version – 3.8
EE version – 3.1.36.2.P
New install – yes
Page – wmillerwinnipeg.com/runattheridge/
It sounds like they did not properly configure the server’s SESSION_SAVE_PATH. They’ll need to verify that they point it to a directory that:
1) actually exists on the server
2) PHP has write access to
Viewing 1 reply thread
The support post ‘Session Save Path not found’ 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.