TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692011-11-25T08:59:27ZTYPO3 Forge
Redmine TYPO3 Core - Task #32075 (Closed): Integrate system extension linkvalidator as submodulehttp://forge.typo3.org/issues/320752011-11-25T08:59:27ZOliver Haderoliver.hader@typo3.org
<p>Integrate system extension linkvalidator as Git submodule.<br />git://git.typo3.org/TYPO3v4/Extensions/linkvalidator.git</p> TYPO3 Core - Bug #30095 (Closed): Arbitrary TypoScript execution on system extension formhttp://forge.typo3.org/issues/300952011-09-20T17:37:34ZOliver Haderoliver.hader@typo3.org
<p>The new system extension form can be used to render custom FORM elements as well as regular cObjects like TEXT or COA.<br />Since the form wizard can be used by any editor in the backend and writes data to the field bodytext, this can also be used to execute arbitrary TypoScript without further access checks.</p>
<p>This change introduces two defined and allowed content elements "header" and "textblock" that can be defined by using the form wizard. If the TypoScript that was generated by the mentioned wizard is rendered, regular cObjects are disabled. If the FORM or FORM_INT cObject is used directly from a TypoScript template, all possible cObjects can still be used.</p>
<p><img src="http://forge.typo3.org/attachments/download/18789/form_wizard.png" title="Content Elements header and text block" alt="Content Elements header and text block" loading="lazy" /></p> TYPO3 Core - Task #30094 (Closed): Refactor view component of system extension formhttp://forge.typo3.org/issues/300942011-09-20T16:52:23ZOliver Haderoliver.hader@typo3.org
<p>Get rid of calling the constructor of the parent without any additional logic.</p> TYPO3 Core - Bug #30088 (Closed): Wrong content element rendering in system extension formhttp://forge.typo3.org/issues/300882011-09-20T13:53:13ZOliver Haderoliver.hader@typo3.org
<p>The ability to render custom content elements in the system extension form fails.</p> TYPO3 Core - Task #30086 (Closed): Strict string value handling in system extension formhttp://forge.typo3.org/issues/300862011-09-20T12:55:28ZOliver Haderoliver.hader@typo3.org
<p>Misconfigurations in e.g. TypoScript lead to cased "Array" strings.</p> TYPO3 Core - Task #30066 (Closed): Clean-up PHPdoc in t3lib_divhttp://forge.typo3.org/issues/300662011-09-20T01:33:51ZOliver Haderoliver.hader@typo3.org
<p>Clean-up PHPdoc in t3lib_div</p>
<ul>
<li>fix some PHPdoc comments</li>
<li>remove @author annotations</li>
</ul> TYPO3 Core - Task #30046 (Closed): Refactor code of new form system extensionhttp://forge.typo3.org/issues/300462011-09-19T20:42:12ZOliver Haderoliver.hader@typo3.org
<p>Refactor code of new form system extension:</p>
<ul>
<li>remove superfluous __construct() methods</li>
<li>fix PHPdoc comments and add type hints</li>
<li>remove unused classes</li>
<li>fix CGL issues</li>
</ul> TYPO3 Core - Bug #29769 (Closed): Parse error in t3lib/class.t3lib_parsehtml.phphttp://forge.typo3.org/issues/297692011-09-14T10:21:00ZOliver Haderoliver.hader@typo3.org
<p>There is a syntax error in t3lib/class.t3lib_parsehtml.php.</p> TYPO3 Core - Task #26738 (Closed): Use external Core Project DBAL as Git submodulehttp://forge.typo3.org/issues/267382011-05-10T22:39:25ZOliver Haderoliver.hader@typo3.org
<p>Use external Core Project DBAL as Git submodule</p> TYPO3 Core - Task #26725 (Closed): Use external Core Project version as Git submodulehttp://forge.typo3.org/issues/267252011-05-10T11:09:35ZOliver Haderoliver.hader@typo3.org
<p>Use external Core Project version as Git submodule in older TYPO3 branches (4.2-4.4)</p> TYPO3 Core - Task #26581 (Closed): Use external Core Projects workspaces and version as Git submo...http://forge.typo3.org/issues/265812011-05-03T12:40:16ZOliver Haderoliver.hader@typo3.org
<p>Use external Core Projects workspaces and version as Git submodules</p> TYPO3 Core - Bug #24777 (Closed): SQL error in Update Wizard of workspaceshttp://forge.typo3.org/issues/247772011-01-24T16:55:27ZOliver Haderoliver.hader@typo3.org
<p>On using the Update Wizard in the Install Tool, the following SQL error appears:<br />SELECT parentid FROM sys_workspace_stages WHERE parenttable="sys_workspace"</p>
<p>Solution: The stages table must be written in singular (sys_workspace_stage)</p>
<p>(issue imported from #M17274)</p> TYPO3 Core - Bug #21821 (Closed): treeLevel in TSconfig conditions should consider the creation o...http://forge.typo3.org/issues/218212009-12-08T11:41:17ZOliver Haderoliver.hader@typo3.org
<p>The TSconfig condition [treeLevel = 2] counts the level of nestification in the pagetree. However, in the backend new pages could be created and the mentioned condition should consider that situation as well.<br />PIDupinRootline behaves similar in the backend.</p>
<p>(issue imported from #M12977)</p> TYPO3 Core - Feature #20577 (Closed): Create better session identifiers and add basic validationhttp://forge.typo3.org/issues/205772009-06-05T15:26:21ZOliver Haderoliver.hader@typo3.org
<p>Current sesssion identifiers in TYPO3 are a MD5 representation of several parameters.<br />Due to several security requirements it might be necessary to have at least a 160bit session identifier (MD5 has only 128bit) - e.g. using SHA1 or SHA2.</p>
<p>Furthermore it should be ensured that a session identifier really was created by the TYPO3 system. It's not critical at all currently since a brute force attack against a 128bit value takes some time. However, the session id used in the cookie should have another hash that uses the encryption key to ensure that it really was created by the accordant TYPO3 website.</p>
<p>(issue imported from #M11280)</p> TYPO3 Core - Bug #17838 (Closed): Files with extension xml are ignored as resource of a templatehttp://forge.typo3.org/issues/178382007-11-23T19:00:19ZOliver Haderoliver.hader@typo3.org
<p>Uploading a xml file to a template (sys_template) is denied by TCEmain since the extension xml isn't part of the allowed file extensions. A possibility would be to define "xml" in the imagefile_ext, but XML isn't an image... ;-)</p>
<p>(issue imported from #M6817)</p>