TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692017-03-17T09:58:20ZTYPO3 Forge
Redmine 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 - Task #77153 (Closed): Mention fileinfo PHP extensionhttp://forge.typo3.org/issues/771532016-07-19T11:07:50ZMathias Brodalambrodala@pagemachine.de
<p>Since <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Remove fileinfo as dependency in SystemEnvironment/Check (Closed)" href="http://forge.typo3.org/issues/74177">#74177</a> the PHP extension <code>fileinfo</code> is no hard dependency anymore. However, without this extension the detection of file types does not work at all. This results in files being shown as "Unknown" in the file module and broken output in extensions which check the resource type of media (e.g. EXT:news).</p>
<p>Thus this extension should at least be mentioned in the installation instructions.</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 - 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 - 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 - Task #73152 (Closed): Update Symfony Console to 3.xhttp://forge.typo3.org/issues/731522016-02-05T17:18:18ZMathias Brodalambrodala@pagemachine.de
<p>The Symfony Console component should be updated to 3.x to use the latest stable release.</p>
<p>This requires quite a few <a href="https://github.com/symfony/symfony/blob/b6767c23dd8f9b54bc9fb97bb0b2b003c1252085/UPGRADE-3.0.md#console" class="external">migrations and a breaking change</a>.</p> TYPO3 Core - Task #73151 (Closed): Update Symfony Finder to 3.xhttp://forge.typo3.org/issues/731512016-02-05T17:10:55ZMathias Brodalambrodala@pagemachine.de
<p>The Symfony Finder component should be updated to 3.x to use the latest stable release.</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 - Task #71521 (Closed): Clean up ObjectManager injection in CommandControllerhttp://forge.typo3.org/issues/715212015-11-12T15:55:23ZMathias Brodalambrodala@pagemachine.de
<p>The <code>ObjectManager</code> injection method in the Extbase <code>CommandController</code> is misused to initialize a lot of objects. This should be cleaned up.</p> TYPO3 Core - Task #69722 (Closed): Drop "sprite" from icon variable names in ImportExporthttp://forge.typo3.org/issues/697222015-09-12T14:06:24ZMathias Brodalambrodala@pagemachine.de
<p>To simplify searching for remaining occurrences of "sprite" in the core, the icon variables in <code>ImportExport</code> should be renamed.</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>