TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-05-11T19:48:22ZTYPO3 Forge
Redmine TYPO3 Core - Bug #100862 (Resolved): Add CSP nonce value to RequireJShttp://forge.typo3.org/issues/1008622023-05-11T19:48:22ZOliver Haderoliver.hader@typo3.orgTYPO3 Core - Bug #80141 (Closed): Add allowLanguageSynchronization chain resolvinghttp://forge.typo3.org/issues/801412017-03-04T20:18:32ZOliver Haderoliver.hader@typo3.org
<p>Currently the localization behavior does not consider localization chains concerning field values to be synchronized over multiple localization hops that use the relative l10n_state "source".</p>
Imagine the following scenario of content element:
<ul>
<li>[uid:10, sys_language_uid:0, l18n_parent:0, l10n_source:0, header:Value]</li>
<li>[uid:11, sys_language_uid:1, l18n_parent:10, l10n_source:10, header:Value, l10n_state:{header:parent}]</li>
<li>[uid:12, sys_language_uid:2, l18n_parent:10, l10n_source:11, header:Value, l10n_state:{header:source}]</li>
</ul>
<p>Now if the record of the default record (uid:10) will be updated and the header value set to "Modified", only direct dependents would be synchronized. The automated update of the direct-child localization record (uid:11) does not trigger another update for the grand-child localization (uid:12). To achieve this, the data-map processor has been extended to collect new modifications to the data-map caused by synchronization processes - as long as modifications could be determined, another synchronization round is triggered for the modified items. This way the localization chain is completely synchronized if required, depending on the according l10n_state settings.</p> TYPO3 Core - Bug #72846 (Closed): Absolute URIs get prefixed with absRefPrefix in typolink proces...http://forge.typo3.org/issues/728462016-01-20T18:52:30ZOliver Haderoliver.hader@typo3.org
<p>An absolute URI (e.g. "/folder/someFile.png") get's prefixed with absRefPrefix (e.g. "/") which results in "//folder/someFile.png" - which is a schema-less URI notation and thus "folder" is interpreted as hostname.</p> TYPO3 Core - Bug #52825 (Closed): \TYPO3\CMS\Extbase\Object\ObjectManagerException vs of \TYPO3\C...http://forge.typo3.org/issues/528252013-10-14T23:51:53ZOliver Haderoliver.hader@typo3.org
<p>\TYPO3\CMS\Extbase\Object\ObjectManagerException is basically the same as the ObjectManager.<br />\TYPO3\CMS\Extbase\Object\ObjectManagerException has been introduced in this change:<br /><a class="external" href="https://git.typo3.org/TYPO3v4/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16">https://git.typo3.org/TYPO3v4/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16</a></p>
<p>Update:<br />Link to commit that introduced this change: <a class="external" href="https://git.typo3.org/TYPO3CMS/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16">https://git.typo3.org/TYPO3CMS/CoreProjects/MVC/extbase.git/commit/569063f64331766ea780cd118f0fd6c707664c16</a></p> TYPO3 Core - Bug #43139 (Closed): Activating NULL value field does not work with blank stringhttp://forge.typo3.org/issues/431392012-11-20T11:07:28ZOliver Haderoliver.hader@typo3.org
<p>Activating a field that supports NULL values and just using a blank string ("") does not work.<br />The problem is a strcmp() call that returns a false-positive on comparing NULL to blank strings.</p> TYPO3 Core - Bug #31936 (Closed): Add possibility to define http-equiv in meta taghttp://forge.typo3.org/issues/319362011-11-18T18:58:44ZOliver Haderoliver.hader@typo3.org
<p>Add possibility to define http-equiv in meta tags, currently this is only done if using the property "refresh".</p> TYPO3 Core - Bug #31561 (Closed): Add more more semantic classes for elementshttp://forge.typo3.org/issues/315612011-11-03T21:34:25ZOliver Haderoliver.hader@typo3.org
<p>The system extension form renders elements with a wrapped class like "csc-form-1" which just states the order or elements. To enable more specific styling a schema like the following is integrated:</p>
<pre>csc-form-<id> csc-form-element csc-form-element-<type></pre> TYPO3 Core - Bug #31120 (Closed): Add default csc-mailform DIV wraphttp://forge.typo3.org/issues/311202011-10-19T18:59:47ZOliver Haderoliver.hader@typo3.org
<p>A new form element does not have any class settings.<br />This issue reintroduces stdWrap possibilites for the new form system extension.</p> TYPO3 Core - Bug #27976 (Closed): A cache with identifier "workspaces_cache" does not existhttp://forge.typo3.org/issues/279762011-07-08T10:41:58ZOliver Haderoliver.hader@typo3.org
<p>The following exception is thrown on e.g. creating a new localized version of a page in the live workspace:</p>
<pre>#1203699034: A cache with identifier "workspaces_cache" does not exist. (More information)
t3lib_cache_exception_NoSuchCache thrown in file
/Users/olly/Development/typo3/master/t3lib/cache/class.t3lib_cache_manager.php in line 132.</pre> TYPO3 Core - Bug #11163 (Closed): Actions performed on tabs are not executed on the correct works...http://forge.typo3.org/issues/111632010-11-30T14:00:43ZOliver Haderoliver.hader@typo3.org
<p>Actions performed on tabs are not executed on the correct workspace</p> TYPO3 Core - Bug #22002 (Closed): Add unit test concerning XML parsing of unwrapped entitieshttp://forge.typo3.org/issues/220022010-01-21T15:12:45ZOliver Haderoliver.hader@typo3.org
<p>Imagine a XML value like the following:<br />index.php?&id=13</p>
<p>Several PHP/libxml versions do not parse entities like "&amp;" anymore, thus this part has to be wrapped in a CDATA block. A setting in the install tool automatically adds this block for flexforms - $TYPO3_CONF_VARS['BE']['flexformForceCDATA'].</p>
<p>However, this unit test checks whether the used PHP version requires the CDATA setting.</p>
<p>(issue imported from #M13317)</p> TYPO3 Core - Bug #21718 (Closed): Add functionality to work with caching frameworkhttp://forge.typo3.org/issues/217182009-11-27T16:25:24ZOliver Haderoliver.hader@typo3.org
<p>DBAL currently misses functionalities to work properly with the caching framework. Besides that maybe also some changes in the caching framework are required.</p>
<p>(issue imported from #M12800)</p> TYPO3 Core - Bug #21206 (Closed): Add more unit tests for t3lib_matchConditionhttp://forge.typo3.org/issues/212062009-10-08T16:12:05ZOliver Haderoliver.hader@typo3.org
Extend the number of unit tests in t3lib_matchCondition for the expressions:
<ul>
<li>language</li>
<li>usergroup</li>
<li>loginUser</li>
<li>globalString</li>
<li>treeLevel</li>
<li>PIDupinRootline</li>
<li>PIDinRootline</li>
<li>compatVersion</li>
<li>generic tests to access the namespaces GP, TSFE, ENV, IENV</li>
</ul>
<p>(issue imported from #M12153)</p> TYPO3 Core - Bug #20322 (Closed): Add possibility to use username and get located to OpenID provi...http://forge.typo3.org/issues/203222009-04-18T02:22:34ZOliver Haderoliver.hader@typo3.org
<p>Add possibility to use username and get located to OpenID provider if an OpenID was provided.</p>
<p>(issue imported from #M10924)</p> TYPO3 Core - Bug #17981 (Closed): Add some more functionality to new AJAX interface in the TYPO3 ...http://forge.typo3.org/issues/179812008-01-11T11:58:59ZOliver Haderoliver.hader@typo3.org
This bug report concerns the following:
<ul>
<li>changing namespace of ajaxIds from e.g. "foldertree_ExpandCollapse" to "SC_alt_db_navframe::ExpandCollapse" </li>
<li>add TYPO3AJAX::setContent($content) to completely overwrite the data array</li>
<li>add the possibility to use a non-associative content array by addContent(null, 'whatever')</li>
<li>add the missing format types "jsonhead" and "jsonbody" </li>
<li>fix some phpdoc related things</li>
</ul>
<p>(issue imported from #M7124)</p>