http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-11-18T21:02:01ZTYPO3 ForgeTYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4352662020-11-18T21:02:01ZJarvis H
<ul></ul><p>I had the same issue. I solved it by clearing browser cookies and truncating the be_sessions table.</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4353502020-11-19T19:39:21ZUwe Jakobsuwe.jakobs@imageco.de
<ul></ul><p>Hi everybody,</p>
<p>same issue here, but Jarvis' solution didn't work for me. Tested it with some Browsers and OSs and did the same things Lukas did.<br />I'm wondering if the issue is concerning Multidomain-Setups due to XSS-Defence-Approach?</p>
<p>Cheers,<br />Uwe</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4353512020-11-19T20:00:16ZLukas Hausammann
<ul></ul><p>Jarvis' solution didn't work for me either.<br />I changed the PHP version from 7.2 to 7.4 and then back again to 7.2.<br />Now it seems to be working. I don't have an explanation for it.</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4353812020-11-20T10:40:49ZOliver Haderoliver.hader@typo3.org
<ul></ul><p>Lukas Hausammann wrote in <a href="#note-3">#note-3</a>:</p>
<blockquote>
<p>I changed the PHP version from 7.2 to 7.4 and then back again to 7.2.<br />Now it seems to be working. I don't have an explanation for it.</p>
</blockquote>
<p>Changing PHP version at least "clears" OPcode cache - maybe that was the reason.</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4354632020-11-20T17:02:27ZUwe Jakobsuwe.jakobs@imageco.de
<ul></ul><p>I can confirm Lukas' workaround - changing PHP-Version down- and up again worked with me. It seems to be related with how your OPcache is managed - Oliver explained why.<br />I my case, only Systems on Managed Servers with the hoster "Hetzner" were affected, when the option "OPcache" was checked in the PHP-Settings.<br />On root-Servers with the same hoster, I had no problems at all, neither on all other Systems (local DEVs as Stand-Alones or VMs) with different OS and PHP-Versions. <br />Obviously, there seems to be a bug in the update-procedure (and not in the 9.5.23-Core) in combination with OPcache-Flushing, since this worked like a charm with older updates.</p>
<p><ins>EDIT:</ins> My assumption concerning Multidomain-Setups proved to be wrong, weanwhile.</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4583562021-11-25T09:32:20ZEugène Fritzeugene.fritz@hotmail.com
<ul></ul><p>Had the same problem, deleting the old core folder solved the problem for me.</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4590872021-11-30T11:25:48ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>Does this still happen in v10/v11?</p> TYPO3 Core - Bug #92872: Update from 9.5.22 to 9.5.23: I will be logged out automatically in the backend when I log inhttp://forge.typo3.org/issues/92872?journal_id=4645632022-02-19T16:28:32ZChristian Kuhnlolli@schwarzbu.ch
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Closed</i></li></ul><p>Hey. I hope it's ok to close here: opcache issues most likely need to be resolved on server level, there is not much TYPO3 application can do here. the 'flush caches' in install tool <strong>may</strong> help here, but a web server or php process restart might be the only solution, depending on opcache configuration.</p>