TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692012-05-24T02:08:53ZTYPO3 Forge
Redmine TYPO3 Core - Bug #37455 (Closed): Autoload gives strange error message if insufficient file permi...http://forge.typo3.org/issues/374552012-05-24T02:08:53ZMichael Knollmimi@kaktusteam.de
<p>When installing a "new" extension via EM which brings its own ext_autoload file, autoloading / class loading mechanism will show up with an error message similar to</p>
<p>"Class could not be found / loaded..."</p>
<p>instead of giving a hint that autoload-cache files could not be written in /typo3temp/Cache/Code/cache_phpcode</p>
<p>The "old" autoload cache files will still be available and everything except the new extension will work fine.</p>
<p>This behaviour should be changed. If autoload-cache cannot be written, there should be an adequate error message telling the user how to fix this issue.</p>
<p>Thx</p>
<p>Mimi</p>
<p>P.S. I also opened up a thread on t.dev mailinglist "Problems with ext_autoload.php and ext_localconf.php" which holds a little more details on this problem.</p> TYPO3 Core - Bug #21705 (Closed): Page Tree shows Server Errorhttp://forge.typo3.org/issues/217052009-11-26T21:18:26ZMichael Knollmimi@kaktusteam.de
<p>I have set up a new installation of Typo3 4.3 RC2 on a FreeBSD server running PHP 5.2.9. When clicking on the page module in the backend, I get a Server error in the frame, where the page tree should be displayed (see attached screenshot). Error Log on the server is attached below!</p>
<p>Although this happens with a TemplaVoila Page Module, the same error occurs, when clicking on the list module in the backend, every time, the page tree should be displayed.</p>
<p>We observed the following effect: After clearing ALL cache-tables, this error occurs on the first click on the page module (or list module). After clicking for the second time, the error is no longer occuring. This means, that whenever the page tree is loaded for a second time, it is correctly displayed.</p>
<p>10.0.0.66 - - [26/Nov/2009:21:08:58 +0100] "GET /typo3/&currentSubScript= HTTP/1.1" 404 319 "http://ry21.ptlistdev.play.OUR_DOMAIN.de/typo3/alt_mod_frameset.php?fW=0&nav=/typo3/alt_db_navframe.php%3F&script=..%2Ftypo3conf%2Fext%2Ftemplavoila%2Fmod1%2Findex.php&id=" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; de; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7" <br />(issue imported from #M12784)</p> TYPO3 Core - Bug #21568 (Closed): Backend Login-Popup not workinghttp://forge.typo3.org/issues/215682009-11-16T16:03:11ZMichael Knollmimi@kaktusteam.de
<p>The new "Refresh-Login" account is not working for me. Although I enter the right password, it says "Password incorrect".</p>
<p>I have Mac OS X 10.6 and Firefox 3.5.5 running.</p>
<p>All BE-skin extensions etc. are switched of.</p>
<p>See attached screenshot</p>
<p>(issue imported from #M12612)</p> TYPO3 Core - Bug #21558 (Closed): BE Login form is puzzledhttp://forge.typo3.org/issues/215582009-11-16T00:53:16ZMichael Knollmimi@kaktusteam.de
<p>Since 4.3beta_xy my backend login form is somehow broken. The fields are not placed where they should be and the button for login has no label. I attached a screenshot to show what's wrong</p>
<p>(issue imported from #M12600)</p> TYPO3 Core - Bug #21177 (Closed): Install Tool Crashes on "Update Wizard"http://forge.typo3.org/issues/211772009-10-02T23:22:01ZMichael Knollmimi@kaktusteam.de
<p>The install tool crashes when I click on "update wizard" after having changed from 4.2.8 to 4.3 Beta1. The following error message occurs:</p>
<p>tx_jsmanager_Exception<br />extjs already registered in tx_jsmanager_Manager::$registryArr</p>
<p>(issue imported from #M12104)</p>