TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-04-05T16:58:21ZTYPO3 Forge
Redmine TYPO3 Core - Task #84630 (Closed): Sort list of Composer dependencieshttp://forge.typo3.org/issues/846302018-04-05T16:58:21ZMathias Brodalambrodala@pagemachine.de
<p>Composer has an option to <a href="https://getcomposer.org/doc/06-config.md#sort-packages" class="external">sort packages</a> which makes for a predictable list of dependencies. This should be used.</p> TYPO3 Core - Task #83417 (Closed): Cannot click label to activate checkbox in Internet Explorer &...http://forge.typo3.org/issues/834172017-12-22T17:45:12ZMathias Brodalambrodala@pagemachine.de
<p>Checkbox fields of the form extension cannot be activated by clicking on their label in Internet Explorer and Edge.</p>
<p>This is a <a href="https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11345957/" class="external">known and confirmed issue</a></p>
<p>Background for the bug:</p>
<p>The <a href="https://www.w3.org/TR/html51/sec-forms.html#element-attrdef-label-for" class="external">specs for the <code>for</code> attribute</a> say:</p>
<blockquote>
<p>If the for attribute is not specified, but the label element has a labelable element descendant, then the first such descendant in tree order is the label element’s labeled control.</p>
</blockquote>
<p>The definition of a <a href="https://www.w3.org/TR/html51/sec-forms.html#labelable-element" class="external">labelable element</a> is:</p>
<blockquote>
<p>... <input> (if the type attribute is not in the hidden state) ...</p>
</blockquote>
<p>Internet Explorer and Edge ignore this and see the hidden input added to every checkbox field in Fluid forms as element to aim at.</p> TYPO3 Core - Bug #80436 (Closed): Linkhandler record browsing not working with CKEditorhttp://forge.typo3.org/issues/804362017-03-24T18:01:00ZMathias Brodalambrodala@pagemachine.de
<p>Apparently the linkhandler record browsing introduced with <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Integrate linkhandler into core (Closed)" href="http://forge.typo3.org/issues/79626">#79626</a> is not working with CKEditor.</p>
<p>Internally CKEditor always passes <code>tt_content</code> as table in <code>BrowseLinksController::getUrlParameters</code> which in turn prevents record listing due to a check in <code>AbstractDatabaseRecordList::generateList()</code> which disallows tables aside from <code>$this->table</code> filled from <code>$_GET['table']</code>.</p> TYPO3 Core - Bug #76374 (Closed): Select trees not rendered on inline recordshttp://forge.typo3.org/issues/763742016-05-30T12:50:16ZMathias Brodalambrodala@pagemachine.de
<p>Since the change in <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Flexform select rendermode tree doesn't respect collapsed nodes (Closed)" href="http://forge.typo3.org/issues/75519">#75519</a> the tree rendering of TCA <code>select</code> is broken for records managed <code>inline</code>.</p>
<p>The change was determined via Git bisecting between TYPO3 6.2.21 and 6.2.22.</p>
<p>See the attached test extension for an example. It adds a single <code>inline</code> relation field to the <code>sys_category</code> table which uses a tree for its <code>parent</code> field. Try to add a relation and see that the tree of the <code>parent</code> field is missing.</p> TYPO3 Core - Bug #69816 (Closed): PageTS ignored for default language in selectorhttp://forge.typo3.org/issues/698162015-09-15T12:26:43ZMathias Brodalambrodala@pagemachine.de
<p>The language selector (usually <code>sys_language_uid</code>) in records shows entries for every language created as <code>sys_language</code> record if possible.</p>
<p>The default language (UID 0) does not show the icon set in <code>mod.SHARED.defaultLanguageFlag</code> and doesn't override the label with the one set in <code>mod.SHARED.defaultLanguageLabel</code>.</p> TYPO3 Core - Bug #69790 (Rejected): Page tree hidden after going back from syslog linkhttp://forge.typo3.org/issues/697902015-09-14T15:38:46ZMathias Brodalambrodala@pagemachine.de
<p>The system information menu in the header of the backend shows a link to the Log module in case there are errors. Upon clicking this link, the page tree component is hidden since it's not used in the Log module.</p>
<p>If you go back via the browser back button afterwards, the page tree stays hidden.</p>
<p>The page tree should be displayed again instead.</p> TYPO3 Core - Bug #68640 (Closed): Fix new content element wizard links click areahttp://forge.typo3.org/issues/686402015-07-30T10:32:18ZMathias Brodalambrodala@pagemachine.de
<p>Recently a regression has been introduced wrt the click area of links in the new content element wizard, see <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Format new content element wizard links as inline-block (Closed)" href="http://forge.typo3.org/issues/56063">#56063</a> for details and <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Port Content Element Wizard to Bootstrap (Closed)" href="http://forge.typo3.org/issues/64892">#64892</a> for a previous regression.</p> TYPO3 Core - Feature #60822 (Closed): Get class tag values via reflectionhttp://forge.typo3.org/issues/608222014-08-06T12:09:14ZMathias Brodalambrodala@pagemachine.de
<p>The <code>ReflectionService</code> currently allows getting tag values for properties and methods. The same should be available for classes since the data is already collected in <code>ReflectionService::reflectClass()</code> anyways.</p>
<p>Suggestion: add <code>ReflectionService::getClassTagsValues($className)</code> and <code>ReflectionService::getClassTagValues($className, $tag)</code> and use the existing data.</p> TYPO3 Core - Feature #59899 (Rejected): Clear system caches selectivelyhttp://forge.typo3.org/issues/598992014-06-26T11:57:02ZMathias Brodalambrodala@pagemachine.de
<p>There should be a way to selectively clear system caches.</p>
<p>This would speed up development tremendously, e.g. if one needs to clear the database query cache but doesn't care about any of the other caches.</p>
<p>A possible solution would be either a dialog with checkboxes or a submenu with a list of caches.</p> TYPO3 Core - Task #56063 (Closed): Format new content element wizard links as inline-blockhttp://forge.typo3.org/issues/560632014-02-18T09:01:38ZMathias Brodalambrodala@pagemachine.de
<p>The links within the new content element wizard are currently rendered as default inline elements which allows only clicking on the actual text. Even clicking between title and description does not work.</p>
<p>The solution is simple: format these links as inline-block to make the whole link clickable.</p> TYPO3 Core - Feature #55757 (Closed): Add PageTSconfig analyzerhttp://forge.typo3.org/issues/557572014-02-07T12:26:47ZMathias Brodalambrodala@pagemachine.de
<p>Similar to what the Template Analyzer does for the TypoScript Object Browser an additional mod function for analyzing PageTS would be useful.</p>
<p>ATM one can only see the currently parsed PageTS for pages. It is impossible to find out where and how this configuration was set which makes debugging for larger sites harder than it should be.</p>
<p>A PageTSconfig analyzer could help here by showing the content of added PageTS files and dynamically added sections like <code>defaultPageTSconfig</code>.</p> TYPO3 Core - Bug #55153 (Closed): Duplicated translation entry for clear cache menu pageshttp://forge.typo3.org/issues/551532014-01-20T09:20:06ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="changeset" title="[TASK] Cache menu needs clear namings and permissions With the introduction of the grouping mech..." href="http://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/1b83cad80a4cffe054faea3ec1f30d7b18389942">1b83cad</a> the clear cache menu items where reworked. This however introduced a duplicated translation entry for the "pages" item. (<code>rm.clearCacheMenu_pages</code>)</p> TYPO3 Core - Task #53455 (Closed): Update backend page titlehttp://forge.typo3.org/issues/534552013-11-08T15:22:28ZMathias Brodalambrodala@pagemachine.de
<p>Since the introduction text of the install tool has been updated recently for 6.2 I think it is about time the page title of the backend is also updated to reflect the brand change. Thus "TYPO3 <version>" becomes "TYPO3 CMS <version>".</p> TYPO3 Core - Bug #53188 (Closed): REDIRECT_TYPO3_DISABLE_CORE_UPDATER ignoredhttp://forge.typo3.org/issues/531882013-10-29T08:38:13ZMathias Brodalambrodala@pagemachine.de
<p>Using Apache mod_rewrite in certain setups makes environment variables from original requests available in the target request as <code>REDIRECT_<envvar></code>, thus setting <code>TYPO3_DISABLE_CORE_UPDATER</code> becomes <code>REDIRECT_TYPO3_DISABLE_CORE_UPDATER</code>.</p>
<p>The latter is currently not considered by TYPO3, thus the core updater cannot be disabled via the environment variable and the mentioned setup.</p>
<p>See <a href="http://stackoverflow.com/a/9406994" class="external">this Stackoverflow</a> post for an explanation and <a href="https://github.com/apache/httpd/blob/e1fac1db26/modules/http/http_request.c#L389" class="external">link to the Apache source code</a>.</p> TYPO3 Core - Bug #52880 (Closed): Class "\extDirect_DataProvider_BackenduserSettings" not foundhttp://forge.typo3.org/issues/528802013-10-16T10:00:20ZMathias Brodalambrodala@pagemachine.de
<p>Trying to create a template record on a fresh 6.2 beta1 installation fails:</p>
<pre>
Fatal error: Class '\extDirect_DataProvider_BackenduserSettings' not found in .../typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4149
</pre>
<p>A file search for this class name yields two <code>makeInstance</code> calls:</p>
<ul>
<li>typo3\sysext\backend\Classes\InterfaceState\ExtDirect\DataProvider.php:46 (<code>__construct()</code>)</li>
<li>typo3\sysext\backend\Classes\Tree\Pagetree\ExtdirectTreeCommands.php:361 (<code>addRootlineOfNodeToStateHash()</code>)</li>
</ul>
<p>It seems like the correct path is <code>\TYPO3\CMS\Backend\User\ExtDirect\BackendUserSettingsDataProvider</code> instead.</p>