TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-03-16T02:06:10ZTYPO3 Forge
Redmine 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 #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 #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 - Bug #52261 (Closed): Bad position of eval=>null checkbox http://forge.typo3.org/issues/522612013-09-25T14:24:41ZErnesto Baschnyeb@cron.eu
<p>The new TCA feature "eval=>null" places a new checkbox as a wizard besides your input field. This seem to look "ok" in the sys_file_reference case (which uses the "useOrOverridePlaceholder" mode), but it looks ugly in case you have regular (non-palette) field:</p>
<p><img src="http://forge.typo3.org/attachments/download/25063/eval-null-checkbox.png" alt="" loading="lazy" /></p>
<p>Also note that a potential "options-palette" icon is misplaced too.</p>
<p>The checkbox must be placed nearer to the input field itself.</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 #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 #24516 (Closed): Backwards compatibility in PHP_SCRIPT and accessing $this-> met...http://forge.typo3.org/issues/245162011-01-11T18:27:27ZErnesto Baschnyeb@cron.eu
<p>Older sites might include PHP_SCRIPT cObject accessing cObject methods through $this->. Since the PHP_SCRIPT object was moved to its own class, the old methods will stop working (e.g. older "languageMenu.php" or stuff like <a class="external" href="http://www.sk-typo3.de/awstats-Zaehlen-von-Dateidownloads.55.0.html">http://www.sk-typo3.de/awstats-Zaehlen-von-Dateidownloads.55.0.html</a></p>
<p>Solution is to add a __call() catch-all to PHP_SCRIPT intercepting those calls and passing them to $this->cObj, while making a note of it in deprecation log.<br />(issue imported from #M16970)</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 - Bug #23482 (Closed): Change all core PHP files to UTF8 encodinghttp://forge.typo3.org/issues/234822010-08-30T20:48:59ZErnesto Baschnyeb@cron.eu
<p>We want to have UTF8 PHP files in order to give proper credit to authors containing non-ASCII characters in their names. This mostly affects PHP comments.</p>
<p>(issue imported from #M15601)</p> TYPO3 Core - Bug #23281 (Closed): Backend shortcut cannot be set in IE8http://forge.typo3.org/issues/232812010-07-27T20:39:25ZErnesto Baschnyeb@cron.eu
<p>When you add any item in backend as a shortcut (using the "star with a +") using IE8, the shortcut icon disappears and a JS error occurs. The current module is <strong>not</strong> added to the shortcut list</p>
<p>(issue imported from #M15252)</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> TYPO3 Core - Bug #15902 (Closed): Calling PHP5-only iconv functions in PHP4http://forge.typo3.org/issues/159022006-03-27T10:58:03ZErnesto Baschnyeb@cron.eu
<p>A change in t3lib_cs that made it into RC2 (cvs diff -r 1.53 -r 1.54 t3lib/class.t3lib_cs.php) added some functions that are only available on PHP5 if the user chooses "iconv" (iconv_substr, iconv_strlen, iconv_strpos, iconv_strrpos). If using PHP4 with iconv support, I will get lots of errors:</p>
<p>Fatal error: Call to undefined function: iconv_strlen() in ....t3lib/class.t3lib_cs.php on line 1388</p>
<p>Attached patch checks if the functions are available before calling them.<br />(issue imported from #M2994)</p>