TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-07T10:59:45ZTYPO3 Forge
Redmine TYPO3 Core - Feature #103072 (New): Manage translation DB fieldshttp://forge.typo3.org/issues/1030722024-02-07T10:59:45ZMathias Brodalambrodala@pagemachine.de
<p>Currently the TCA of TYPO3 knows these <code>ctrl</code> options to enable and manage translation behavior for tables:</p>
<p>- <code>languageField</code> (<code>sys_language_uid</code> by convention)<br />- <code>transOrigPointerField</code> (<code>l10n_parent</code> by convention, <code>l18n_parent</code> in <code>tt_content</code>)<br />- <code>translationSource</code>(<code>l10n_source</code> by convention)<br />- <code>transOrigDiffSourceField</code> (<code>l10n_diffsource</code> by convention, <code>l18n_diffsource</code> in <code>tt_content</code>)</p>
<p>Each of these have 2 purposes:</p>
<p>1. Enable translations or a related feature<br />2. Tell TYPO3 which DB field to use in queries</p>
<p>This by itself is a problem but the main question is whether the names of these DB fields need to be configurable at all.</p>
<p>There are recently a lot of consolidations and simplifications in TCA. The same could be applied here:</p>
<p>- Turn these options from <code>string</code> to <code>bool</code>, thus only enable/disable the feature. TYPO3 would then use fixed DB field names and thus fully manage these.<br />- Consolidate/merge these options with better and clearer names, e.g. <code>'enableTranslations' => true</code>, <code>'trackTranslationDifferences' => true</code> or similar.</p> TYPO3 Core - Feature #96055 (Closed): Let the command "language:update" issue warningshttp://forge.typo3.org/issues/960552021-11-23T09:57:29ZMathias Brodalambrodala@pagemachine.de
<p>Currently the CLI command <code>language:update</code> fails hard if translations could not be fetched. (No matter if for a private extension or a public extension without translations, see <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: CLI command language:update fails due to packages without translation packs (Closed)" href="http://forge.typo3.org/issues/95700">#95700</a>)</p>
<p>It would be useful if these where warnings instead by default since failed translations are updates are usually not that important and low priority.</p>
<p>An optional CLI option could be added to turn these warnings into errors again which would be useful for CI systems.</p> TYPO3 Core - Feature #89417 (New): Snippets/components in form definitionshttp://forge.typo3.org/issues/894172019-10-15T09:58:57ZMathias Brodalambrodala@pagemachine.de
<p>It would be useful if the Form framework did support snippets/components. These could then be referenced in a regular form definition and would be inserted on the fly as soon as the form is built.</p>
<p>Obviously some kind of parameter support would be necessary here to make it easy to e.g. set the name for a form field provided by a snippet.</p>
<p>Maybe this could be achieved with <a class="issue tracker-2 status-5 priority-4 priority-default closed child parent" title="Feature: Support "imports" within forms form definition files (Closed)" href="http://forge.typo3.org/issues/84204">#84204</a> and YAML anchors/references.</p> 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 #84580 (Closed): "Stop page tree" icon/label unclearhttp://forge.typo3.org/issues/845802018-04-03T12:24:52ZMathias Brodalambrodala@pagemachine.de
<p>The option <strong>Stop page tree</strong> which can be enabled for any page has an unclear icon/label.</p>
<p>The icon is a very simple red "+" and the label only reads <strong>Stop page tree</strong>. There is no clear indication that this option prevents the page tree to render the subtree of the page where this option was enabled.</p>
<p>A better icon/label/indication could be added here.</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 - 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 - 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 #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 - 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 - 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>