-
MODX Staff
- 12,272 Posts
Looks like they’re both running PHP 5.2.6. PHP 5.3 is still in RC status so I can’t see Mosso deploying that in production beyond limited testing yet.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Ryan, yes I see that. I got confused about the Mosso naming convention on the new instances: "HTTP_X_MOSSO_DT PHP5-3" versus the instances that do work that say: "HTTP_X_MOSSO_DT PHP5-2 ".
I did notice that the variable configurations are not the same. Do you think that just a PHP configuration change could cause this issue?
OK, my problem is solved. Here is the deal:
Evidentially, by default the servers store all sessions in a /tmp/ directory and that can cause an issue depending on how the server is configured. This /tmp/ directory is shared by all websites on the cloud. By changing where the session goes, it pulls the session away from the file system garbage collecting.
There are two lines that need to be added to the .htaccess file that do two things:
1. Saves our sessions into a directory in our structure
2. Extends the session time longer
# Write the sessions into a directory specific to the server instance
php_value session.save_path /mnt/stor2-wc1-dfw1/396360/398509/www.haselden.com/web/content/sessions/
php_value session.gc_maxlifetime 28800
Implementing this solution solved my issue.
-
MODX Staff
- 12,272 Posts
That’s great information. I think I’ll rename and sticky this topic in the thread for future reference for others. Thanks for doing the research brandsavvy.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Thanks Guys! Was having the same problem and pulling my hair out. All is good now.
THANK YOU!!!!
I was trying to get this issue working after reading this page:
http://svn.modxcms.com/docs/display/MODx096/Friendly+URL+Solutions
What I was doing was not using the full server path of my site. My manager kept logging me out and it was driving me nuts. This seemed to have solved it. Question though; do we need to change the folder permissions whatever directory we use for sessions?
Just curious here. Again this post kept me from pulling the few remaining head hairs I have!
I twitch because I care....and drink too much coffee.
It may not be necessary but it doesn’t hurt to add read/write access to the sessions folder.
I’m having the same issue (when trying to login it says "...is currently editing these settings. Please wait until the other user has finished and try again."
I have made the changes to the ht.access file and continue to get the message. Is there something that I’m doing incorrectly?
Here’s what I added:
# Write the sessions into a directory specific to the server instance
php_value session.save_path /home/domainName/public_html/assets/sessions/
php_value session.gc_maxlifetime 28800
thanks for any help!