http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-05-07T23:18:21ZTYPO3 ForgeTYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=1639032013-05-07T23:18:21ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li><li><strong>Target version</strong> deleted (<del><i>0</i></del>)</li></ul><p>The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?</p> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=1658142013-05-17T08:32:03ZFranz Holzingerfranz@ttproducts.de
<ul></ul><p>The code of the method substituteMarkerArrayCached has been moved into <br />file ContentObjectRenderer.php.</p>
<p>The code looks unchanged. The problem remains the same.</p>
<pre>
// Finding keys and check hash:
$sPkeys = array_keys($subpartContentArray);
$wPkeys = array_keys($wrappedSubpartContentArray);
$aKeys = array_merge(array_keys($markContentArray), $sPkeys, $wPkeys);
</pre> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=1658252013-05-17T09:57:28ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=2448832015-01-15T17:26:26ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li><li><strong>Is Regression</strong> set to <i>No</i></li></ul><p>Since you dug so deep into the code, would you see the possibility to come up with a patch for this?</p> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=2449272015-01-15T19:10:31Z rengaw83
<ul></ul><p>I dont have a patch at the moment, but i am using the rn_base extension since some years. There are the same function with some changes, which fixed this issue.</p>
<p>Have a look at <a class="external" href="https://github.com/rengaw83/rn_base/blob/master/util/class.tx_rnbase_util_Templates.php#L295">https://github.com/rengaw83/rn_base/blob/master/util/class.tx_rnbase_util_Templates.php#L295</a></p>
<p>The reason is, how the md5 store key was created.<br />This should not created with a merge of the marker array keys.<br />The store key has to be created with all marker array keys itself.</p>
<p>old:<br /><pre>
$storeKey = md5('substituteMarkerArrayCached_storeKey:'.serialize(array($content, $aKeys)));
</pre></p>
<p>new can be:<br /><pre>
$storeKey = md5('substituteMarkerArrayCached_storeKey:'.serialize(array($content, $sPkeys, $wPkeys, array_keys($markContentArray))));
</pre></p>
<p>I hope it helps a little bit.</p> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=2614632015-06-15T14:18:39ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=3012332016-04-08T11:00:53ZDaniel Goerz
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>This issue is very old. Is the bug still present in master and/or 7LTS?</p> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=3087462016-07-07T10:53:28ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Category</strong> set to <i>Content Rendering</i></li></ul> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=3148612016-10-07T10:36:14ZOliver Haderoliver.hader@typo3.org
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Accepted</i></li></ul><p>Behavior confirmed in master (CMS 8)</p> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=3148622016-10-07T10:36:38ZGerrit Code Review
<ul><li><strong>Status</strong> changed from <i>Accepted</i> to <i>Under Review</i></li></ul><p>Patch set 1 for branch <strong>master</strong> of project <strong>Packages/TYPO3.CMS</strong> has been pushed to the review server.<br />It is available at <a class="external" href="https://review.typo3.org/50098">https://review.typo3.org/50098</a></p> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=3458152017-10-19T22:40:13ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>Under Review</i> to <i>New</i></li></ul> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=3496392017-10-27T13:17:03ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Category</strong> changed from <i>Content Rendering</i> to <i>Frontend</i></li></ul> TYPO3 Core - Bug #19501: same key wrongly used in substituteMarkerArrayCachedhttp://forge.typo3.org/issues/19501?journal_id=4200442020-03-23T13:43:15ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Meanwhile, the method has been deprecated and removed.</p>