http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-05-12T06:07:12ZTYPO3 ForgeTYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4250262020-05-12T06:07:12ZJosef Glatzjosef.glatz@typo3.org
<ul><li><strong>Category</strong> set to <i>TypoScript</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>I never saw TypoScript snippets where parenthesis (brackets) are in use within object names (or as part of object names) since TYPO3 3.8. According to <a class="external" href="https://docs.typo3.org/m/typo3/tutorial-typoscript-in-45-minutes/10.4/en-us/TypoScriptOverview/FirstSteps/Index.html?highlight=parenthesis">https://docs.typo3.org/m/typo3/tutorial-typoscript-in-45-minutes/10.4/en-us/TypoScriptOverview/FirstSteps/Index.html?highlight=parenthesis</a> shows me that also:</p>
<blockquote>
<p>Parenthesis (()) are used for writing text values on more than one line.</p>
</blockquote>
<p>Do you have some reference for us? Or probably the place within the code of the TYPO3 core why such thing should have worked?</p> TYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4250312020-05-12T08:14:25ZBernd Wilket3A@pi-phi.de
<ul></ul><p>If those parenthesis worked before as a name I would consider it a bug or unwanted side effect as it does not conform the rules of typoscript.<br />Any opening parenthesis before an equal sign should open a multiline value, which ends with a line starting with a closing parenthesis (after white space), while the rests of these both lines are ignored.</p>
<p>Maybe the handling of whitespace as a seperator of object-/property-names and operator has changed and the splitting (and interpreting) is done different than before.</p>
<p>An explaining error message about unbalanced parenthesis would be required.</p> TYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4258772020-05-24T20:41:08ZGeorg Ringer
<ul><li><strong>Subject</strong> changed from <i>TypoScript - PageTS not loaded if </i> to <i>TypoScript - PageTS not loaded if a bracket exists in the key</i></li></ul> TYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4645372022-02-19T14:38:34ZChristian Kuhnlolli@schwarzbu.ch
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>New</i></li></ul> TYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4704592022-06-28T16:19:24ZChristian Kuhnlolli@schwarzbu.ch
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>Round brackets '(' are NOT valid keys of an identifier, since they are used for multiline assignments. The docs says valid chars are a-z,A-Z,0-9, but in practice colon : is used, too.</p>
<p>foo (<br /> multiline<br /> value<br />)</p>
<p>Unsure what the old parser does here, but the new parser creates mykey identifier with value 'something' and "= label" is a comment.</p>
<p>This won't change. Don't use these chars in identifiers. Won't fix.</p> TYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4704602022-06-28T16:19:38ZChristian Kuhnlolli@schwarzbu.ch
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/97816">Feature #97816</a>: New TypoScript parser</i> added</li></ul> TYPO3 Core - Bug #91361: TypoScript - PageTS not loaded if a bracket exists in the keyhttp://forge.typo3.org/issues/91361?journal_id=4717652022-07-20T11:59:27ZChristian Hackl
<ul></ul><p>It was not about the fix, but that you get an error message at all or a corresponding entry is written in the error_log or something.</p>
<p>I don't know the parser now, but in general I would consider characters that are not allowed in certain places, but are still somehow taken into account as here, as a question of security, or not?</p>