TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-07-27T15:34:20ZTYPO3 Forge
Redmine TYPO3 Core - Task #60622 (Rejected): Deprecate getUrl, curlProxyServer and encourage usage of HTT...http://forge.typo3.org/issues/606222014-07-27T15:34:20ZErnesto Baschnyeb@cron.eu
<p>The SYS.curl* settings are being used by GeneralUtility::getUrl and openid. And probably other extensions are using that too.</p>
<p>Since 6.0 we have the nice HttpRequest adapter for the PEAR HTTP_Request2 component, which is a full replacement of what our old getUrl does.</p>
<p>So we want to deprecate getUrl along with the curl* settings.</p> TYPO3 Core - Bug #57262 (Closed): Install Tool: getFolderStatus ajax also being called in Step In...http://forge.typo3.org/issues/572622014-03-25T01:23:42ZErnesto Baschnyeb@cron.eu
<p>The Ajax calls to getFolderStatus and getEnvironmentStatus are useful to add the badges in the left menu of the Install Tool.</p>
<p>But they are also being fired when the Step Installer is running (no Left Menu).</p>
<p>It would be more stable if we would only fire these ajax calls when the Left Menu is indeed loaded and not regardless of the page you are in.</p> TYPO3 Core - Bug #57008 (Closed): New Installation: Could not acquire lock for ClassLoaderhttp://forge.typo3.org/issues/570082014-03-17T22:25:13ZErnesto Baschnyeb@cron.eu
<p>With the Class Loader Locking patch applied (see <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: PHP Warnings after clearing configuration cache in BE (Closed)" href="http://forge.typo3.org/issues/55099">#55099</a>) when installing a fresh new TYPO3 installation (no typo3temp directory present), I get:</p>
<p>( ! ) Fatal error: Uncaught exception 'RuntimeException' with message 'Could not acquire lock for ClassLoader cache creation.' in /www/sites/typo3-62/html/typo3_src/typo3/sysext/core/Classes/Core/ClassLoader.php on line 704<br />( ! ) RuntimeException: Could not acquire lock for ClassLoader cache creation. in /www/sites/typo3-62/html/typo3_src/typo3/sysext/core/Classes/Core/ClassLoader.php on line 704</p>
<p>This should be handled somehow.</p> TYPO3 Core - Task #54511 (Closed): Travis increase PHP memory_limit to 1280mhttp://forge.typo3.org/issues/545112013-12-19T13:56:58ZErnesto Baschnyeb@cron.eu
<p>Currently travis is failing due to exploded memory_limit (>1024m). Why it takes so much needs to be investigated and is planned here: <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: phpunit run in Travis: Detect and fix memory leaks (Closed)" href="http://forge.typo3.org/issues/54510">#54510</a></p>
<p>While this is not tackled, we should increase memory_limit for phpunit run a bit so that it at least works again. I.e. to 1280M.</p> TYPO3 Core - Bug #54510 (Closed): phpunit run in Travis: Detect and fix memory leakshttp://forge.typo3.org/issues/545102013-12-19T13:55:22ZErnesto Baschnyeb@cron.eu
<p>Travis with PHP 5.3 is requiring more than 1 GB of RAM in one run since some merge and then the PHP run fails.</p>
<p>Instead of constantly increase the memory_limit when this occurs, we should investigate what exactly takes so much memory and limit that so that the test-run scales better.</p> TYPO3 Core - Bug #53975 (Closed): BeLog: Exception when time input fields are emptyhttp://forge.typo3.org/issues/539752013-11-26T11:20:41ZErnesto Baschnyeb@cron.eu
<p>If you go to "Info>Log" or "Admin>Log" and select "Userdefined" time range and then leave one of the input fields (start or stop) empty and click "Set", you end up with this exception:</p>
<p>Exception while property mapping at property path "":PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Belog\Domain\Model\Constraint::setManualDateStop() must be an instance of DateTime, null given, called in .../html/typo3_src/typo3/sysext/extbase/Classes/Reflection/ObjectAccess.php on line 215 and defined in .../html/typo3_src/typo3/sysext/belog/Classes/Domain/Model/Constraint.php line 273</p>
<p>When you are in this situation and go to the module again, even changing the Time Select Box to "Undefined" you still get this error (probably because the empty input fields are hidden but submitted again).</p>
<p>And empty input field in start/stop should remove this specific limit.</p> TYPO3 Core - Bug #53940 (Rejected): Extension name is not case insensitive in anymorehttp://forge.typo3.org/issues/539402013-11-25T15:30:01ZErnesto Baschnyeb@cron.eu
<p>The extension "abaticker" for example contains something like:</p>
<pre>
t3lib_extMgm::addPlugin(Array("LLL:EXT:abaTicker/locallang_db.php:tt_content.list_type_pi1", $_EXTKEY."_pi1"),"list_type");
</pre>
<p>In 6.2 this now fails with:</p>
<p>"TYPO3 Fatal Error: Extension key "abaTicker" is NOT loaded" (Exception 1365429656)</p>
<p>So the ExtensionManagementUtil API doesn't seem to be backwards compatible yet (i.e. extPath() etc), as it doesn't seem to expect different CaSe for the passed extension key.</p> TYPO3 Core - Epic #53915 (Closed): Usability and timing issues in Pagetreehttp://forge.typo3.org/issues/539152013-11-25T00:37:06ZErnesto Baschnyeb@cron.eu
<p>The page tree has some problems when it has to deal with long running tasks:</p>
<p>- delete whole tree<br />- copy tree with lots of childs<br />- etc...</p>
<p>This umbrella-issue should try to collect these so that they can be tackled at once.</p> TYPO3 Core - Bug #52812 (Rejected): Installing extension bringes 'Package "xy" is not available'http://forge.typo3.org/issues/528122013-10-14T19:09:26ZErnesto Baschnyeb@cron.eu
<p>If I copy an extension directory to typo3conf/ext/ and try to install it using the Extension Manager (it is listed already), I get:</p>
<pre><code>#1166546734: Package "xy" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive). (More information)</code></pre>
<p>The problem is that the PackageStates file is not up-to-date: it does not include this new package which was just copied there without the knowledge of the Package Management.</p>
<p>Since this is not so uncommon, I would propose to re-create the PackageStates.php file as soon as the Extension Manager tries to do something with packages to make sure it is in sync with the reality - just like it behaved before.</p> TYPO3 Core - Feature #51538 (Rejected): Move old css_styled_content static templates to own exten...http://forge.typo3.org/issues/515382013-08-29T18:13:37ZErnesto Baschnyeb@cron.eu
<p>css_styled_content provides several static templates that enable to render the frontend in the same way as some older TYPO3 version. We currently ship static templates as old as TYPO3 3.8. The whole list appears in the "Include Template from Extension" list and the list is getting longer each release.</p>
<p>To make it clearer that these templates are not maintained anymore, and new installations should be given these by default, we decided to move these over to a new System Extension which is not installed by default, but can be installed through the Upgrade Wizard if someone decides to stay with older compatibility version.</p>
<p>Proposal for new extension name: csc_oldtemplates</p>
<p>We decided to keep the extension in the core thou so that potential changes and fixes could be more easily be done by the core team itself directly in the core.</p> TYPO3 Core - Bug #42890 (Rejected): Regression: Javascript error in Backend (jumpToUrl)http://forge.typo3.org/issues/428902012-11-12T17:50:56ZErnesto Baschnyeb@cron.eu
<p>All checkboxes in the Backend that contain a "onclick" pointing to "jumpToUrl" seem to be broken in the latest release of TYPO3. The Javascript pops up an error:</p>
<p>Uncaught ReferenceError: Invalid left-hand side in assignment</p>
<p>To test, go to the list module and try to select "Extended View" or "Localization View" from the options beneath the list.</p>
<p>Or in Extension Manager (the old-old one), try to select "Display shy extensions"</p>
<p>Tested on 4.5.x, but should affect also the latest security releases of the other branches as well.</p> TYPO3 Core - Bug #26995 (Closed): Merge CGL changes from 4.5.3http://forge.typo3.org/issues/269952011-05-23T22:11:16ZErnesto Baschnyeb@cron.eu
<p>Hi,</p>
<p>in patchset 4 of <a class="external" href="https://review.typo3.org/2288">https://review.typo3.org/2288</a> I applied CGL fixes to the <strong>new</strong> code that was changed since 4.5.2. Please consider applying that to the external repository's version also (maybe after we move to GIT).</p>
<p>There are other CGL issues in the extension still, but at least I wanted to make sure no new issues are introduced.</p> TYPO3 Core - Bug #13320 (Closed): Don't use cross-extension dependencies (e.g. em)http://forge.typo3.org/issues/133202011-02-24T08:15:08ZErnesto Baschnyeb@cron.eu
<p>Hi,</p>
<p>please apply the following change which was included in typo3_src already:</p>
<p><a class="external" href="http://forge.typo3.org/projects/typo3v4-core/repository/revisions/10615">http://forge.typo3.org/projects/typo3v4-core/repository/revisions/10615</a></p>
<p>We will release 4.5.1a with this fix included and want to make sure that it doesn't happen again.</p>
<p>Thanks!</p> TYPO3 Core - Feature #24850 (Rejected): After the last Upgrade Wizard, a link to "COMPARE" should...http://forge.typo3.org/issues/248502011-01-27T11:27:34ZErnesto Baschnyeb@cron.eu
<p>After the last Upgrade Wizard is through, we should present a last Next button which links to the "COMPARE" screen.</p>
<p>This could even be integrated in a standalone "Wizard" so that the DB compare is done cleanly in the Upgrade Wizard path, so that after that the user is presented with a "Congratulation" message and some other nice words.</p>
<p>(issue imported from #M17354)</p> TYPO3 Core - Bug #12079 (Closed): Not possible to reactivate t3editor after deactivationhttp://forge.typo3.org/issues/120792011-01-10T22:21:26ZErnesto Baschnyeb@cron.eu
<p>When I de-select the checkbox "Deactivate t3editor" which is shown below the Info/Modify form of SETUP (or CONSTANT), there is no way of getting it back "active". If I unselect that checkbox again and SAVE, it is again activated as soon as I enter that form again.</p>
<p>This happens on 4.4 and current trunk. Would be cool to have that fixed for the 4.5.0 final release.</p>