http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692017-10-18T00:01:44ZTYPO3 ForgeTYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=3436922017-10-18T00:01:44ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Category</strong> set to <i>TypoScript</i></li></ul> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=3948822019-02-11T22:45:48ZChristian Forgács
<ul></ul><p>This bug still exists in TYPO3 9</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=3966202019-03-13T09:32:01ZFabian Schöner
<ul></ul><p>This bug also exists in TYPO3 7.6.34.</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4142282020-01-22T18:13:41ZGuillaume Germainguillaume@germain.bzh
<ul><li><strong>Target version</strong> set to <i>Candidate for patchlevel</i></li></ul><p>This bug also exists in TYPO3 9.5.13.</p>
<p>There is a problem with the Introduction Package because the "bootstrap_package" extension uses "RESTORE_REGISTER" in lib.dynamicContent.</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4142292020-01-22T18:16:48ZGuillaume Germainguillaume@germain.bzh
<ul><li><strong>Category</strong> changed from <i>TypoScript</i> to <i>Frontend</i></li></ul><p>It concerns the TypoScriptFrontendController class.</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4343682020-10-30T16:24:04ZPetra Neumann
<ul></ul><p>The problem still exists in TYPO3 v10.</p>
<p>If any RESTORE_REGISTER is called, the temp value for SYS_LASTCHANGED is gone. Since ext:fluid_styled_content suggests using RESTORE_REGISTER for inserting content in the page template based on FLUIDTEMPLATE (see lib.dynamicContent), a lot of site-package extensions make use of it (like the bootstrap package). So in many TYPO3 installations SYS_LASTCHANGED is only updated for changes of the page properties but not the page content. This might be a problem, since the ContentObjectRenderer.php reads "The SYS_LASTCHANGED timestamp can be used by various caching/indexing applications to determine if the page has new content." - which will not work as intended then. Also, some sites use SYS_LASTCHANGED to show a "Last Updated on ...", even though it is not intended for that originally - this also fails with the value not being written correctly.</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4449762021-05-28T07:03:23ZReindl Berndb.reindl@2mountain.com
<ul><li><strong>File</strong> <a href="/attachments/36103">RestoreRegisterContentObject.php</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/36103/RestoreRegisterContentObject.php">RestoreRegisterContentObject.php</a> added</li></ul><p>If 'SYS_LASTCHANGED' is stored outside the $register variable, it's no longer available via 'data = register:SYS_LASTCHANGED' in TypoScript.</p>
<p>Quick solution:</p>
<p>@<br />public function render($conf = [])
{<br /> $SYS_LASTCHANGED = isset($GLOBALS['TSFE']->register['SYS_LASTCHANGED']) ? $GLOBALS['TSFE']->register['SYS_LASTCHANGED'] : false;<br /> $GLOBALS['TSFE']->register = array_pop($GLOBALS['TSFE']->registerStack);<br /> if($SYS_LASTCHANGED !== false)<br /> $GLOBALS['TSFE']->register['SYS_LASTCHANGED'] = $SYS_LASTCHANGED; <br /> return '';<br /> }<br />@</p>
<p>So 'SYS_LASTCHANGED' is still available in register but is not restored when RESTORE_REGISTER is called.</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4451372021-05-31T11:54:19ZDaniel Lorenzdaniel.lorenz@extco.de
<ul><li><strong>TYPO3 Version</strong> changed from <i>8</i> to <i>10</i></li></ul><p>We have been able to successfully test this change in a current TYPO3 v10.4.</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4478502021-08-02T10:32:16ZSimon Gillitypo3@gilbertsoft.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-2 priority-4 priority-default" href="/issues/90827">Bug #90827</a>: If you edit the page content element, the "Last Mod." does not change.</i> added</li></ul> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4510492021-09-02T10:39:45ZAnonymous
<ul></ul><p>Daniel Lorenz wrote in <a href="#note-8">#note-8</a>:</p>
<blockquote>
<p>We have been able to successfully test this change in a current TYPO3 v10.4.</p>
</blockquote>
<p>We have the same problem. Especially with indexed_search which does not recognize changes to the page content.</p>
<p>Quickfix successfully tested under 10.4</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=4620552022-01-18T21:28:07ZSebastian Schmalsebastian.schmal@gmx.de
<ul><li><strong>TYPO3 Version</strong> changed from <i>10</i> to <i>11</i></li><li><strong>PHP Version</strong> changed from <i>7.0</i> to <i>7.4</i></li></ul><p>same problem with the ext:seo (TYPO3 11.x)</p>
<p>typo3\sysext\seo\Classes\XmlSitemap\PagesXmlSitemapDataProvider.php</p>
<p>'lastMod' => (int)($page['SYS_LASTCHANGED'] ?: $page['tstamp']),</p>
<p>but the field "SYS_LASTCHANGED" have a old timestamp in the DB.</p>
<p>the field "tstamp" is right, but the ext:seo take the SYS_LASTCHANGED</p>
<p>Yes, it update the page, like this <a class="external" href="https://forge.typo3.org/issues/90827#note-1">https://forge.typo3.org/issues/90827#note-1</a> (only updated in the frontend), but why?</p> TYPO3 Core - Bug #82528: SYS_LASTCHANGED value not being correctly set if RESTORE_REGISTER is usedhttp://forge.typo3.org/issues/82528?journal_id=5122572024-03-15T15:24:01ZOliver Pfaff
<ul><li><strong>File</strong> <a href="/attachments/38350">BUGFIX_core_bug__forge_typo3_org_issues_82528.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/38350/BUGFIX_core_bug__forge_typo3_org_issues_82528.patch">BUGFIX_core_bug__forge_typo3_org_issues_82528.patch</a> added</li></ul><p>This seems still a thing. Here a new Patchfile for TYPO3 11, it uses the same solution from Reindl Bernd but avoids the usage of the $GLOBALS like the implementation in V11</p>
<p>Probably the bug is still inside v12 as well, i didn't test this. RestoreRegisterContentObject in v12 is the same as in v11 but maybe a different or better solution was found.</p>