TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-07-19T16:29:10ZTYPO3 Forge
Redmine TYPO3 Core - Bug #88806 (Closed): "Test Mail Setup" broken: Too few arguments to function EventDi...http://forge.typo3.org/issues/888062019-07-19T16:29:10ZMathias Brodalambrodala@pagemachine.de
<p>Using <strong>Test Mail Setup</strong> in the <strong>Environment</strong> module currently fails with an error which can be found in the TYPO3 logfile:</p>
<code>
Fri, 19 Jul 2019 16:25:30 +0200 [CRITICAL] request="262570147be62" component="TYPO3.CMS.Core.Error.DebugExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: Too few arguments to function TYPO3\CMS\Core\EventDispatcher\EventDispatcher::__construct(), 0 passed in /.../typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 3450 and exactly 1 expected | ArgumentCountError thrown in file /.../typo3/sysext/core/Classes/EventDispatcher/EventDispatcher.php in line 35. Requested URL: http://.../typo3/install.php?install[controller]=environment&install[context]=backend - {"TYPO3_MODE":"BE","exception":{}}
</code>
<p>For some reason dependency injection does not seem to be working properly here.</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 #87149 (Closed): Cannot debug Generator outputhttp://forge.typo3.org/issues/871492018-12-13T15:08:23ZMathias Brodalambrodala@pagemachine.de
<p>If <code>DebuggerUtility::var_dump()</code> is used on a <code>\Generator</code>, an error occurs:</p>
<blockquote>
<p>Cannot rewind a generator that was already run</p>
</blockquote>
<p>This is due to the implicit <code>rewind()</code> call within <code>DebuggerUtility::renderCollection()</code> which should be avoided for generators.</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 #85988 (Closed): @cli annotation deprecated without replacementhttp://forge.typo3.org/issues/859882018-08-27T11:10:51ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate @cli annotation (Closed)" href="http://forge.typo3.org/issues/85977">#85977</a> the <code>@cli</code> annotation has been deprecated without replacement but hinting at a successor in TYPO3v10. No matter if and when this will really happen we cannot do a deprecation without a replacement so this change needs to be reverted.</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 - 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 #84465 (Closed): "Status report" broken because of invalid routehttp://forge.typo3.org/issues/844652018-03-18T10:52:13ZMathias Brodalambrodala@pagemachine.de
<p>The <strong>Status report</strong> within the <strong>Reports</strong> module throws an exception due to an invalid route identifier:</p>
<blockquote>
<p>#1476050190: Unable to generate a URL for the named route "system_ReportsTxreportsm1" because this route was not found.</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 - Bug #82518 (Closed): Broken composite form element check in RenderAllFormValuesViewH...http://forge.typo3.org/issues/825182017-09-20T13:51:32ZMathias Brodalambrodala@pagemachine.de
<p>The check for composite form elements in the <code>RenderAllFormValuesViewHelper</code> is broken:</p>
<pre>
if (
!$element instanceof FormElementInterface
|| $element->getType() === 'Honeypot'
|| (
isset($renderingOptions['_isCompositeFormElement'])
&& $renderingOptions['_isCompositeFormElement'] = true
)
) {
continue;
}
</pre>
<p>This was implicitly fixed for master in <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: EXT:form - do not show hidden field on confirmation page (Closed)" href="http://forge.typo3.org/issues/81770">#81770</a>.</p> TYPO3 Core - Bug #73035 (Closed): Broken path for GlobalDebugFunctions autoload in core extensionhttp://forge.typo3.org/issues/730352016-01-30T17:42:20ZMathias Brodalambrodala@pagemachine.de
<p>The <code>core</code> extension specifies a wrong path in its <code>composer.json</code> for autoloading the <code>GlobalDebugFunctions.php</code> file:</p>
<pre>
"files": ["typo3/sysext/core/Resources/PHP/GlobalDebugFunctions.php"]
</pre>
<p>This should be fixed for the case this extension is required separately via Composer in the future.</p> TYPO3 Core - Bug #67047 (Closed): Cannot access shortcut target in menushttp://forge.typo3.org/issues/670472015-05-20T12:18:54ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Invalid shortcut target on translated pages (Closed)" href="http://forge.typo3.org/issues/36822">#36822</a> links via overlaid shortcuts have been fixed but the original menu item data was kept unchanged.</p>
<p>This makes it impossible to e.g. mark active menu items with pure TypoScript. An <code>override</code> is not useful since both <code>CONTENT</code> as well as <code>RECORDS</code> perform overlays too.</p> TYPO3 Core - Bug #66473 (Closed): Cannot create object implementing Serializable on PHP 5.6http://forge.typo3.org/issues/664732015-04-17T18:05:51ZMathias Brodalambrodala@pagemachine.de
<p>Starting with PHP 5.6 classes implementing the <code>Serializable</code> interface are represented as <code>C</code> instead of <code>O</code> in the serialized output.</p>
<p>The <code>Container::getEmptyObject</code> method which creates objects with the unserialize hack to avoid calling the constructor thus yields an error like this:</p>
<blockquote>
<p>Warning: Erroneous data format for unserializing 'Foo' in ...<br />Notice: unserialize(): Error at offset 13 of 15 bytes in ...</p>
</blockquote>
<p>Starting with PHP 5.4 this usecase can be dealt with by <a href="http://php.net/manual/en/reflectionclass.newinstancewithoutconstructor.php" class="external"><code>ReflectionClass::newInstanceWithoutConstructor</code></a></p>
<p>This also needs to fixed for TYPO3 6.2 though which supports PHP 5.3, in which case checking for the <code>Serializable</code> interface and using <code>C</code> instead of <code>O</code> could work.</p> TYPO3 Core - Bug #66350 (Closed): 6.2 static template outdatedhttp://forge.typo3.org/issues/663502015-04-10T10:59:27ZMathias Brodalambrodala@pagemachine.de
<p>The <code>v6.2</code> static template of <code>css_styled_content</code> in the current master is not up to date with changes from the 6.2 branch, namely the title attribute rendering of File Links (see <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Title not used for Filelinks (Closed)" href="http://forge.typo3.org/issues/60429">#60429</a>) and a small style differnce.</p>
<p>This should be updated to ensure exactly the same rendering when using 7.x with the <code>v6.2</code> static template as it is in 6.2 with the latest static template.</p> TYPO3 Core - Bug #66347 (Closed): Alternative text used as link title in File Linkshttp://forge.typo3.org/issues/663472015-04-10T10:40:46ZMathias Brodalambrodala@pagemachine.de
<p>If an alternative text was specified for a file, it is used as link title for file, preview and icon in File Links.</p>
<p>This should be fixed to use the title instead.</p>