Logout Bug in v1.0.12 after manager folder got renamed?

I tried the new feature and renamed the manager folder, which is awesome as it brings more security! I also defined the new manager path in assets/cache/siteManager.php

However, now I am editing a document and when it gets "autosaved" after x seconds, modx logs out automatically (asking me if I really want to leave the page).

I thought it has to do with the manager path, which is still static "manager" in:

export_site.static.php, line 35
import_site.static.php, line 468
export.class.inc.php, line 275
modxmailer.class.inc.php, line 94
export_site.processor.php, line 61

But it is not solving the problem.

Any suggestions why I am logged out when the "auto save" happens, after I have renamed the manager folder?
Thanks


PS: I am still not sure if it is a auto save feature, but the site just reloads by itself, logging out and not saving the changes.
PPS:
From the network I see it is firing a GET to: /myrenamedmanager/includes/session_keepalive.php?tok=1234...
2. Then POST to: /myrenamedmanager/index.php
3. Then GET back to the document edited (?): /myrenamedmanager/index.php?a=8
4. and GET to the manager folder: /myrenamedmanager [ed. note: kajus99 last edited this post 12 years, 11 months ago.]

Quote from: kajus99 at Sep 30, 2013, 05:00 AM

Any suggestions why I am logged out when the "auto save" happens, after I have renamed the manager folder?
PS: I am still not sure if it is a auto save feature, but the site just reloads by itself, logging out and not saving the changes.

There isn't any autosave-like features in MODx Evolution... probably just some cookie leftovers after renaming manager folder. Did you try in incognito browser mode?

Thanks for your help, Eoler. I cleaned the browser cache and now it works. Sorry for the false report. But maybe it helps others with the same issue

Have a great day!

Well, one week later I have to say that - even after clearing the browser cache (latest Firefox on Win7) - the sudden logout still happens. Maybe somebody else can confirm this bug (who has the manager folder renamed of course).

To report back: I "solved" this by always going into the private mode of the browser and then logging into the manager. There seems to be indeed a cookie conflict somewhere.