TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692016-09-02T15:20:47ZTYPO3 Forge
Redmine TYPO3 Core - Task #77787 (Closed): Optimize rendering of Changelogs for docs.typo3.orghttp://forge.typo3.org/issues/777872016-09-02T15:20:47ZErnesto Baschnyeb@cron.eu
<p>The rendering of the TYPO3 Core Changelog's is currently suboptimal. The result:</p>
<p><a class="external" href="https://docs.typo3.org/typo3cms/extensions/core/latest/Index.html">https://docs.typo3.org/typo3cms/extensions/core/latest/Index.html</a></p>
<p>The rendering produces tons of warnings, the structure is not up to date with the latest theme, and there are several syntax errors with our Rest files.</p>
<p>Solution: Fix it all.</p> 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 - Task #57209 (Closed): Remove deprecation of BasicFileUtility::init until core stops ...http://forge.typo3.org/issues/572092014-03-23T17:58:02ZErnesto Baschnyeb@cron.eu
<p>Until we fully remove usage of BasicFileUtility throughout the core (i.e. DataHandler, Import/Export module, ElementBrowser and others), the core should not pollute the deprecation log with it.</p> TYPO3 Core - Task #56960 (Closed): Adjust sys_notes styling according to UX teamhttp://forge.typo3.org/issues/569602014-03-16T14:41:36ZErnesto Baschnyeb@cron.eu
<p>Adjust CSS and styling of sys notes according to the definitions of the UX team. See #26796.</p> TYPO3 Core - Task #56941 (Closed): Return the 1-2-3 step icons in the step installerhttp://forge.typo3.org/issues/569412014-03-15T19:52:56ZErnesto Baschnyeb@cron.eu
<p>The 1-2-3 step installer could get the step icons back to visualize where the user is in the process of installation.</p>
<p>See <a class="external" href="https://redpen.io/xdk5sg">https://redpen.io/xdk5sg</a></p> TYPO3 Core - Task #56538 (Closed): Cache the $GLOBALS['TYPO3_LOADED_EXT'] as an arrayhttp://forge.typo3.org/issues/565382014-03-04T15:28:03ZErnesto Baschnyeb@cron.eu
<p>Several core components still access $GLOBALS['TYPO3_LOADED_EXT'] directly. Basically it's used to loop through the activated extensions and also to check if some extension is installed.</p>
<p>Since the Package Management, this array is being simulated by an object (LoadedExtensionsArray). Plan was to be able to add deprecation messages for accessing this array in future.</p>
<p>When accessing a FE with one USER_INT, accessing this object takes about 10% of the time.</p>
<p>It should be considered if we cannot generate the original array on first request, cache it, and then make the GLOBAL array available again to whoever uses it. It's just a list of extensions. The gain of the future possibility of throwing a deprecation message opposed to simply having this array as an array and be fast is probably not worth it.</p> TYPO3 Core - Task #56497 (Closed): Install Tool order of menu itemshttp://forge.typo3.org/issues/564972014-03-03T15:52:16ZErnesto Baschnyeb@cron.eu
<p>According to feedback from the UX team, we should reorder the menu items of the install tool:</p>
<p><a class="external" href="https://projects.invisionapp.com/share/H2IU7YVE#/screens/12116399/comments/7066513">https://projects.invisionapp.com/share/H2IU7YVE#/screens/12116399/comments/7066513</a></p>
<p>(and here a screen in case the above link is not working anymore):</p>
<p><img src="http://forge.typo3.org/attachments/download/26168/install-tool-order.png" alt="" loading="lazy" /></p>
<p>Current Order:</p>
<ul>
<li>Welcome</li>
<li>Important actions</li>
<li>System environment</li>
<li>Configuration Presets</li>
<li>Folder structure</li>
<li>Test setup</li>
<li>Upgrade Wizard</li>
<li>All configuration</li>
<li>Clean up</li>
<li>Logout from Install Tool</li>
</ul>
<p>New proposed order:</p>
<ul>
<li>Important Actions</li>
<li>Configuration Presets</li>
<li>All Configuration</li>
<li>Upgrade Wizard</li>
<li>System environment</li>
<li>Folder Structure</li>
<li>Test Setup</li>
<li>Cleanup</li>
</ul>
<p>"Logout" is put below the menu as a link and "Welcome" is just the first screen but without any menu item for it.</p> TYPO3 Core - Task #55464 (Closed): Install Tool Lock Screen (Backend Mode) Stylinghttp://forge.typo3.org/issues/554642014-01-30T15:09:52ZErnesto Baschnyeb@cron.eu
<p>Warning icon misplaced in the Alert to "Unlock Install Tool" when called as a Backend Module. Fix it.</p> TYPO3 Core - Task #55453 (Closed): Install Tool > All Configuration "Expand All" functionalityhttp://forge.typo3.org/issues/554532014-01-30T12:32:56ZErnesto Baschnyeb@cron.eu
<p>To ease finding settings in the new Install Tool "All Configuration", we want to have an "Expand all" feature to expand (and collapse) all accordions at the same time.</p> TYPO3 Core - Task #54883 (Closed): Document that TYPO3 CMS is not compatible with MySQL strict modeshttp://forge.typo3.org/issues/548832014-01-09T18:00:11ZErnesto Baschnyeb@cron.eu
<p>TYPO3 is not currently compatible with MySQL configured with "STRICT_TRANS_TABLES" or "STRICT_ALL_TABLES" enabled.</p>
<p>There are currently several issues with this: <a class="issue tracker-1 status-6 priority-4 priority-default closed child" title="Bug: SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW499d21cdec168) (Rejected)" href="http://forge.typo3.org/issues/20052">#20052</a>, <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Unable to create a page (Closed)" href="http://forge.typo3.org/issues/21212">#21212</a>, <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Unable to login into BE when using MySQL 5+ (Closed)" href="http://forge.typo3.org/issues/15295">#15295</a>, <a class="issue tracker-1 status-5 priority-4 priority-default closed child" title="Bug: Installer will not create any be_users if unsupported sql_mode is used (Closed)" href="http://forge.typo3.org/issues/18821">#18821</a> and probably many more.</p>
<p>So while this is not solved (if even possible...) we should document how to configure MySQL to avoid this situation, because several "mysql installation documentation" (i.e. on Windows) recommend setting "STRICT_ALL_TABLES" by default.</p> TYPO3 Core - Epic #54542 (Closed): WP: Importer / Exporter with relations MM/IRRE/FALhttp://forge.typo3.org/issues/545422013-12-20T21:49:35ZErnesto Baschnyeb@cron.eu
<p>The import and export functionality is available since the beginning of TYPO3 CMS. This backend module mostly relies on the internal DataHandler/TCEMain system of TYPO3. For TYPO3 6.2 LTS, the Core Team needs to improve the handling of the IRRE and MM relations within the import and export process.<br />Additionally, the import / export module must be able to handle exports which were generated in a pre-FAL-version of TYPO3 (e.g. like the last LTS Version 4.5) in order to be able to import directly to the FAL.<br />Since importing and exporting large sites via a web-backend leads to problems in runtime and memory limits, a CLI Module must be added.</p>
<p>Epic for the work-package dealing with fixes in the Importer/Exporter module for inclusion in TYPO3 6.2 LTS.</p>
<p>Please do not add sub-tasks to this on your own, instead contact the release manager (Ernesto) before.</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 - Epic #54260 (Closed): WP: FAL Missing Issues / Features / APIhttp://forge.typo3.org/issues/542602013-12-07T14:56:05ZErnesto Baschnyeb@cron.euTYPO3 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 - Epic #24849 (Closed): Upgrade Wizard Usabilityhttp://forge.typo3.org/issues/248492011-01-27T11:06:34ZErnesto Baschnyeb@cron.eu
<p>The Upgrade Wizard of TYPO3 still lacks a better usability.</p>
<p>This is an umbrella-issue to collect the issues which we should solve in future TYPO3 versions.</p>
<p>Please add other issues which describe bugs, issues and problems with the Upgrade Wizard as a <strong>child</strong> of this issue. Thanks!</p>
<p>(issue imported from #M17353)</p>