http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692007-03-13T08:09:10ZTYPO3 ForgeTYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=446322007-03-13T08:09:10ZOliver Haderoliver.hader@typo3.org
<ul></ul><p>I think most "buggy extensions" were built as hyrid, using caching/cHash by default and disabling the cache in special situations by calling $TSFE->no_cache(). This could happen for e.g. guestbooks or shopping systems - the regular content for viewing should be cached - dynamic interactions with the user (e.g. put an article to a cart) should not.</p>
<p>Furthermore it might happen, that two different extensions are located on a page. The first is of type USER (cached) and the second is of type USER_INT (uncached). Providing data for both of them in one link will also be an issue for the cHash.</p>
<p>Thus, it might me required to have a method to walk around the cHash checks by using a so-called cHashTunnel. Parameters using this tunnel are not checked against being represented by the given cHash - but could of cause have an own cache for their specific demand.</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=446332007-03-13T15:32:20ZSteffen Kamperinfo@sk-typo3.de
<ul></ul><p>As we discussed in ECT-list, there are some combinations in extensions that causes this error (e.g. USER_INT and $GLOBALS['TSFE']->reqCHash();). So it is very important to make a strict guideline for extensions, how they should handle the cHash.</p>
<p>The most errors occures with developers when not knowing how to set the no_cache, how $pi_checkCHash influences the links etc.</p>
<p>If you want to set the 'pageNotFoundOnCHashError' default to 1, a list has to be made for the extensions that doesn't work with this, the authors should be contacted to update the extensions.</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=446342007-03-30T00:12:52ZMichael Stuckimichael.stucki@typo3.org
<ul></ul><p>Hi Steffen,</p>
<p>I've seen that Elmar has set up an article about proper caching of plugins, so probably you could manage to put this into the articles section on TYPO3.org? (Probably it can easily be merged with the "mysteries of chash"?)</p>
<p>Also I like the idea of having a list with extensions that require to be changed accordingly. We will definitely need to push this, therefore I find it important that it gets back into Trunk (4.2) as soon as possible...</p>
<p>- michael</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=1629182013-05-05T10:22:26ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Status</strong> changed from <i>Accepted</i> to <i>Needs Feedback</i></li><li><strong>Target version</strong> deleted (<del><i>0</i></del>)</li><li><strong>TYPO3 Version</strong> set to <i>4.1</i></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 #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=1805472013-09-03T13:05:06ZUwe Trotzekuwe.trotzek@googlemail.com
<ul></ul><p>Since TYPO3 6.1.X the default value of pageNotFoundOnCHashError has been set to '1'. As we used the default value of this option we didn't notice the problem before.</p>
<p>We get this error with ppw_lunchmenu's pdf generation. Of course an old extension but I think there are more Exts with the same error.</p>
<p>So I would say: Yes, the problem still exists.</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=1807752013-09-04T19:04:27ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=2456492015-01-19T09:54:58ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Category</strong> set to <i>Frontend</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li><li><strong>Assignee</strong> changed from <i>Michael Stucki</i> to <i>Mathias Schreiber</i></li><li><strong>Is Regression</strong> set to <i>No</i></li></ul><p>Is this still an issue?</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=2484222015-02-02T21:51:11ZGeorg Ringer
<ul></ul><p>imo this has been resolved by turning it on by default!</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=2628832015-06-19T16:51:33ZMichael Stuckimichael.stucki@typo3.org
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Resolved</i></li></ul><p>Uwe Trotzek wrote:</p>
<blockquote>
<p>Since TYPO3 6.1.X the default value of pageNotFoundOnCHashError has been set to '1'. As we used the default value of this option we didn't notice the problem before.</p>
<p>We get this error with ppw_lunchmenu's pdf generation. Of course an old extension but I think there are more Exts with the same error.</p>
<p>So I would say: Yes, the problem still exists.</p>
</blockquote>
<p>What you are describing sounds like expected: the cHash is wrong and therefore an error is shown. In that case, the real problem is in your extension "ppw_lunchmenu" and needs to be fixed. It was only not noticed before the mentioned change.</p>
<p><a class="user active user-mention" href="http://forge.typo3.org/users/41028">@all review</a>: I consider the issue as solved now that pageNotFoundOnCHashError is TRUE by default.</p> TYPO3 Core - Bug #17115: Wrong &chash values should trigger an errorhttp://forge.typo3.org/issues/17115?journal_id=3868782018-10-02T12:32:02ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>