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 #85620 (Closed): Add hint about missing pages to Site Configuration modulehttp://forge.typo3.org/issues/856202018-07-23T14:46:00ZMathias Brodalambrodala@pagemachine.de
<p>If there are no pages, the Site <em>Configuration</em> module only shows some table headers without any hint, that first at least one page needs to be added through the <em>Page</em> module. There should be a hint similar to the <em>Redirects</em> module.</p> TYPO3 Core - Feature #84713 (Closed): Add option to get a single processed form valuehttp://forge.typo3.org/issues/847132018-04-13T16:51:03ZMathias Brodalambrodala@pagemachine.de
<p>Currently the <code>RenderAllFormValuesViewHelper</code> is the only option to get processed form values. There is no way to selectively retrieve the processed value of a single form element which would be useful e.g. for custom email templates which don't need all form values or need a custom order and placement of form values.</p>
<p>One option would be a <code>RenderFormValueViewHelper</code>. The API method <code>FormDefinition::getElementByIdentifier()</code> could be used internally to retrieve a requested form element. The value processing would be moved to a central location for both of these viewhelpers.</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 #84466 (Closed): Add separate HTTPS security check to reports modulehttp://forge.typo3.org/issues/844662018-03-18T11:27:03ZMathias Brodalambrodala@pagemachine.de
<p>The reports module needs to have a separate HTTPS security check independent from the suggestion added by <code>rsaauth</code> which is bound to be removed sooner or later. Using TYPO3 (or any website) without HTTPS is deemed insecure.</p> TYPO3 Core - Task #77891 (Closed): Add Forger RST utility link to changelog HowTohttp://forge.typo3.org/issues/778912016-09-09T09:34:01ZMathias Brodalambrodala@pagemachine.de
<p>The <a href="https://docs.typo3.org/typo3cms/extensions/core/Changelog/Howto.html" class="external">changelog HowTo</a> should contain a link to the Forger RST utility.</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 - Feature #69711 (Closed): Add deprecation feature to IconFactoryhttp://forge.typo3.org/issues/697112015-09-12T12:19:37ZMathias Brodalambrodala@pagemachine.de
<p>The <code>IconFactory</code> should be able to handle deprecated icons by logging a deprecation message and optionally using a registered replacement icon instead.</p> TYPO3 Core - Feature #63561 (Closed): Add stdWrap strtotimehttp://forge.typo3.org/issues/635612014-12-04T12:14:25ZMathias Brodalambrodala@pagemachine.de
<p>To complement the existing <code>date</code> and <code>strftime</code> which allow converting timestamps to a formatted date the counterpart <code>strtotime</code> should be added to <code>stdWrap</code>. This allows for processing like this:</p>
<pre>
next_weekday = TEXT
next_weekday {
data = GP:selected_date
strtotime = + 2 weekdays
strftime = %Y-%m-%d
}
</pre>
<p>For <code>GP:selected_date</code> having a value <code>2014-12-04</code> this would output <code>2014-12-08</code>.</p> TYPO3 Core - Feature #62960 (Closed): Add hook for mailer initializationhttp://forge.typo3.org/issues/629602014-11-14T16:58:17ZMathias Brodalambrodala@pagemachine.de
<p>The <code>TYPO3\CMS\Core\Mail\Mailer</code> class is the central instance for mailing and should have a hook called upon initialization.</p>
<p>This hook could be used e.g. to register Swift mailer plugins at runtime.</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>