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 #53683 (Closed): Don't underline the whole preview text in Web>Page content elem...http://forge.typo3.org/issues/536832013-11-15T21:55:21ZErnesto Baschnyeb@cron.eu
<p>Since we underline links in the backend, the Web>Page also renders all preview text inside content element boxes in underline on mouse over, because those are also links (to the edit windows). This is cluttery and ugly. So get rid of the underline of the preview text!</p>
<p>Reported and wished by the UX team.</p> TYPO3 Core - Bug #53075 (Closed): Do not auto-load SC_* classeshttp://forge.typo3.org/issues/530752013-10-23T14:41:55ZErnesto Baschnyeb@cron.eu
<p>The SC_* classes contain runnable code, and thus cannot be "auto-loaded". This was discovered due to crashes in the phpunit tests for 4.7 (by travis).</p>
<p>So fixing this will also fix broken travis.</p> TYPO3 Core - Bug #52779 (Closed): Exception if uninstalled extension has "wrong key"http://forge.typo3.org/issues/527792013-10-14T12:01:03ZErnesto Baschnyeb@cron.eu
<p>I know of tons of installations where some <strong>deinstalled</strong> extension in typo3conf/ext/ gets renamed to "tt_news.old" or "news.bak" etc. This was no problem before.</p>
<p>With the new package management feature, this now throws an exception on first hit:</p>
<pre><code>InvalidPackageKeyException('"' . $packageKey . '" is not a valid package key.', 1217959510)</code></pre>
<p>Solution:</p>
<p>The loop that scans for packages should skip those who's key is not invalid, in order to avoid an exception later down the road.</p> TYPO3 Core - Bug #52437 (Closed): Don't write LocalConfiguration on every Install Tool entryhttp://forge.typo3.org/issues/524372013-10-01T17:01:03ZErnesto Baschnyeb@cron.eu
<p>Silent Updater "removeObsoleteLocalConfigurationSettings" will always kick in and save the current LocalConfiguration even if nothing has to be changed.</p>
<p>If you have a non-writeable LocalConfiguration.php you will then end up in an Exception in this step already, without the installer having a chance to kick in and handle it in a more "gentle" way (needs improvements too, will need some further issues).</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 #43466 (Closed): Drag&Drop in page module broken in Chromehttp://forge.typo3.org/issues/434662012-11-29T22:45:19ZErnesto Baschnyeb@cron.eu
<p>In current master (and branch 6.0) the drag&drop functionality is broken in Chrome (and potentially also Safari?).</p>
<p>This used to work on 6.0.0 release.</p>
<p>Using git bisect I was able to identify the change that broke it: <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: BE login shows unaesthetic scrollbars (Closed)" href="http://forge.typo3.org/issues/43330">#43330</a>. Looks harmless, but reverting it makes drag&drop work again.</p>
<p>Any candidates to explain that? :)</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 #13320 (Closed): Don't use cross-extension dependencies (e.g. em)http://forge.typo3.org/issues/133202011-02-24T08:15:08ZErnesto Baschnyeb@cron.eu
<p>Hi,</p>
<p>please apply the following change which was included in typo3_src already:</p>
<p><a class="external" href="http://forge.typo3.org/projects/typo3v4-core/repository/revisions/10615">http://forge.typo3.org/projects/typo3v4-core/repository/revisions/10615</a></p>
<p>We will release 4.5.1a with this fix included and want to make sure that it doesn't happen again.</p>
<p>Thanks!</p> TYPO3 Core - Bug #12385 (Closed): Conflict scheduler:testtask with linkvalidator::taskhttp://forge.typo3.org/issues/123852011-01-20T00:58:01ZErnesto Baschnyeb@cron.eu
<p>Please consider this report, and check if its really valid. If so, please rename the field, would be the easiest option:</p>
<p><a class="external" href="http://bugs.typo3.org/view.php?id=17152">http://bugs.typo3.org/view.php?id=17152</a></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 #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 #21336 (Closed): Encryption key can be recalculated when using normal mailform w...http://forge.typo3.org/issues/213362009-10-22T11:11:35ZErnesto Baschnyeb@cron.eu
<p>These settings required for being exploitable:<br />['TYPO3_CONF_VARS']['FE']['secureFormmail'] 0<br />['TYPO3_CONF_VARS']['FE']['strictFormmail'] 0</p>
<p>Reported by Stefan Schuler.</p>
<p>Security Team OTRS reference: 2009021010000086 <br />(issue imported from #M12310)</p>