Keep getting logged out of Poseidon when trying to save changes

[seadhna]

Hi there,
I keep getting logged out of the CMS in the last couple of days whenever I try to save certain articles or modules. I have already set the session time in Global Config. to 60 minutes. It doesn't happen for every article, only particular ones, and particular modules. Any ideas?

[seadhna]

Actually, it's not juts when I try to save - sometimes when I just try to open a module, I am sent to the login screen...

[seadhna]

Hi again,
I appear to have been able to resolve the issue by choosing 'NO' in Global Configuration (security tab) for 'Match Browser'.
All four of these options are now 'No' - does this compromise the security of the site in any way?

many thanks!

[datahell]

No, its OK to leave them all to no.
It looks strange to me why "match browser" causes you this problem. It looks like something changes your browser signature... Browser plug-ins can do bad things...

What match browser does is that it checks your browser signature and validates it. If an attacker high-jacks your session he wont be able to login as you, if he hasn't exactly the same browser signature as you. So match browser is an extra security option. The same way work "match ip" and "match referrer" options. With "match ip" only one user can login per ip. This is disabled by default as will cause you problems if multiple people share your home or work internet connection and access simultaneously the site.

[webgift]

Have you tried using a different browser? It looks strange to me too.

[ahmet]

with my old hosting i had the same problemm.. With my new host, it doesnt happen now..
To your information..

[seadhna]

Hi, sorry guys, I didn't see these replies. Yes, the problem occurred for several sites on the new CMS (not sure if it perhaps started with Poseidon) but it doesn't happen for one site which also had 'match browser' ticked to yes. So it's very strange! Quite possible an issue with the hosting company as suggested.

[seadhna]

Oh, not sure if this makes a difference - the one that caused no problems is using the Aurora template. The sites with problems are using self-created templates so perhaps there's something in that.