Hi,
the description of the problem:
when you open the website manager and click on any item, the page reloads and instead of the item fields and content the welcome screen is displayed (which you see when you first login to the manager dashboard). The request is sent, the item link in the list looks active (has background) and there is the resource address in the address field (e.g. site.com/manager/?a=resource/update&id=2). No errors in the console. However, when I log in from my laptop where I created the website - it works! But only in Google Chrome (both usual and incognito mode).
There is another strange detail. When I open a recource content on my computer and try to leave the page without making any changes, the system shows me the warring alert as if there were unsaved changes. Maybe this is somehow related.
The manager has only one user - the admin, so all attempts to work with resources were made via this account. Everything worked okay at the beginning, but suddenly such behavior occured. It was my client who first noticed the problem when she was trying to add and edit new resources. It happened when I wasn't working on the website and I can't think of any action that could cause it.
I guess it is some kind of a cache or cookie problem, but I am not good at it. I tried manually clearing the core/cache directory but it didn't help.
That's really mysterious.
The only thing I can think of is a leftover cookie or something in the browser cache, though using incognito or private mode should solve that.
One other thought: could you be logging in to www.site.com on one machine and site.com on the other? That would make it a session issue.
In the MODX .htaccess file, there's a section you can uncomment to force www or non-www URLs, so that may be working like it's supposed to.
You could check the .htaccess file against the standard MODX ht.access file (which may still be there in the MODX root), to see if the host has added anything.
Another thing to try is repairing all tables in the database in PhpMyAdmin.
Yes. You can use a second DB with MODX, but you have to explicitly open a connection to it in code when you want to use it. It's not recommended unless you can't avoid it (e.g., the second DB has to be on a different server).
PS: I also get the unsaved changes message at times. I think it comes from an unruly MODX plugin or a browser plugin.
It looks like automatically created or something like that. I have login/password only for the first databased that I seem to remember creating.