TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-03-23T17:58:02ZTYPO3 Forge
Redmine 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 - Bug #56951 (Closed): New page wizard broken tree lineshttp://forge.typo3.org/issues/569512014-03-16T02:16:07ZErnesto Baschnyeb@cron.eu
<p>The new page wizard (URL like /typo3/db_new.php?id=xx&pagesOnly=1) looks ugly.</p>
<p>Reas is because there is a mix of new styled t3-tree 30px high tree lines, and not yet reworked "halfline.gif".</p>
<p>Solution would be to include also a higher "halfline.gif" in the new t3-treeline sprite (typo3/sysext/t3skin/images/icons/treeline/) and make use of this new markup in this wizard.</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 #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 - Bug #53891 (Closed): Upgrade Wizard "Migrate file relations" should hide itselfhttp://forge.typo3.org/issues/538912013-11-22T21:18:22ZErnesto Baschnyeb@cron.eu
<p>If there are nothing left to migrate, the Upgrade Wizard "Migrate all file relations from tt_content.image and pages.media" should hide itself. Currently this is the only Upgrade Wizard which is always shown, and this is confusing to the user.</p> TYPO3 Core - Feature #53890 (Closed): Upgrade Wizard, first step should be Database Migrationhttp://forge.typo3.org/issues/538902013-11-22T21:13:20ZErnesto Baschnyeb@cron.eu
<p>The first "Upgrade Wizard" should be a Database Analyser step that just migrates the database to the newly added features (new fields, new tables, new indexes). No "dropping" of any field at this point (as a later upgrade Wizard might need the information in them).</p>
<p>This first Upgrade Wizard could present a list of changes that will be done and a single checkbox bellow to "accept" that changes.</p>
<p>This Wizard should "hide itself" if it detects that there are no changes required.</p> TYPO3 Core - Task #52405 (Closed): Install Tool: Allow multiple status messages for a single Filehttp://forge.typo3.org/issues/524052013-09-30T20:01:09ZErnesto Baschnyeb@cron.eu
<p>Sometimes a file has incorrect content <strong>and</strong> incorrect permissions. Currently only the permission problem is displayed and only after fixing that this uncovers the "wrong content" problem.</p>
<p>We want to see as much "errors" in the same time, thus allow File and Directory status checks to return several errors / warnings at once.</p> TYPO3 Core - Feature #51730 (Closed): EM should only install extensions compatible with current T...http://forge.typo3.org/issues/517302013-09-04T16:01:54ZErnesto Baschnyeb@cron.eu
<p>When the EM fetches the "latest extension version" it should also consider the typo3 dependency constrain so that only extension versions compatible with the current TYPO3 version are considered.</p>
<p>This goes in line with the <a href="http://typo3.org/news/article/announcing-ter-cleanup-process/" class="external">TER cleanup initiative</a></p>
<p>It would also allow extension authors to provide extension versions for different TYPO3 releases.</p>
<p>Some issues / conflicts could still arise with this, like:</p>
<p>Extension A compatible with TYPO3 6.2 depends on Extension B which does not have a TYPO3 6.2 compatible version (yet).</p>
<p>So maybe there should still be "some way" to overrule this compatibility check in cases where the admin is sure of what he's doing.</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 - Feature #50481 (Closed): TCEforms: Replace "More options" icon for uncollapsing pale...http://forge.typo3.org/issues/504812013-07-27T00:09:55ZErnesto Baschnyeb@cron.eu
<p>The icons to collapse and expand the Palettes ("More options") is not very usable.</p>
<p>As discussed in the UX Team #50354, we want to replace the icon with the small arrow (used also by the IRRE collapsing-feature) along with the palettes label as text (or text "More options" in case there is no label for this palette):</p>
<ul>
<li>> More options <- completely clickable</li>
</ul>
<p>As soon as it is clicked, the palette is uncollapsed and the arrow points down and the text changes to:</p>
<ul>
<li>v Less options (or the label)</li>
</ul>
<p>While doing that change, the icon should be aligned back with the field above it (move it some px to the LEFT), probably by removing the inline-style "margin-left: 20px;" and adding a new class to the TD instead.</p> TYPO3 Core - Bug #43331 (Closed): "Strict standards: Declaration of "CompatbilityClassLoaderPhpBe...http://forge.typo3.org/issues/433312012-11-27T09:27:34ZErnesto Baschnyeb@cron.eu
<p>On PHP < 5.3 I get this warning on top of the login screen (and also in the whole backend, making it completely unusable):</p>
<p>Strict standards: Declaration of TYPO3\CMS\Core\Compatibility\CompatbilityClassLoaderPhpBelow50307::requireClassFileOnce() should be compatible with that of TYPO3\CMS\Core\Core\ClassLoader::requireClassFileOnce() in /.../typo3_src/typo3/sysext/core/Classes/Core/SystemEnvironmentBuilder.php on line 239</p>
<p>Acording to git bisect this got broken with change <a class="issue tracker-4 status-5 priority-3 priority-lowest closed" title="Task: Protect bootstrap methods (Closed)" href="http://forge.typo3.org/issues/43285">#43285</a>.</p>
<p>Indeed the declaration of the methods differ:</p>
<pre>
class ClassLoader {
...
static protected function requireClassFileOnce($classPath) {
...
</pre>
<pre>
class CompatbilityClassLoaderPhpBelow50307 extends \TYPO3\CMS\Core\Core\ClassLoader {
...
static public function requireClassFileOnce($classPath, $className) {
...
</pre>
<p>And by the way, the classname CompatbilityClassLoaderPhpBelow50307 is misspelled (misses an "i" in Compat*i*bility).</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 #25398 (Closed): TCEforms draws huge empty icon row which on select-fields, maki...http://forge.typo3.org/issues/253982011-03-25T20:18:25ZErnesto Baschnyeb@cron.eu
<p>Certain fields of type "select" which offer records from a "foreign_table" will contain a huge amount of t3-icon-empty icons just below the select box. If you have enough of them, you even get a horizotanl scrollbar.</p>
<p>See some screenshots here:<br /><a class="external" href="http://forge.typo3.org/issues/13422">http://forge.typo3.org/issues/13422</a></p>
<p>The issue is not a CSS issue, but a bug in the rendering of such a field.</p>
<p>See it in action in tt_content field "sys_language". Just create enough sys_language records so that you see the row of empty icons being created. This wasn't this way before.</p>
<p>(issue imported from #M18041)</p>