TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-08-09T17:07:24ZTYPO3 Forge
Redmine TYPO3 Core - Bug #101640 (Resolved): PHP Warning: Undefined array key "eval" in ...core/Classes/D...http://forge.typo3.org/issues/1016402023-08-09T17:07:24ZErnesto Baschnyeb@cron.eu
<p>In case I have a TCA "slug" field without a "eval" config, PHP 8 will bail out with this exception, for example when moving a page in the backend:</p>
<pre><code>PHP Warning: Undefined array key "eval" in /srv/www/www_dhbw_de/releases/60/private/typo3/sysext/core/Classes/DataHandling/DataHandler.php line 8390</code></pre> TYPO3 Core - Bug #45834 (Closed): Detection of curlProxyServer settings buggy on upgrade to 6.0http://forge.typo3.org/issues/458342013-02-25T19:24:39ZErnesto Baschnyeb@cron.eu
<p>In <a class="issue tracker-2 status-5 priority-3 priority-lowest closed behind-schedule" title="Feature: Include HTTP Request2 for better HTTP handling (Closed)" href="http://forge.typo3.org/issues/28344">#28344</a> "HTTP Request2" API was included. It supports detecting old school "curlProxyServer" settings and transfer these to the "new" setting under HTTP:</p>
<pre>
$proxyParts = explode(':', $GLOBALS['TYPO3_CONF_VARS']['SYS']['curlProxyServer'], 2);
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_host'] = $proxyParts[0];
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_port'] = $proxyParts[1];
</pre>
<p>This code ended up in Core/Bootstrap::transferDeprecatedCurlSettings() after namespace and bootstrapification.</p>
<p>I have always set up this setting like this:</p>
<pre>
$GLOBALS['TYPO3_CONF_VARS']['SYS']['curlProxyServer'] = 'http://proxy:3128';
</pre>
<p>I guess the implementator of the transferDeprecatedCurlSettings was only thinking about the "proxy:3128" kind of syntax. I end up with:</p>
<pre>
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_host'] = 'http'
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy_port'] = '//proxy:3128;
</pre>
<p>Other than that, I would also auto-set ['HTTP']['adapter'] to 'curl' if legacy 'curlUse' = TRUE.</p> TYPO3 Core - Bug #25772 (Closed): Resizeable textareas: scrollbar sticks to mousehttp://forge.typo3.org/issues/257722011-04-05T17:05:00ZErnesto Baschnyeb@cron.eu
<p>If you have resizeable textareas enabled and you try to use the scrollbar to scroll in your content with Internet Explorer 8, the re-sizing feature "sticks" to your mouse pointer (even after releasing the mouse button).</p>
<p>You can try it out with PageTS field in Page properties.</p> TYPO3 Core - Bug #25771 (Closed): Resizeable textareas with Internet Explorer (IE8): random jumps...http://forge.typo3.org/issues/257712011-04-05T17:03:08ZErnesto Baschnyeb@cron.eu
<p>Since 4.4 (?) textareas (e.g. PageTS field in the Page settings) are resizeable. With Internet Explorer there are some problems with it:</p>
<p>If in the user settings you disable the entry "Make Textareas Resizeable", you are not able to click on any line without causing the scrollbar to randomly jump around the content, thus making it very difficult to edit content in these fields.</p> TYPO3 Core - Bug #24914 (Closed): Upgrade Wizard "Install Outsourced System Extensions" should on...http://forge.typo3.org/issues/249142011-02-01T12:11:22ZErnesto Baschnyeb@cron.eu
<p>The Upgrade Wizard "Install Outsourced System Extensions" (tx_coreupdates_installsysexts) suggests the user to install all system extensions, even those which are already installed. This is confusing to the user that is doing a "new installation" based on the intro package for example, where all those extensions are already installed by default.</p>
<p>Solution would be to do the same logic as we have in "tx_coreupdates_installnewsysexts", which checks every extension if they are installed (and if all are installed, don't present the wizard at all!).</p>
<p>(issue imported from #M17429)</p> TYPO3 Core - Bug #24583 (Closed): Not installing extensions in Upgrade Wizard should also get rid...http://forge.typo3.org/issues/245832011-01-26T00:23:43ZErnesto Baschnyeb@cron.eu
<p>If one chooses not to install all suggested new sysext, the wizard should never been shown again.</p>
<p>Also solves the problem <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Update Failed! message even when update did not fail! (Closed)" href="http://forge.typo3.org/issues/24522">#24522</a>.</p>
<p>(issue imported from #M17320)</p> TYPO3 Core - Bug #24681 (Closed): CSH tooltips should be placed nearer to the texthttp://forge.typo3.org/issues/246812011-01-20T13:39:57ZErnesto Baschnyeb@cron.eu
<p>Since <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: CSH tooltip often gets in the way of the field it is supposed to provide help for (Closed)" href="http://forge.typo3.org/issues/24578">#24578</a> the tooltips are on top of the labels, improving the usability. But they are some px too far away. Also the (?) icon in the docheader, the arrow pointing out to the tooltip is not placed aligned with the icon.</p>
<p>Solution is to offset the pointer -10px and also move the tooltip closer with some ExtJS magic.</p>
<p>(issue imported from #M17163)</p> TYPO3 Core - Bug #24634 (Closed): Make the t3lib_utility_Mail hook subscriber optional / configur...http://forge.typo3.org/issues/246342011-01-18T10:03:45ZErnesto Baschnyeb@cron.eu
<p>t3lib_utility_Mail::mail subscribed hook allows "old applications" which used to send mail through it to go through SwiftMailer instead.</p>
<p>This allows old extensions which haven't been ported to make use of SwiftMailer to gain access to the configurability of SwiftMailer (different transports) and send RFC conformant E-Mails.</p>
<p>This works fine for simple cases but will fail as soon as the sending application already tried to create the MIME confirmity itself (e.g. by using other libraries or doing it on its own). We don't want to add a full MIME parsing routines in Core just because of that backwards compatibility!</p>
<p>Since this cannot be detected, we implement a switch to disable the subscribed hook.</p>
<p>So if your installation uses some extension which sends mails, test if it works and that the generated mails are ok "out of the box" (which means that the SwiftMail hook is working), if it is not working (e.g. empty body of the mail, wrong attachment count, or garbled mail content), use the switch to turn the hook off (which also means that the configured transport under [MAIL] are not regarded anymore, and mails are send using the old school mail() method.</p>
<p>(issue imported from #M17109)</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 #24271 (Closed): New sysext modules are placed incorrectly in the Web> module menuhttp://forge.typo3.org/issues/242712010-12-02T01:19:12ZErnesto Baschnyeb@cron.eu
<p>Since <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Sysext Modules are shown in Module Menu, even though extensions are not installed (Closed)" href="http://forge.typo3.org/issues/23599">#23599</a> the old "hardcoded" sysext list, perm, func and info lost their "fixed place" in the Web> modules menu. They now rely (like any other extension) in t3lib_extMgm::addModule().</p>
<p>Since they used to have after:layout in its calling, they were positioned after the "Web>Page" module. But since all had this property, they got added in the opposite order as intended.</p>
<p>We still don't have any other way to position modules besides "after" and "before", which is not flexible enough. Until we have a solution, I remove the hardcoded "after:layout" so that they get added in the order of loading (in extList). In the dummy + intro package I will order them correctly so that they appear after Page.</p>
<p>Your ordering might vary depending on when you installed those extensions.</p>
<p>(issue imported from #M16643)</p> TYPO3 Core - Bug #24267 (Closed): Install Tool is unuseable since DBAL merge (switches to a very ...http://forge.typo3.org/issues/242672010-12-01T20:50:47ZErnesto Baschnyeb@cron.eu
<p>Since tonights DBAL merging the install tool does not work anymore. One character wrong, but big impact. :)</p>
<p>(issue imported from #M16639)</p> TYPO3 Core - Feature #24240 (Closed): Provide a SwiftMailer transport that only saves send mails ...http://forge.typo3.org/issues/242402010-11-29T22:57:43ZErnesto Baschnyeb@cron.eu
<p>We introduced the SwiftMailer interface in t3lib_mail in 4.5 alpha2. So we can now generate RFC conformant mails and have a powerful mail engine available which also supports different transport mechanisms (like mail(), sendmail and direct SMTP).</p>
<p>To ease debugging mail sending in a TYPO3 installation, it might be useful for a complete installation not really <strong>send</strong> mails, but just save them to a file.</p>
<p>This RFC provides this feature, allowing the admin to configure the new transport "mbox", which saves all mails to a mbox-conformant file (simple text file, see RFC 4155). This file can be viewed with a regular text editor or a mail client which can open a "mbox" file.</p>
<p>Along with Jigal's RFC <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: The new Swift Mailer should be used by TYPO3 for sending all kinds of mail (Closed)" href="http://forge.typo3.org/issues/24222">#24222</a> which hooks into all other mail() usage we are now able to log every outgoing mail to a file!</p>
<p>This feature is a follow-up the the new mailing API and will be included according to the rules for "new features" in this phase (see <a class="external" href="http://forge.typo3.org/projects/typo3v45-projects/wiki/Feature_Freeze">http://forge.typo3.org/projects/typo3v45-projects/wiki/Feature_Freeze</a>, where "t3lib_mail" is listed as potential candidates for follow-ups).<br />(issue imported from #M16610)</p> TYPO3 Core - Feature #24147 (Closed): Remove Internet Explorer 6 supporthttp://forge.typo3.org/issues/241472010-11-20T13:04:01ZErnesto Baschnyeb@cron.eu
<p>Internet Explorer 6 will be last supported in 4.5 (Long Term Release), thus we decided to get rid of all specific IE6 (and related ancient browsers) starting in 4.6 already.</p>
<p>(issue imported from #M16490)</p> TYPO3 Core - Task #24146 (Closed): Remove ImageMagick 4 and ImageMagick 5 supporthttp://forge.typo3.org/issues/241462010-11-20T13:02:31ZErnesto Baschnyeb@cron.eu
<p>IM4 and IM5 support has been deprecated in 4.5 and since this is a long time support release we decided to remove support for it starting in 4.6 already to speed up the process of implementing fixes and new features in our image handling routines.</p>
<p>(issue imported from #M16489)</p> TYPO3 Core - Bug #24038 (Closed): SVG TypoScript object unuseable after tslib_content splituphttp://forge.typo3.org/issues/240382010-11-12T21:23:17ZErnesto Baschnyeb@cron.eu
<p>A minor typo in the ext_autoload makes the SVG not work anymore, because the class is not loaded.</p>
<p>(issue imported from #M16370)</p>