TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-03-16T14:41:36ZTYPO3 Forge
Redmine 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 - Bug #56950 (Closed): Additional margin on top of ExtJS context menushttp://forge.typo3.org/issues/569502014-03-16T02:06:10ZErnesto Baschnyeb@cron.eu
<p>In the page tree, the context menu got an additional wrong top margin due to the removal of the ExtJS normalization (<a class="issue tracker-1 status-5 priority-4 priority-default closed parent" title="Bug: Missing margin/padding on content element fields (Closed)" href="http://forge.typo3.org/issues/56418">#56418</a>).</p> TYPO3 Core - Bug #53692 (Closed): Backend background color is limited to height:100%http://forge.typo3.org/issues/536922013-11-16T13:27:25ZErnesto Baschnyeb@cron.eu
<p>In several backend screens where there is need to scroll, the background color stops at 100% height. This can be seen for example in the Login screen (dark gray ends abruptly when scrolling down), the Element browser (gray background) and others.</p>
<p>This is a regression introduced with <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Integrate normalize css reset (Closed)" href="http://forge.typo3.org/issues/47920">#47920</a> (adding the normalizer.css) and needs to be fixed until 6.2 release.</p>
<p>The UX team noted that also: <a class="external" href="https://projects.invisionapp.com/share/H2IU7YVE#/screens/10263303/comments/6159625">https://projects.invisionapp.com/share/H2IU7YVE#/screens/10263303/comments/6159625</a></p> TYPO3 Core - Feature #53685 (Closed): Add edit icons to Backend User "Compare" viewhttp://forge.typo3.org/issues/536852013-11-15T22:14:24ZErnesto Baschnyeb@cron.eu
<p>The Backend Users "Compare" view lack some sort of "action buttons".</p>
<p>UX team noted that here:</p>
<p><a class="external" href="https://projects.invisionapp.com/share/H2IU7YVE#/screens/481308/10259907/comments/6169317">https://projects.invisionapp.com/share/H2IU7YVE#/screens/481308/10259907/comments/6169317</a></p>
<p>An improvement would be to have "Edit User" pen icons on the header row besides the usernames to be able to edit them directly from here if desired.</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 - Task #29802 (Closed): Add SwiftMailer license exception to be included in TYPO3v4http://forge.typo3.org/issues/298022011-09-15T11:58:51ZErnesto Baschnyeb@cron.eu
<p>SwiftMailer Library, which is included since TYPO3v4 as the engine behind "t3lib_mail" in typo3/contrib/swiftmailer is licensed LGPLv3. This is not per-se includeable in a GPLv2 product as TYPO3v4 is.</p>
<p>So we've got an exception from the SwiftMailer author, which will be included in typo3/contrib/swiftmailer/LICENSE.TYPO3v4-Exception.</p> 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 - 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 #24571 (Closed): Backend search throws Exceptions / SQL errors when running as n...http://forge.typo3.org/issues/245712011-01-14T15:05:39ZErnesto Baschnyeb@cron.eu
<p>When a non-admin tries the BE live search, SQL errors are thrown (and you see them in the debug console if this is active). Only happens for non-admin users.</p>
<p>(issue imported from #M17032)</p> TYPO3 Core - Bug #23799 (Closed): Add IfModule mod_rewrite.c to misc/advanced.htaccesshttp://forge.typo3.org/issues/237992010-10-20T09:42:15ZErnesto Baschnyeb@cron.eu
<p>The introduction package creates its own .htaccess file which contains <IfModule mod_rewrite.c>.</p>
<p>I would like to have that IfModule in misc/advanced.htaccess so that the introduction package could ship with our misc/advanced.htaccess, instead of creating its own .htaccess file.</p>
<p>The usage of misc/advanced.htaccess will be then added to the intro-package packaging script.</p>
<p>I would like to commit this also for 4.4, so that we can also use this in the 4.4 introduction packaging script.<br />(issue imported from #M16075)</p> TYPO3 Core - Bug #23798 (Closed): Add new API t3lib_befunc::helpTextArray and use it in the ExtDi...http://forge.typo3.org/issues/237982010-10-20T09:30:50ZErnesto Baschnyeb@cron.eu
<p>Currently the ExtDirect which fetches the tooltip fetches the information on its own from the $TCA_DESCR array. It will also render "TYPO3 Inline Help" as a default header if none is given and will not render an "arrow" which used to symbolize a link to a popup in its content.</p>
<p>This patch adds a new API function t3lib_befunc::helpTextArray which is then used by t3lib_befunc::helpText and also the new ExtDirect call to fetch the information. The tooltips now won't have a title anymore if there is no "alttitle" defined.</p>
<p>Almost none CSH uses "alttile", so usually you won't see any. There are some examples in the Extension manager (e.g. the main titles "Loaded Extensions" etc).<br />(issue imported from #M16074)</p> TYPO3 Core - Feature #23743 (Closed): Allow skins to register sprites through addIconSpritehttp://forge.typo3.org/issues/237432010-10-15T21:21:37ZErnesto Baschnyeb@cron.eu
<p>Currently, extensions can register sprites using t3lib_spriteManager::addIconSprite(). This requires an array of icons (which will be added to $TBE_STYLES['spritemanager']['spriteIconsAvailable']) and the CSS filename which contains the generated sprite.css.</p>
<p>A skin might also want to provide a different sprite, but the skin's CSS files are already loaded automatically from the registered directory. See <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Core lacks "current" flags (Closed)" href="http://forge.typo3.org/issues/23266">#23266</a> where t3skin wants to add a sprite for flags. After this fix, we will use the API to do so in t3skin, simply not passing the CSS filename, but just the array of images.</p>
<p>(issue imported from #M16007)</p> TYPO3 Core - Bug #22235 (Closed): "Show" clickmenu in page tree generates wrong URLhttp://forge.typo3.org/issues/222352010-03-04T09:19:32ZErnesto Baschnyeb@cron.eu
<p>If we don't have any sys_domain record in our page tree, the clickmenu "Show" will generate a link like:</p>
<p><a class="external" href="http://example.com//index.php?id=xx">http://example.com//index.php?id=xx</a></p>
<p>Note the double "//" before index.php. This won't work if you have realurl installed (it doesn't even need to be enabled for your site):</p>
<p>"Error!</p>
<p>Reason: "index.php" could not be found, closest page matching is<br />"</p>
<p>(issue imported from #M13740)</p> TYPO3 Core - Bug #22234 (Closed): "Show" clickmenu in page tree does not work for mount pageshttp://forge.typo3.org/issues/222342010-03-04T09:08:14ZErnesto Baschnyeb@cron.eu
<p>Clicking the "Show" on a page which is a mount point to somewhere else brings the error:</p>
<p>"The requested page didn't have a proper connection to the tree-root! (Illegal Mount Point found in rootline)"</p>
<p>(issue imported from #M13739)</p> TYPO3 Core - Bug #15989 (Closed): Alignment of text in Text w/ images and "nowrap" is wrong (FF)http://forge.typo3.org/issues/159892006-04-05T16:38:32ZErnesto Baschnyeb@cron.eu
<p>In RC3, creating an content element of type "Text with images" and setting the position of images to be "in text, left" or "in text, right" (NOWRAP!), the text is misaligned if its longer than the image-block height. Right after the image-block ends, the text flows 10px to the left (or right) in the default setup (or "x"px, if the textMargin constant was changed).</p>
<p>This seem to be the problem reported by Franz Koch in the Content Rendering Group.</p>
<p>Please check the attached patch if the problems were solved, Franz Koch. If there are any other problems that aren's solved by this patch, please give more feedback on steps to reproduce the problem.<br />(issue imported from #M3138)</p>