TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692010-07-03T10:30:06ZTYPO3 Forge
Redmine TYPO3 Core - Bug #23082 (Closed): Install tool causes PHP warnings if typo3conf/ is not writeablehttp://forge.typo3.org/issues/230822010-07-03T10:30:06ZRobert Lemkerobert@typo3.org
<p>When running TYPO3 right after downloading it (e.g. the 4.4 introduction package) and you didn't set the right file permissions, you'll get PHP warnings when trying to use the install tool.</p>
<p>Download the packaged TYPO3 4.4, unpack it and access it through its base URL, e.g. <a class="external" href="http://myhost/">http://myhost/</a>.</p>
<p>(issue imported from #M14980)</p> TYPO3 Core - Bug #17120 (Closed): Content is not cached and white page displayed with big content...http://forge.typo3.org/issues/171202007-03-14T13:28:30ZRobert Lemkerobert@typo3.org
<p>This problem originally occurred on typo3.org (ter_doc_pi1) but can be reproduced independently:</p>
<p>If a frontend plugin returns a large amount of content, this content is not written into the page cache. In addition not even the page without the FE plugin output is shown, but instead only a white page is displayed (which will be cached).</p>
<p>Use the attached extension to reproduce the behaviour:</p>
<p>- Install the FE plugin from the exploit extension on any page<br />- Make sure that you're running PHP 5.2.1<br />- View the page containing the FE plugin, the page should be blank</p>
<p>- Set the no_cache flag in the page properties or add "no_cache=1" to the GET parameters<br />- View the page containing the FE plugin, the page should display the content</p>
<p>Obviously the problem has nothing to do with the FE plugin itself (hence the exploit extension). While debugging, it turned out that in tslib_fe->setPageCacheContent() the $content is already empty: Therefore the empty content is (correctly) stored in the cache_pages table.</p>
<p>The content disappears somewhere between the "return" of the FE plugin in the setPageCacheContent method in tslib_fe.<br />(issue imported from #M5221)</p> TYPO3 Core - Bug #15936 (Closed): Gremlin: The running TYPO3 version (4.0-CVS) is higher than all...http://forge.typo3.org/issues/159362006-03-29T09:50:21ZRobert Lemkerobert@typo3.org
<p>When installing an extension which has weird version numbers in its constraints due to the switch to TER2, the users gets a warning which is technically correct but annoying.</p>
<p>Install an extension which depends on TYPO3 version 0.0.2 or similar</p>
<p>Just ignore every constraint with TYPO3 version < 3.x.x and PHP version 3.0.0<br />(issue imported from #M3039)</p> TYPO3 Core - Bug #15879 (Closed): EM: Suggested extensions are not handled correctlyhttp://forge.typo3.org/issues/158792006-03-22T18:23:29ZRobert Lemkerobert@typo3.org
<p>During the install of an extension which suggests other extensions the user is asked if these extensions should be downloaded as well. Usually he can either follow the suggestion or ignore it.</p>
<p>There are two issues I experienced:</p>
<p>a) The extension keys of the extensions being suggested are not displayed correctly<br />b) Even if I check the "ignore" check box, I can't proceed</p>
<p>- Import templavoila 0.6.1 from a local .t3x file (attached to this report)<br />- doc_tut_ftb1 and rlmp_tvnotes shouldn't be installed</p>
<p>The suggestions don't suggest a specific version of extensions, might be related to that.<br />(issue imported from #M2957)</p> TYPO3 Core - Bug #15877 (Closed): EM doesn't respect dependencies if no version number is specifiedhttp://forge.typo3.org/issues/158772006-03-22T15:40:54ZRobert Lemkerobert@typo3.org
<p>After downloading an extension which depends on other extension but not on specific versions of them, these dependencies don't appear in the EM locally and are not checked either.<br />However, these constraints are displayed correctly at TYPO3.org</p>
<p>Download rlmp_eventdb 1.0.4 with EM2 from TER2. View details in the EM: No dependencies are shown.</p>
<p>Constraints of rlmp_eventdb:</p>
<pre><code>'depends' => array(<br /> 'php' => '4.3.1-',<br /> 'typo3' => '3.7.1-',<br /> 'cms' => '',<br /> 'lang' => '',<br /> 'address' => '',<br /> 'moneylib' => '',<br /> 'rlmp_dateselectlib' => '',<br /> 'overlib' => '',<br /> 'frontendformslib' => '',<br /> ),</code></pre>
<p>(issue imported from #M2954)</p> TYPO3 Core - Bug #15635 (Closed): Extension Manager: Charset of extension titles, authors etc. is...http://forge.typo3.org/issues/156352006-02-16T17:40:33ZRobert Lemkerobert@typo3.org
<p>The charset of all TER2 data is utf8 and the EM just displays extension titles, authors etc. in that charset, regardless of which charset is defined for the BE</p>
<p>du weißt schon ....</p>
<p>(issue imported from #M2579)</p> TYPO3 Core - Bug #15237 (Closed): Nesting of sections doesn`t seem to workhttp://forge.typo3.org/issues/152372005-11-25T14:48:42ZRobert Lemkerobert@typo3.org
<p>I tried to create nested sections for a content element that can contain two different kind of contents. This went fine. But one of the contents has two different subcontents again and so I wanted to create nested sections. While the mapping was no problem, it was not possible to create the nested contents in the TV page module. It seems that only one select field for sections can be used.</p>
<p>This is a missing feature in TCEforms as well as the TemplaVoila Page Module. Unfortunately rendering nested SC/COs is not that trivial, so I don't solve it right away. If anybody feels like it, just go ahead.<br />(issue imported from #M1930)</p> TYPO3 Core - Feature #15181 (Closed): Make EM unit test awarehttp://forge.typo3.org/issues/151812005-11-19T18:41:37ZRobert Lemkerobert@typo3.org
<p>Unit tests are always stored in a subdirectory "tests" of an extension. The Extension Manager should either ignore the whole content of that directory (ie. not report XCLASS errors etc.) or show a message that some unit tests are found.</p>
<p>(issue imported from #M1904)</p> TYPO3 Core - Bug #14557 (Closed): EM: Updating an extension with changed dependencies blocks websitehttp://forge.typo3.org/issues/145572005-02-17T18:18:17ZRobert Lemkerobert@typo3.org
<p>When updating an extension which has new dependencies to other extensions, the EM will replace the old extension with the new version but updated extension fails because of the unresolved dependencies.</p>
<p>Install an extension, add another extension to the dependency list and update the extension.</p>
<p>The extension manager should look into the emconf.php and evaluate the new dependencies before updating the extension.<br />(issue imported from #M809)</p> TYPO3 Core - Bug #14123 (Closed): cached image sizes don't work properly, method for clearing the...http://forge.typo3.org/issues/141232004-04-29T11:52:29ZRobert Lemkerobert@typo3.org
<p>Have to fixe the cache clearing mechanism.</p>
<p>- Put SQL for cache_imagesizes into t3lib/stddb/tables.sql instead of typo3/sysext/cms/ext_tables.sql<br />- Move cache clearing into install tool<br />(issue imported from #M31)</p> TYPO3 Core - Bug #14122 (Closed): Install Tool shows fatal error if typo3/ext is not writeablehttp://forge.typo3.org/issues/141222004-04-29T11:39:05ZRobert Lemkerobert@typo3.org
<p>If the global extensions directory is not writeable, the Basic Configuration section will show a fatal error although typo3/ext doesn't neccessarily have to be writeable - in fact it should have read/execute status in a multi-user enviroment.</p>
<p>Maybe we should put a warning that no global extensions can be installed and show a fatal error if typo3/ext/ is not readable at all.</p>
<p>(issue imported from #M30)</p>