TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-12-07T09:29:03ZTYPO3 Forge
Redmine TYPO3 Core - Task #96267 (New): Add dedicated error for class construction without dependencieshttp://forge.typo3.org/issues/962672021-12-07T09:29:03ZMathias Brodalambrodala@pagemachine.de
<p>Right now if <code>GeneralUtility::makeInstance()</code> is used to construct a class which uses constructor dependency injection and has not being marked as <code>public</code>, a low-level <code>\ArgumentCountError</code> is thrown by PHP.</p>
<p>This should be improved by catching this case and replacing the error with a custom one (e.g. <code>MissingDependenciesError</code>). Either that custom error already hints at possible solutions or its dedicated error code is used to link to the docs with more details. The docs could then suggest to mark the class as <code>public</code> or manually pass the dependencies as arguments.</p> TYPO3 Core - Task #89866 (Closed): Use new Typo3Copyright API everywherehttp://forge.typo3.org/issues/898662019-12-05T17:08:33ZMathias Brodalambrodala@pagemachine.de
<p>After <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Move Copyright information generation out of TYPO3 Backend (Closed)" href="http://forge.typo3.org/issues/89756">#89756</a> there are still some locations which directly use e.g. the <code>TYPO3_copyright_year</code> constant and should be migrated to the <code>Typo3Copyright</code> class.</p> TYPO3 Core - Epic #89759 (New): Performance improvements in Forms modulehttp://forge.typo3.org/issues/897592019-11-24T12:08:23ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Epic #89731 (New): Configuration streamlininghttp://forge.typo3.org/issues/897312019-11-21T18:55:56ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #88220 (Accepted): Documentation for "Allow multiple recipients in EmailFinisher"http://forge.typo3.org/issues/882202019-04-26T12:35:22ZMathias Brodalambrodala@pagemachine.de
<p>The EXT:form documentation (setup/YAML) must be updated for <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow multiple recipients in EmailFinisher (Closed)" href="http://forge.typo3.org/issues/80420">#80420</a>.</p> TYPO3 Core - Task #86916 (Closed): Use button group for Create/Filter buttons above page treehttp://forge.typo3.org/issues/869162018-11-13T11:54:37ZMathias Brodalambrodala@pagemachine.de
<p>Since the buttons for <em>Create new pages</em> and filtering are mutually exclusive they behave like a <a href="https://getbootstrap.com/docs/3.3/components/#btn-groups" class="external">button group</a>. Thus they should be styled as such:</p>
<p><img src="http://forge.typo3.org/attachments/download/33920/button-group.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #85619 (Closed): Streamline package interdependencieshttp://forge.typo3.org/issues/856192018-07-23T14:39:12ZMathias Brodalambrodala@pagemachine.de
<p>Currently a lot of <code>typo3/cms-*</code> packages have hidden dependencies on other <code>typo3/cms-*</code> packages, e.g. by using views and wizards defined in these packages. For example the <em>Redirects</em> module (<code>typo3/cms-redirects</code>) fails with an exception if <code>typo3/cms-recordlist</code> is not installed.</p>
<p>It should be checked where dependencies are still missing and should be declared explicitly in each Composer manifest.</p> TYPO3 Core - Task #85031 (Closed): Use ServerRequestInterface in ImportExportControllerhttp://forge.typo3.org/issues/850312018-05-17T11:12:52ZMathias Brodalambrodala@pagemachine.deTYPO3 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 #84361 (Closed): Use modal-based new content element wizard everywherehttp://forge.typo3.org/issues/843612018-03-16T17:06:33ZMathias Brodalambrodala@pagemachine.de
<p>There is a modal-based wizard for creating new content elements accessible from the new record view (<em>Click here for wizard!</em>).</p>
<p>This can also be enabled for the list module through some PageTS option.</p>
<p>Instead of hiding this superior UI behind some unknown option this wizard should be enabled everywhere and the option should be removed. Afterwards some code can be deprecated and eventually removed.</p> TYPO3 Core - Task #69760 (Closed): Add cache to IconFactoryhttp://forge.typo3.org/issues/697602015-09-13T14:54:26ZMathias Brodalambrodala@pagemachine.de
<p>The <code>IconFactory</code> should have a persistent cache to store the rendered icon markup.</p> TYPO3 Core - Task #69748 (Rejected): Use IconRegistry API to register iconshttp://forge.typo3.org/issues/697482015-09-13T10:45:19ZMathias Brodalambrodala@pagemachine.de
<p>Currently icons of all shipped TYPO3 extensions have their icons registered directly within the <code>IconRegistry</code>. This should be refactored to use our own API for registering icons in each extension. (aka "Eating your own dog food".)</p>
<p>This should be done last after all icons have been moved to <code>IconRegistry</code>/<code>IconFactory</code>.</p> TYPO3 Core - Task #59820 (Closed): Re-sync Extbase with TYPO3 Flow wherever possiblehttp://forge.typo3.org/issues/598202014-06-23T17:07:20ZMathias Brodalambrodala@pagemachine.de
<p>From time to time I stumble upon bugs in Extbase which apparently where fixed in TYPO3 Flow already. These fixes should have been backported to Extbase to keep it in sync.</p>
<p>Thus I'd like to request a re-sync of Extbase with TYPO3 Flow wherever it is possible.</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 - 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>