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 - 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 #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 - 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 - Epic #54260 (Closed): WP: FAL Missing Issues / Features / APIhttp://forge.typo3.org/issues/542602013-12-07T14:56:05ZErnesto Baschnyeb@cron.euTYPO3 Core - Task #53988 (Closed): First Time Installation doesn't need a "beforePackageStatesMig...http://forge.typo3.org/issues/539882013-11-26T18:10:24ZErnesto Baschnyeb@cron.eu
<p>For a dummy blank new installation the Installer creates a LocalConfiguration.php in "old-school" way (with extList) and then converts that to PackageStates and moves the old file to LocalConfiguration.beforePackageStatesMigration.php.</p>
<p>This is ugly, as you find yourself with "old files" while you are just installing it for the first time.</p>
<p>Could be streamlined, so that the first time installation activates the packages automatically.</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 - Task #53829 (Closed): Improve usability of Filelist "Drag-Upload"http://forge.typo3.org/issues/538292013-11-21T11:14:14ZErnesto Baschnyeb@cron.eu
<p>We now can drag&upload files into the Filelist, which is cool. But it looks ugly.</p>
<p>The UX team provided us with a suggestion on how it could look and work.</p>
<p>Here are some points on how it should work:</p>
<p><a class="external" href="http://redpen.io/z2gdmu">http://redpen.io/z2gdmu</a></p>
<p>I think it would be great to have it like that:</p>
<p><img src="http://forge.typo3.org/attachments/download/25541/FAL-Upload.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #53814 (Closed): Doc-Module: Unclear different between "Manage" and "Show" Docu...http://forge.typo3.org/issues/538142013-11-20T21:33:43ZErnesto Baschnyeb@cron.eu
<p>As noted by the UX team, the selector between "Show" and "Manage" is confusing, as the difference is not quite clear at first.</p>
<p>See this comment:</p>
<p><a class="external" href="https://projects.invisionapp.com/share/H2IU7YVE#/screens/10260005/comments/6168385">https://projects.invisionapp.com/share/H2IU7YVE#/screens/10260005/comments/6168385</a></p>
<p>Not even to me it is clear what view is showing me what, and what exactly the "Download" does (because as an user, I expect to be able to "Download" the documentation myself.</p>
<p>Maybe rephrasing the menu items would be a better fit, or even merge the functionality in a single view? Why would I want to differentiate between "showing" or "managing"? We could display the whole list and then provide according actions depending if it has already been fetched locally or not.</p>
<p>@Xavier, would be great to have some input from you on that matter. Thanks!</p> TYPO3 Core - Task #53681 (Closed): Change wording for User Settings "Reset Configuration and Clea...http://forge.typo3.org/issues/536812013-11-15T19:45:26ZErnesto Baschnyeb@cron.eu
<p>In #632 it was proposed to change the text of the User Settings, Admin, "Reset Configuration and Clear Temporary Data" and "Clear Temporary Data".</p>
<p>Moreover both button labels point to the same CSH, and for an user its not really clear what the difference is at all.</p>
<p>Suggestions from Jens (<a class="external" href="http://forge.typo3.org/issues/632#note-15">http://forge.typo3.org/issues/632#note-15</a>):</p>
<blockquote>
<ul>
<li>Reset Configuration and clear temporary data
<ul>
<li>= Reset user settings</li>
</ul>
</li>
<li>Clear Temporary data
<ul>
<li>= Reset backend states</li>
<li>= Clear backend caching</li>
<li>= Remove Temporary Settings</li>
<li>= Reset interface states</li>
<li>.. other Ideas?</li>
</ul></li>
</ul>
</blockquote>
<p>Suggestions from Steffen R:</p>
<blockquote>
<ul>
<li>"Reset your backend status (open folders, list setting, tree collapse states, last open tabs..." </li>
<li>"Restore this form to default" :)</li>
</ul>
</blockquote> TYPO3 Core - Task #24900 (Closed): "Version Compatibility" Upgrade Wizard should not be displayed...http://forge.typo3.org/issues/249002011-01-31T10:47:55ZErnesto Baschnyeb@cron.eu
<p>The "Version Compatibility" wizard will always show up, even if nothing was changed to the FE rendering. So the user is left with a dialog which is pretty confusing (see screenshot upgrade-wizard-compatVersion.png).</p>
<p>Solution: only call this wizard if there is there is something to do.<br />(issue imported from #M17415)</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>