TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-06-05T10:55:06ZTYPO3 Forge
Redmine TYPO3 Core - Feature #59355 (Rejected): make trustedHostsPattern use sys_domain recordshttp://forge.typo3.org/issues/593552014-06-05T10:55:06ZChristian Zenkertypo3@xopn.de
<p>Configuring the regexp for trustedHostsPattern is really tedious in larger installations with lots of handled domains.</p>
<p>How about introducing a feature to use sys_domain records to determine if a HTTP_HOST is valid?</p> TYPO3 Core - Bug #59277 (Closed): Warning "Invalid argument supplied for foreach()" in SearchCont...http://forge.typo3.org/issues/592772014-06-02T13:47:35ZChristian Zenkertypo3@xopn.de
<p>Performing a search with indexed_search a warning will be raised:</p>
<pre>Core: Error handler (FE): PHP Warning: Invalid argument supplied for foreach() in /var/www/ltslohmann/devbox/typo3_src-6-patched/typo3/sysext/indexed_search/Classes/Controller/SearchController.php line 615</pre>
<p>I found this issue in 6.1.9, but it seems to also be present in 6.2.</p> TYPO3 Core - Bug #56988 (Closed): IE8 Users can't login to backendhttp://forge.typo3.org/issues/569882014-03-17T12:54:18ZChristian Zenkertypo3@xopn.de
<p>From what I understand <a href="http://forum.typo3.org/index.php/t/199084/" class="external">IE8 is still (kind of) supported</a>, right?</p>
<p>When a user logs in to the backend with IE8 they won't see anything but a white page caused by the following JS exception:</p>
<pre><code>Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322)
Timestamp: Mon, 17 Mar 2014 11:47:38 UTC
Message: Expected identifier
Line: 3956
Char: 61
Code: 0
URI: http://example.com/typo3temp/compressor/merged-0409cb80b420cef16c8b514e2b382dbb-940cefcae7e07458d2dc490c43c14753.1395047044.js
Message: 'TYPO3.state.ExtDirectProvider' is null or not an object
Line: 135
Char: 4
Code: 0
URI: http://example.com/typo3/backend.php
</code></pre>
<p>The error occurs here<br /><pre><code>TYPO3.settings.ShortcutMenu.delete.ajaxUrl</code></pre></p>
<p><code>delete</code> is a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Reserved_Words" class="external">reserved word</a> in JavaScript and causes problems in IE8 (and lower) only.</p>
<p>Regression from <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="Task: Protect core Ajax calls against CSRF (Closed)" href="http://forge.typo3.org/issues/56356">#56356</a>.</p>
<p>Also I used the following regexp to look for similar issues, but did not find any:<br /><pre><code>(?<=\.)(brake|case|catch|continue|debugger|default|delete|do|else|finally|for|function|if|in|instanceof|new|return|switch|this|throw|try|typeof|var|void|while|with)(?!\w)</code></pre></p> TYPO3 Core - Bug #56271 (Rejected): SqlSchemaMigrationService getUpdateSuggestions creates invali...http://forge.typo3.org/issues/562712014-02-25T15:08:09ZChristian Zenkertypo3@xopn.de
<p>Consider an extension changes its database definition from</p>
<pre><code>CREATE TABLE tx_foobar_table (
old_uid int(11) NOT NULL DEFAULT '0',
PRIMARY KEY (old_uid)
)</code></pre> to<br /><pre><code>CREATE TABLE tx_foobar_table (
uid int(11) NOT NULL DEFAULT '0' auto_increment,
PRIMARY KEY (uid)
)</code></pre>The statements the install tool generates for that are:<br /><pre><code>ALTER TABLE tx_realurl_redirects ADD uid int(11) NOT NULL auto_increment;
ALTER TABLE tx_realurl_redirects DROP PRIMARY KEY;
ALTER TABLE tx_realurl_redirects ADD PRIMARY KEY (uid);</code></pre><br />The problem here is that the column definition includes the <code>auto_increment</code> where MySQL requires a column with auto_increment to be the Primary Key.
<p>There is already a <a href="https://git.typo3.org/Packages/TYPO3.CMS.git/blob/9e9ca9ae1e397f5fa8f4dbbd6caa563a27db1f98:/typo3/sysext/install/Classes/Service/SqlSchemaMigrationService.php#l348" class="external">fix in the source code to circumvent this</a> for newly created primary keys, but not if a primary key is changed.</p> TYPO3 Core - Bug #48984 (Closed): cache tags table has orphaned records for Typo3DatabaseBackendhttp://forge.typo3.org/issues/489842013-06-10T11:04:11ZChristian Zenkertypo3@xopn.de
<p>Description:</p>
<p>1. When creating a page and assigning multiple tags, there is one record created in the cache table and multiple in the cache_tags table.<br />2. When flushing cache records by tag only the <strong>one</strong> entry in cache_tags with the requested tag will be removed. All other cache_tags with the same identifier will remain.</p>
<p>Expected: all entries in cache_tags with the deleted identifier are removed.</p>
<p>Found this issue in TYPO3 4.6, but from reading it does not seem to be fixed in the master branch.</p> TYPO3 Core - Bug #40855 (Closed): stdWrap of special.value in HMENU is applied twicehttp://forge.typo3.org/issues/408552012-09-12T10:25:41ZChristian Zenkertypo3@xopn.de
<p><em>also appears in 4.5 and very likely 4.6</em></p>
<p>If the <code>stdWrap</code> functionality of <code>HMENU.special.value</code> is used, this is applied twice.<br />I'm not very familiar on how HMENU works internally. If someone could tell me the best place to fix this without side-effects, I would be happy to submit a patch.</p>
<p>Here are my findings:</p>
<p>The first time stdWrap is applied is <code>tslib_content_HierarchicalMenu::render()</code> (line 59 in TYPO3 4.5.19).<br />Then it is added multiple times accross <code>tslib_menu</code> again.</p>
<p>I would go with removing the stdWrapping in <code>tslib_menu</code>, but am I right with this or is there any other entry point to this class other than <code>tslib_content_HierarchicalMenu::render()</code> that I should check?</p> TYPO3 Core - Bug #32596 (Closed): EM: ambiguous XClass naming tx_em_Connection_ExtDirectServerhttp://forge.typo3.org/issues/325962011-12-15T14:24:16ZChristian Zenkertypo3@xopn.de
<p>Just a small typo:</p>
<p>The naming for XClassing tx_em_Connection_ExtDirectServer is written with and without underscore between "connection" and "extdirectserver".</p>
<code>if (defined('TYPO3_MODE') && isset($GLOBALS['TYPO3_CONF_VARS'][TYPO3_MODE]['XCLASS']['typo3/sysext/em/classes/connection/class.tx_em_connectionextdirectserver.php'])) {
include_once($GLOBALS['TYPO3_CONF_VARS'][TYPO3_MODE]['XCLASS']['typo3/sysext/em/classes/connection/class.tx_em_connection_extdirectserver.php']);
}</code> TYPO3 Core - Bug #25060 (Closed): config.debug = 1 triggers Quirks Mode in IE-Browserhttp://forge.typo3.org/issues/250602011-02-16T16:48:19ZChristian Zenkertypo3@xopn.de
<p>Enabling the debugger will put the debugging comment () in front of any other output - even DocType declaration. This way Quirks Mode in Internet Explorer is triggered.</p>
<p>How to reproduce:<br />- set page.config.debug = 1 on a typical TypoScript setup<br />- verify that Quirks Mode is active by rendering a box with a width and height of 50px, border of 10px and some background color. You should see, that the colored box (without border) is actually just 30px high and wide. Standard mode would give you a box with the full 50px</p>
<p>Temporary Workaround:<br />- disable config.debug (at least for IE browsers)</p>
<p>Solution:<br />- render the debug output after the content as it was in TYPO3 4.4 and below. Patch is appended.</p>
<p>not present in TYPO3 4.4 and below<br />(issue imported from #M17618)</p>