First thing I would check is your session & cookie settings within the modx system settings, specifically the session_cookie_lifetime to see how long your sessions are set to last for (in seconds)
-
☆ A M B ☆
- 427 Posts
Quote from: nick2687 at Jun 11, 2013, 02:22 PMFirst thing I would check is your session & cookie settings within the modx system settings...
I have never seen a need to even adjust the default settings. More likely it is in the php or server configuration.
-
☆ A M B ☆
- 24,524 Posts
Revo by default stores sessions in the database. A badly configured "cloud" could be causing this. It might be worth a try changing the System Setting "session_handler_class" to empty (delete the modSessionHandler) - then it will use the default PHP session files.
Also check your .htaccess or equivalent. This sort of thing can be caused by flip-flopping between www.domain.com and just domain.com, as these are considered different domains for SESSION purposes.
Consider the steps taken: every time a page is requested from the server, the SESSION cookie for that domain is also sent by the browser, which cookie contains the SESSION ID. The requested .php file is run (index.php or an AJAX request processing .php file) - this is where the rewrite comes into play, rewriting, for example, home.html to index.php?q=1 to let MODx know to process resource ID #1. The manager page requests should never be re-written - either requests to domain.com/manager/ should be excluded from the .htaccess file, or the RewriteEngine should be turned off in a .htaccess file in the /manager/ directory. PHP now does its thing, getting the Session ID from the $_COOKIE, querying the database to get the session information for that ID, and then setting the $_SESSION array. This includes for whole pages, page reloads and refreshes, as well as AJAX requests which, while not re-loading the entire page, make server requests for the specific .php files that will return the output to be displayed.
So there are a lot of things that have to work together here, from the browser to the server configuration to the database. My suspicion here is a badly configured "cloud" server configuration, causing database access to be a bit erratic. The Manager makes a lot of queries. That's why I suggested switching the System Settings to using the default PHP session handler.
I tried to remove the session_handler_class setting. URL Rewriting is disabled. I also disabled my stop browser script blocker plugin to be sure that it doesn't block the cookie but it's not better
-
☆ A M B ☆
- 1,780 Posts
You may want to check your timezone settings, in PHP, Apache, and mySQL. Any discrepancy between those settings, and sessions could get confused.
Hi,
Seems that all is in order with the timezone settings. I tried to use another wamp server (XAMPP) and I have the same problem. Could this problem be related directly to Windows ? On my Linux server all is Ok
Julien
I noticed something else : the problem happens only if I open in the extra I'm developping.
Hi.
I've same problem.
When I´m working in any component, Aparece a screen center to said "Your session has expired. Please proceed to login again." and can not save.
Anybody could resolve it?
I also get this message in the modx installations in which I am developing an extra. I have seen that in modx_session table there is created a new session when I open my cmp that I am developing.
Did anyone figured this out yet?
FYI: To enable development on the modx installation I had to change sessions_cookie_path setting to /. I could emagine that this is causing the problems :/
EDIT: It seesm so. If I clear the session table, change the sessions_cookie_path setting to an empty value and clear the cache manually everything is working normaly. I can't use my cmp tough because I am developing this extra outside of my modx installation ...
Any help would be nice, since I am got stocked on this one ^^
have a good n8!
[ed. note: venty13 last edited this post 12 years, 5 months ago.]
