I'm fairly sure it did.I don't believe before 1.0.3 it would log me out of Facebook entirely if I logged out of the forum.
I'm fairly sure it did.I don't believe before 1.0.3 it would log me out of Facebook entirely if I logged out of the forum.
I'm fairly sure it did.
Chrome is terrible for clearing cache.
I usually have to press CTRL+F5 2 or more times.
general-forums.com/logout/?redirect=http://general-forums.com/logout/?redirect=http://general-forums.com/logout/?redirect=http%3A//general-forums.com/logout/%3Fredirect%3Dhttp%253A//general-forums.com/logout/%253Fredirect%253Dhttp%25253A//general-forums.com/logout/%25253Fredirect%25253Dhttp%2525253A//general-forums.com/logout/%2525253Fredirect%2525253Dhttp%252525253A//general-forums.com/logout/%252525253Fredirect%252525253Dhttp%25252525253A//general-forums.com/logout/%25252525253Fredirect%25252525253Dhttp%2525252525253A//general-forums.com/logout/%2525252525253Fredirect%2525252525253Dhttp%252525252525253A//general-forums.com/logout/%252525252525253Fredirect%252525252525253Dhttp%25252525252525253A//general-forums.com/logout/
location += (location.indexOf('?') >= 0 ? '&' : '?') + 'redirect=' + escape(window.location);
window.location = XenForo.canonicalizeUrl(location);
okay, I commented out the one line from the first page, should I un-commented that and commented out the lines you just mentioned?Removing these 2 lines from js/xenforo/xenforo.js might be a safer workaround, as it will prevent the loop from happening (ie, for people that already triggered it):
Code:location += (location.indexOf('?') >= 0 ? '&' : '?') + 'redirect=' + escape(window.location); window.location = XenForo.canonicalizeUrl(location);
You can do both.okay, I commented out the one line from the first page, should I un-commented that and commented out the lines you just mentioned?
Fixed now, though the full fix is quite extensive (including a couple template changes). The workarounds I posted (one or the other, or both) should work in the mean time. If you get in the redirect loop, the issue should also go away once your session becomes invalid (after an hour of inactivity, usually).
Fixed now, though the full fix is quite extensive (including a couple template changes). The workarounds I posted (one or the other, or both) should work in the mean time. If you get in the redirect loop, the issue should also go away once your session becomes invalid (after an hour of inactivity, usually).
We use essential cookies to make this site work, and optional cookies to enhance your experience.