CB

Related issue at following thread.

http://www.joomlapolis.com/forum/153-professional-member-support/152845-2283-joomla-16--cb-14-login-problem#152845

Definitely seams date/time related during session/cookie comparison.

Added new case (with fall through so doesn't affect other CMS) to translate timezone to offset. Don't know if this exactly will fix the session issue, but it should cause their datetimes to match up MUCH better then before.

r1422 implements first part of fix : timezone was returned as region instead of number on joomla 1.6:

as suggested with following differences:

• Comment "NO break; on purpose for fall-through on other CMS:" is not correct, fall-through is not needed, as there is a break below anyway, it's better for phplint to avoid fallthroughs

• not sure that all php versions do optimize /60/60 into /3600, so let's do the math ourselves.

• added caching for the result in static var.

However, the session issue will still be there if timezone is set incorrectly, compared to server's timezone.

Kyle,
Please try doing following:

Edit plugin_foundation.php and return an offset of 25 !!!

Then see if session bug appears.

That will help find and fix that one.

Was never able to duplicate even with a offset of 25. Perhaps is a linux based issue? Am operating on a windows server (localhost).

Could not confirm even on Linux based install. Can be tested http://cb14.tafix.com/ where I have completely remove the offset fix. Could not duplicate. After waiting designated times the session issue never happened. At time of expiration of session I was simply logged out, no error. Logging back in presented no error either.

Spoof checking not entirely compatible with all browsers, hosts, or installs. Too easy to conflict. Patchs will turn the spoof checking into a parameter allowing admin to determine its usage. Default is now also disabled for best compatibility and stability.

Implemented as suggested in r1441 : Setting to disable spoofing protection if needed by bad server config

But set default to 1 and not to 0, as otherwise existing installations might experiment much more spam.