TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-03-18T10:52:13ZTYPO3 Forge
Redmine 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 #84408 (Closed): Extract request processing from IconFactoryhttp://forge.typo3.org/issues/844082018-03-17T11:29:13ZMathias Brodalambrodala@pagemachine.de
<p>The <code>IconFactory</code> provides an API to get icons but also request processing via AJAX. The latter should be moved to a separate controller.</p> 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 #81760 (Closed): Typo in label for "Recently updated pages" menu descriptionhttp://forge.typo3.org/issues/817602017-06-30T15:23:09ZMathias Brodalambrodala@pagemachine.de
<p>The description of the <strong>Recently updated pages</strong> menu currently says:</p>
<blockquote>
<p>Menu of recenlty updated pages</p>
</blockquote>
<p>This should be fixed to say <em>recently</em>.</p> TYPO3 Core - Bug #81524 (Closed): Cannot send mails with special characters in local parthttp://forge.typo3.org/issues/815242017-06-09T12:47:40ZMathias Brodalambrodala@pagemachine.de
<p>Currently it is impossible to send mails with special characters in their local part, e.g. <code>john.lötzsch@example.org</code>. Swiftmailer fails with the following error:</p>
<pre>
[ Swift_RfcComplianceException ]
Address in mailbox given [john.lötzsch@example.org] does not comply with RFC 2822, 3.6.2.
thrown in file er/lib/classes/Swift/Mime/Headers/MailboxHeader.php
in line 345
</pre>
<p>The mentioned <a href="https://tools.ietf.org/html/rfc2822" class="external">RFC 2822</a> has been extended by <a href="https://tools.ietf.org/html/rfc5335" class="external">RFC 5335</a> which is <a href="https://github.com/swiftmailer/swiftmailer/commit/e7cf4bd807b44be83d8922b3a1abe4d11a3fb15a" class="external">supported by Swiftmailer 6.x and newer</a>, thus an upgrade is necessary. This implies a few <a href="https://github.com/swiftmailer/swiftmailer/blob/v6.0.0/CHANGES#L4" class="external">breaking changes</a> however.</p> TYPO3 Core - Bug #81297 (Closed): Extbase record preview leads to 404 due to missing cHashhttp://forge.typo3.org/issues/812972017-05-22T14:56:45ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Require cHash for cached plugin actions in Extbase (Closed)" href="http://forge.typo3.org/issues/78002">#78002</a> the cHash is enforced for Extbase plugins if arguments are present. This however breaks the <a href="https://docs.typo3.org/typo3cms/TSconfigReference/PageTsconfig/TCEmain/Index.html#preview" class="external">record preview</a> feature since it does not add a <code>cHash</code> argument but uses <code>no_cache</code> instead.</p>
<p>A possible fix could be <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Avoid usage of no_cache in preview link configuration (Closed)" href="http://forge.typo3.org/issues/78336">#78336</a> which adds an option to enable <code>cHash</code> calculation for record preview URLs.</p> TYPO3 Core - Bug #80316 (Closed): Misleading deprecation message for GeneralUtility::requireOnce/...http://forge.typo3.org/issues/803162017-03-17T09:58:20ZMathias Brodalambrodala@pagemachine.de
<p>The methods <code>GeneralUtility::requireOnce()</code> and <code>GeneralUtility::requireFile</code> currenty log a message like the following upon usage:</p>
<pre>
TYPO3\CMS\Core\Utility\GeneralUtility::requireOnce() - since TYPO3 CMS 8, this file will be removed in TYPO3 CMS 9
</pre>
<p>Since <code>GeneralUtility.php</code> is unlikely to be removed that soon, this should be fixed. ;-)</p> TYPO3 Core - Bug #76976 (Closed): Missing dependency on PHP extension "mbstring"http://forge.typo3.org/issues/769762016-07-07T12:19:28ZMathias Brodalambrodala@pagemachine.de
<p>All current TYPO3 LTS versions require the PHP extension "mbstring" which is mentioned in the installation requirements but not checked anywhere. This should be added to the Composer manifest as well as the system environment check.</p> TYPO3 Core - Bug #73518 (Closed): Disabled menu item state wrong for pages hidden in default lang...http://forge.typo3.org/issues/735182016-02-17T11:20:03ZMathias Brodalambrodala@pagemachine.de
<p>With <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Use API to check for "Hide default translation of page" (Closed)" href="http://forge.typo3.org/issues/73083">#73083</a> a cleanup was performed but an error was introduced in the backport to 6.2 which breaks the disabled menu item state (<code>USERDEF1</code> / <code>USERDEF2</code>).</p> TYPO3 Core - Bug #73083 (Closed): Use API to check for "Hide default translation of page"http://forge.typo3.org/issues/730832016-02-02T17:15:33ZMathias Brodalambrodala@pagemachine.de
<p>Throughout the core the logic to handle <code>pages.l18n_cfg</code> with value <code>1</code> (Hide default translation of page) is duplicated instead of calling <code>GeneralUtility::hideIfDefaultLanguage()</code> This should be fixed.</p> TYPO3 Core - Bug #69708 (Closed): Replace sprite icon in ImportExport::addRelationshttp://forge.typo3.org/issues/697082015-09-12T10:46:58ZMathias Brodalambrodala@pagemachine.de
<p>The <code>IconUtility</code> usage for <code>status-status-checked</code> and <code>status-dialog-warning</code> in <code>ImportExport::addRelations</code> must be updated to use the new <code>IconFactory</code></p> TYPO3 Core - Bug #60338 (Closed): Changing view format does not affect partial formathttp://forge.typo3.org/issues/603382014-07-15T15:35:24ZMathias Brodalambrodala@pagemachine.de
<p>When using one view object to render a template in different formats (e.g. email in text and HTML), the template respects the requested format. However, partials are always rendered in the first rendered format. Example:</p>
<p><strong>Content of templates/partials</strong>:</p>
<p>Content of <code>Foo.txt</code>:<br /><pre>
Hello
<f:render partial="Bar"/>
</pre></p>
<p>Content of <code>Partials/Bar.txt</code>:<br /><pre>
World
</pre></p>
<p>Content of <code>Foo.html</code>:<br /><pre>
<p>Text</p>
<f:render partial="Bar"/>
</pre></p>
<p>Content of <code>Partials/Bar.html</code>:<br /><pre>
<p>World</p>
</pre></p>
<p><strong>1st invocation</strong>:</p>
<pre>
// Let $view be an instance of \TYPO3\CMS\Fluid\View\TemplateView
$view->setFormat('txt');
$view->render('Foo');
</pre>
<p>Result:<br /><pre>
Hello
World
</pre></p>
<p><strong>2nd invocation</strong>:</p>
<pre>
// $view is the same instance as above
$view->setFormat('html');
$view->render('Foo');
</pre>
<p>Result:<br /><pre>
<p>Hello</p>
World
</pre></p>
<p>As you can see, the 2nd output was rendered using the txt-Partial.</p>
<p>This is due to the local partial identifier cache in <code>AbstractTemplateView</code> which only considers the partial name, not the current request format. If that one is incorporated, separate cache entries for each partial formats are created.</p> TYPO3 Core - Bug #60296 (Closed): Task executor ignores full framework configurationhttp://forge.typo3.org/issues/602962014-07-14T09:24:00ZMathias Brodalambrodala@pagemachine.de
<p>In the <a href="https://git.typo3.org/?p=Packages/TYPO3.CMS.git;a=blob;f=typo3/sysext/extbase/Classes/Scheduler/TaskExecutor.php;h=466bfaeee8549b5a9bbfa8a9033cdf05bad5e0d1;hb=HEAD#l79" class="external">initialization step</a> of the Scheduler task executor, class implementations are registered but only based on <code>config.tx_extbase.objects</code>. Possible overrides through <code>module.tx_<myext>.objects</code> are currently ignored.</p>
<p>This should be changed to respect the full framework configuration instead like what <code>TYPO3\CMS\Extbase\Core\Bootstrap</code> already does since #44796 was fixed.</p> TYPO3 Core - Bug #53974 (Closed): Environment variables prefixed with REDIRECT_ ignoredhttp://forge.typo3.org/issues/539742013-11-26T11:16:07ZMathias Brodalambrodala@pagemachine.de
<p>Using Apache mod_rewrite in certain setups (mostly PHP in CGI mode) makes environment variables from original requests available in the target request as <code>REDIRECT_<envvar></code>, thus e.g. setting <code>TYPO3_DISABLED_CORE_UPDATER</code> becomes <code>REDIRECT_TYPO3_DISABLED_CORE_UPDATER</code>.</p>
<p>This should be handled transparently by <code>GeneralUtility::getIndpEnv()</code> and relevant locations be updated (e.g. <code>TYPO3_CONTEXT</code>, <code>TYPO3_DISABLE_CORE_UPDATER</code>).</p> TYPO3 Core - Bug #53188 (Closed): REDIRECT_TYPO3_DISABLE_CORE_UPDATER ignoredhttp://forge.typo3.org/issues/531882013-10-29T08:38:13ZMathias Brodalambrodala@pagemachine.de
<p>Using Apache mod_rewrite in certain setups makes environment variables from original requests available in the target request as <code>REDIRECT_<envvar></code>, thus setting <code>TYPO3_DISABLE_CORE_UPDATER</code> becomes <code>REDIRECT_TYPO3_DISABLE_CORE_UPDATER</code>.</p>
<p>The latter is currently not considered by TYPO3, thus the core updater cannot be disabled via the environment variable and the mentioned setup.</p>
<p>See <a href="http://stackoverflow.com/a/9406994" class="external">this Stackoverflow</a> post for an explanation and <a href="https://github.com/apache/httpd/blob/e1fac1db26/modules/http/http_request.c#L389" class="external">link to the Apache source code</a>.</p>