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 - Feature #89762 (New): Add pagination to forms listhttp://forge.typo3.org/issues/897622019-11-24T12:17:48ZMathias Brodalambrodala@pagemachine.de
<p>There should be a pagination in the forms list to not have the module die on long form lists or folders with many files. As a side effect management for editors will be simpler since long lists are barely manageable.</p>
<p>Before this <a class="issue tracker-2 status-8 priority-4 priority-default child" title="Feature: Show storage list for selection (Under Review)" href="http://forge.typo3.org/issues/89760">#89760</a> should be done since currently all forms are loaded into a single list after loading them from all storage folders which would make a pagination pointless.</p> TYPO3 Core - Bug #87328 (New): "Make new translation of this page" can create invalid page transl...http://forge.typo3.org/issues/873282019-01-04T14:05:41ZMathias Brodalambrodala@pagemachine.de
<p>Since <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: BE page module => 'Make new translation of this page' doesn't use command localize to create tran... (Closed)" href="http://forge.typo3.org/issues/81345">#81345</a> the <strong>Make new translation of this page</strong> feature within the page module directly creates localizations instead of opening the edit view for page translations.</p>
<p>This can lead to invalid page translations if e.g. the <code>title</code> has been configured to be empty in translations (unset <code>l10n_mode</code>) and thus must be filled by editors explicitly. In this case the edit view is shown correctly with errors after localization but one can simply close the view without additional prompt or action. After this the translation exists without title which in itself can lead to further issues. When trying to save instead a proper dialog is shown mentioning the invalid fields.</p> TYPO3 Core - Bug #87035 (Closed): AdditionalFactoryConfiguration.php not used anymorehttp://forge.typo3.org/issues/870352018-11-29T10:32:53ZMathias Brodalambrodala@pagemachine.de
<p>The <code>typo3conf/AdditionalFactoryConfiguration.php</code> file can be used to provide additional default values to be put into <code>typo3conf/LocalConfiguration.php</code> upon TYPO3 setup.</p>
<p>However, this file is not used anymore since TYPO3v9 and currently must be placed one level above instead, so basically next to <code>index.php</code>.</p>
<p>This is a regression introduced with <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Replace further path usages with Environment API (Closed)" href="http://forge.typo3.org/issues/85560">#85560</a>.</p> TYPO3 Core - Bug #84973 (Closed): Cannot delete invalid Scheduler taskhttp://forge.typo3.org/issues/849732018-05-11T17:39:24ZMathias Brodalambrodala@pagemachine.de
<p>When trying to delete an invalid Scheduler task (e.g. due to the related code being removed) an error occurs:</p>
<pre>
Fatal error: TYPO3\CMS\Scheduler\Scheduler::isValidTaskObject(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition &quot;<Task>&quot; of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /.../typo3/sysext/scheduler/Classes/Scheduler.php on line 449
</pre> TYPO3 Core - Bug #84491 (Closed): Breaks field in EXT:styleguidehttp://forge.typo3.org/issues/844912018-03-20T09:21:36ZMathias Brodalambrodala@pagemachine.de
<p>EXT:styleguide, elements basic > text_17 breaks with</p>
<blockquote>
<p>Argument 2 passed to TYPO3\CMS\Backend\Controller\Wizard\TableController::configurationStringToArray() must be of the type integer, null given, called in /.../typo3/sysext/backend/Classes/Controller/Wizard/TableController.php on line 496</p>
</blockquote> TYPO3 Core - Bug #84178 (Closed): Cannot create but upload file with "@" in namehttp://forge.typo3.org/issues/841782018-03-08T14:45:32ZMathias Brodalambrodala@pagemachine.de
<p>In FAL there are at least two different ways to create files which apparently do not apply the same sanitation/validation rules to file names.</p>
<p>This can be verified easily in the <strong>Filelist</strong> module: if you try to upload a file called <strong><a class="email" href="mailto:foo@bar.txt">foo@bar.txt</a></strong> everything simply works.</p>
<p>But if you create a file called <strong><a class="email" href="mailto:foo@bar.txt">foo@bar.txt</a></strong> a <code>ResourceDoesNotExistException</code> is thrown:</p>
<pre>
#1329647780: Object with identifier "1:/foo@bar.txt" does not exist in storage
</pre>
<p>When opening the file list once more after this, an error flash message is shown which says <em>File name "<a class="email" href="mailto:foo@bar.txt">foo@bar.txt</a>" was not allowed!</em>.</p>
<p>This behavior can be traced back to these two code paths:</p>
<ul>
<li><code>LocalDriver::addFile()</code> calls <code>LocalDriver::sanitizeFileName()</code> which accepts <strong><a class="email" href="mailto:foo@bar.txt">foo@bar.txt</a></strong> (this is used e.g. for file uploads)</li>
<li><code>LocalDriver::createFile()</code> calls <code>AbstractDriver::isValidFilename()</code> which denies <strong><a class="email" href="mailto:foo@bar.txt">foo@bar.txt</a></strong> (this is used for everything else)</li>
</ul> 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 - Feature #83175 (New): Add option to disable "Move page" prompthttp://forge.typo3.org/issues/831752017-11-30T15:04:43ZMathias Brodalambrodala@pagemachine.de
<p>The new page tree shows a modal prompt when a page was moved to ask for Move, Copy or Cancel.</p>
<p>Since this slows down editing workflows considerably there should be an option to disable this and default to move and copy when pressing the Ctrl key during drag-and-drop.</p>
<p>Cancelling everything via the Esc key during drag would be the icing on the cake. ;-)</p> TYPO3 Core - Feature #82019 (New): Accept array instead of CSV in TCAhttp://forge.typo3.org/issues/820192017-08-01T14:14:26ZMathias Brodalambrodala@pagemachine.de
<p>There are various locations in TCA which require a CSV string of values, e.g. <code>ctrl/searchFields</code> or <code>types/N/showitem</code>.</p>
<p>To make it easer to handle this e.g. in Git one can use a multi-line string or the <code>implode()</code> function to convert an array of strings back to an CSV string.</p>
<p>Arrays of strings should be supported natively here to streamline TCA config.</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 - Feature #61171 (Closed): Add generic data-* attributehttp://forge.typo3.org/issues/611712014-08-25T11:26:16ZMathias Brodalambrodala@pagemachine.de
<p><a href="https://forge.typo3.org/projects/package-typo3-fluid/repository/revisions/8f7bd506e06e62c4f28428f47d14a4e4f9ea8977" class="external">This change</a> should be backported from TYPO3.Fluid to enable easier integration of HTML5 data attributes.</p> TYPO3 Core - Bug #60913 (Closed): Cannot edit lazy loaded objectshttp://forge.typo3.org/issues/609132014-08-12T14:01:52ZMathias Brodalambrodala@pagemachine.de
<p>Lazy loaded objects cannot be edited through Fluid forms.</p>
<p>Given the following form:</p>
<pre>
<f:form name="bar" object="{foo.bar}">
<f:form.textfield property="propertyOfBar"/>
<f:form.submit value="Update"/>
</f:form>
</pre>
<p>If "bar" of "foo" is an instance of <code>TYPO3\CMS\Extbase\Persistence\Generic\LazyLoadingProxy</code> the initial check in <code>TYPO3\CMS\Fluid\ViewHelpers\Form\AbstractFormViewHelper::renderHiddenIdentityField</code> fails because the <code>LazyLoadingProxy</code> instance cannot be an instance of <code>TYPO3\CMS\Extbase\DomainObject\AbstractDomainObject</code>. This prevents the hidden identity field from being rendered which makes editing impossible.</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 - Feature #51556 (Closed): Add custom data to errors in validatorshttp://forge.typo3.org/issues/515562013-08-30T11:16:05ZMathias Brodalambrodala@pagemachine.de
<p>It would be useful if validators could add custom data to errors which can be used to give additional hints to the user.</p>
<p>This could for example be the specific article name and amount missing until its minimum order amount is fulfilled. Error messages outputted in the form then could use this additional data to be as specific as possible.</p>