Latest Version of Safari and ProcessWire

[ryanscherler]

I just upgraded to the latest version of Safari (6.1 with the developer tools enabled) and it seems that whenever I inspect an element or just view source, I get logged out of the PW admin.

Any ideas why this might be happening?

* BTW: I am running PW 2.3.5

[Martijn Geerts]

I have no issues with Safari 6.1 & PW 2.35.

ps, I'm happy Safari developer tools is useful again. 

[ryanscherler]

Maybe its related to the beta admin theme that Ryan has just released ( http://processwire.com/talk/topic/4650-new-processwire-admin-theme-on-dev-branch/ )?

I have no idea why that would be though...

[ryanscherler]

I just tried renaming the templates-admin to something different and then tried, still getting logged out with the default admin theme.

I just checked another client site running the stable version (2.3.0), inspected an element while logged in and it didn't log me out. Something related to 2.3.5 for me it seems.

[titanium]

I just upgraded to the latest version of Safari (6.1 with the developer tools enabled) 

I don't know if it makes any difference and if it is of any help, but Safari's latest version is 7.0 (default in OS X 10.9 Mavericks)...

[ryanscherler]

I haven't updated to Maverics yet - so its possible this issue may work itself out in 7.0? Although Martijn seems to not have issues with 6.1.

[adrian]

I know it doesn't help, but I am also having no problems with 2.35 (actually very latest dev today) and Safari 6.1

Not sure why or how exactly, but does setting:

$config->sessionFingerprint = false;  

help at all?

Are there any other settings in the config.php that are different between the site with the new admin theme and the other site you tested?

[ryanscherler]

Setting the session fingerprint to false didn't have an effect. Are you also getting logged out after viewing source / inspecting an element in Safari 6.1?

[adrian]

Sorry - maybe my wording wasn't very clear - I am not having any problems - the "also" was referencing Martijn's comment.

[ryanscherler]

Hah - sorry, I somehow misread the "no" in your previous post. I am really not sure what to do on this.

I'm about to update to Maverics and safari 7.0 - hopefully that will solve this odd issue ;-)

[ryanscherler]

Wait! For some reason I cleared my cache and set the session fingerprint to false. It seems to have fixed it. I stay logged in now when inspecting an element. Any ideas why it would do this?

[ryan]

Maybe you have badBIOS?