TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-04-18T11:13:08ZTYPO3 Forge
Redmine TYPO3 Core - Task #88172 (Rejected): Add scalar/return type hints in CommandMaphttp://forge.typo3.org/issues/881722019-04-18T11:13:08ZMathias Brodalambrodala@pagemachine.de
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Exception on sendToStage with User TsConfig option "options.workspaces.changeStageMode = pages" (Closed)" href="http://forge.typo3.org/issues/87046">#87046</a> was caused by a type mismatch which should be prevented with <code>strict_types</code> and scalar/return type hints.</p> TYPO3 Core - Task #85358 (Rejected): Privately declare deprecated public methods/propertieshttp://forge.typo3.org/issues/853582018-06-23T10:57:48ZMathias Brodalambrodala@pagemachine.de
<p>There are two traits <code>PublicMethodDeprecationTrait</code> and <code>PublicPropertyDeprecationTrait</code>. These require defining a property map which methods/properties should be handled.</p>
<p>To ensure deprecations continue to work even in classes extending these and overwriting the property map the property map must be declared <code>private</code>:</p>
<p><a class="external" href="https://3v4l.org/Ejdue">https://3v4l.org/Ejdue</a></p> TYPO3 Core - Bug #85320 (Rejected): Translation arguments not inserted into default valuehttp://forge.typo3.org/issues/853202018-06-20T16:37:57ZMathias Brodalambrodala@pagemachine.de
<p>Given is a form with a default value for a form element label which includes placeholders like <code>%s</code> and <a href="https://docs.typo3.org/typo3cms/extensions/form/Concepts/FrontendRendering/Index.html#form-element-translation-arguments-are-supported" class="external">translation arguments via TypoScript</a>.</p>
<p>When viewing the page with the form in English then the translation arguments are not inserted into the form element label. Instead the default value for the label is shown including placeholders.</p> TYPO3 Core - Task #84462 (Rejected): RSA encryption hook should be moved from EXT:rsaauth to EXT:...http://forge.typo3.org/issues/844622018-03-18T10:08:32ZMathias Brodalambrodala@pagemachine.de
<p>The <code>rsaauth</code> extension currently registers a hook for the <code>felogin</code> extension for RSA encrypted login form submission.</p>
<p>This should be moved to the <code>felogin</code> extension instead.</p> TYPO3 Core - Bug #83246 (Rejected): TCA "check" eval "maximumRecordsChecked*" not implemented any...http://forge.typo3.org/issues/832462017-12-07T10:56:21ZMathias Brodalambrodala@pagemachine.de
<p>The two <code>eval</code> options <code>maximumRecordsChecked</code> and <code>maximumRecordsCheckedInPid</code> mentioned in the <a href="https://docs.typo3.org/typo3cms/TCAReference/ColumnsConfig/Type/Check.html#eval" class="external">docs for TCA type <code>check</code></a> are not implemented anymore. This might have been dropped with the FormEngine refactor.</p> TYPO3 Core - Task #76766 (Rejected): Enable Recycler by defaulthttp://forge.typo3.org/issues/767662016-06-24T09:14:51ZMathias Brodalambrodala@pagemachine.de
<p>One part of a good user experience is the safety of undoing destructive operations. Within TYPO3 this can be achieved for a lot of locations with the Recycler module.</p>
<p>Thus I suggest to enable it by default for new installations.</p> TYPO3 Core - Feature #73474 (Rejected): Disconnect slots from signalshttp://forge.typo3.org/issues/734742016-02-16T10:45:24ZMathias Brodalambrodala@pagemachine.de
<p>The Extbase signal/slot <code>Dispatcher</code> should allow for disconnecting slots from signals.</p>
<p>With this, one can cleanly prevent certain slots from being invoked instead of resorting to hacks.</p> TYPO3 Core - Task #73069 (Rejected): Rename extension:dumpclassloadinginformation commandhttp://forge.typo3.org/issues/730692016-02-01T15:58:04ZMathias Brodalambrodala@pagemachine.de
<p>The <code>extension:dumpclassloadinginformation</code> is hard to type and remember and should be renamed to <code>extension:dumpautoload</code> to be in line with <code>composer dumpautoload</code>.</p> TYPO3 Core - Feature #71038 (Rejected): Install extensions with dependencies on CLIhttp://forge.typo3.org/issues/710382015-10-26T14:31:03ZMathias Brodalambrodala@pagemachine.de
<p>The <code>ExtensionCommandController</code> provides the <code>extension:install</code> command which can be used to install extensions via CLI while ignoring all dependencies.</p>
<p>A switch like <code>--with-dependencies</code> could be added which triggers installation of all extensions required by the extension to install. Of course these must exist when invoking this command. (Which is already given if the extension was fetched via Composer.)</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 - 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 - Feature #61066 (Rejected): Configuration per application contexthttp://forge.typo3.org/issues/610662014-08-19T15:00:14ZMathias Brodalambrodala@pagemachine.de
<p>TYPO3 Flow allows for different configuration per application context (even subcontexts). The same should be supported in CMS, too.</p> TYPO3 Core - Feature #60546 (Rejected): Flash message support for command controllershttp://forge.typo3.org/issues/605462014-07-24T21:42:41ZMathias Brodalambrodala@pagemachine.de
<p>Command controllers should be able to create flash messages just like action controllers.</p>
<p>Displaying them in the backend if executed as Scheduler task should be pretty straightforward as every backend module can do this.</p>
<p>Displaying them in CLI would take quite a lot of work unless the Symfony console is merged with <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: [FEATURE] Integrate Symfony/Console into CommandController (Closed)" href="http://forge.typo3.org/issues/59606">#59606</a>. In that case Symfony's native support for <a href="http://symfony.com/doc/current/components/console/helpers/formatterhelper.html#print-messages-in-a-block" class="external">outputting a message block</a> with appropriate colors should do the trick.</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 - Bug #52888 (Rejected): FIRST_INSTALL file is ignoredhttp://forge.typo3.org/issues/528882013-10-16T13:40:24ZMathias Brodalambrodala@pagemachine.de
<p>The <code>FIRST_INSTALL</code> file which may be used to have the TYPO3 installer automatically create the <code>ENABLE_INSTALL_TOOL</code> file is completely ignored in the new installer. In fact, a file search yields nothing.</p>