TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-03-15T19:52:56ZTYPO3 Forge
Redmine TYPO3 Core - Task #56941 (Closed): Return the 1-2-3 step icons in the step installerhttp://forge.typo3.org/issues/569412014-03-15T19:52:56ZErnesto Baschnyeb@cron.eu
<p>The 1-2-3 step installer could get the step icons back to visualize where the user is in the process of installation.</p>
<p>See <a class="external" href="https://redpen.io/xdk5sg">https://redpen.io/xdk5sg</a></p> TYPO3 Core - Bug #56770 (Closed): Install Tool flash messages in Step Installerhttp://forge.typo3.org/issues/567702014-03-11T16:51:49ZErnesto Baschnyeb@cron.eu
<p>The Step Installer sometimes want to present some "flash messages" which are passed over from one controller to the next through the session. Currently these messages are displayed over Step installer box.</p>
<p>And this looks ugly:</p>
<p><img src="http://forge.typo3.org/attachments/download/26211/install-tool-message-original.png" alt="" loading="lazy" /></p>
<p>This looks especially ugly in the first step of the Step Installer if the install tool tries to create the directory structure and fails on every single directory due to permission problems.</p>
<p>This is just a tiny adaptation to make it "less ugly", could be turned over again later on if we find an even better solution.</p>
<p>My pragmatic suggestion for now looks like this:</p>
<p><img src="http://forge.typo3.org/attachments/download/26212/install-tool-message-new.png" alt="" loading="lazy" /></p> TYPO3 Core - Feature #52090 (Closed): Merge Save Buttonshttp://forge.typo3.org/issues/520902013-09-17T22:40:56ZErnesto Baschnyeb@cron.eu
<p>To remove visual clutter it'd be great to merge the different save buttons into a split button drop down. Suggested to the UX team, designed and approved by Jens:</p>
<p><img src="http://forge.typo3.org/attachments/download/25002/TYPO3-Save-Selectbox-1.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/25003/TYPO3-Save-Selectbox-2.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/25004/TYPO3-Save-Selectbox-3.png" alt="" loading="lazy" /></p>
<hr />
<p>The CSS for this:</p>
<p>Arrow: <img src="http://forge.typo3.org/attachments/download/25005/small-arrow-down-8bit.png" alt="" loading="lazy" /> (inactive) = small-arrow-down-8bit.png</p>
<pre><code class="css syntaxhl" data-language="css"><span class="nc">.select-box-inactive-bg</span> <span class="p">{</span>
<span class="nl">border</span><span class="p">:</span> <span class="m">1px</span> <span class="nb">solid</span> <span class="m">#b3b3b3</span><span class="p">;</span> <span class="c">/* stroke */</span>
<span class="nl">background-color</span><span class="p">:</span> <span class="m">#cbcbcb</span><span class="p">;</span> <span class="c">/* color overlay */</span>
<span class="p">}</span>
</code></pre>
<pre><code class="css syntaxhl" data-language="css"><span class="nc">.select-box-hover-btn</span> <span class="p">{</span>
<span class="nl">border</span><span class="p">:</span> <span class="m">1px</span> <span class="nb">solid</span> <span class="m">#7b7b7b</span><span class="p">;</span>
<span class="nl">background-image</span><span class="p">:</span> <span class="n">-moz-linear-gradient</span><span class="p">(</span><span class="nb">bottom</span><span class="p">,</span> <span class="m">#d5d5d5</span> <span class="m">0%</span><span class="p">,</span> <span class="m">#f5f5f5</span> <span class="m">100%</span><span class="p">);</span>
<span class="nl">background-image</span><span class="p">:</span> <span class="n">-o-linear-gradient</span><span class="p">(</span><span class="nb">bottom</span><span class="p">,</span> <span class="m">#d5d5d5</span> <span class="m">0%</span><span class="p">,</span> <span class="m">#f5f5f5</span> <span class="m">100%</span><span class="p">);</span>
<span class="nl">background-image</span><span class="p">:</span> <span class="n">-webkit-linear-gradient</span><span class="p">(</span><span class="nb">bottom</span><span class="p">,</span> <span class="m">#d5d5d5</span> <span class="m">0%</span><span class="p">,</span> <span class="m">#f5f5f5</span> <span class="m">100%</span><span class="p">);</span>
<span class="nl">background-image</span><span class="p">:</span> <span class="n">linear-gradient</span><span class="p">(</span><span class="nb">bottom</span><span class="p">,</span> <span class="m">#d5d5d5</span> <span class="m">0%</span><span class="p">,</span> <span class="m">#f5f5f5</span> <span class="m">100%</span><span class="p">);</span>
<span class="p">}</span>
</code></pre>
<hr />
<p>Arrow: <img src="http://forge.typo3.org/attachments/download/25006/small-arrow-down-act-8bit.png" alt="" loading="lazy" /> (active) = small-arrow-down-act-8bit.png</p>
<pre><code class="css syntaxhl" data-language="css"><span class="nc">.select-box-contextmenu-active</span> <span class="p">{</span>
<span class="nl">border</span><span class="p">:</span> <span class="m">1px</span> <span class="nb">solid</span> <span class="m">#7b7b7b</span><span class="p">;</span>
<span class="nl">background-color</span><span class="p">:</span> <span class="m">#f7f7f7</span><span class="p">;</span>
<span class="nl">-moz-box-shadow</span><span class="p">:</span> <span class="m">0</span> <span class="m">1px</span> <span class="m">4px</span> <span class="n">rgba</span><span class="p">(</span><span class="m">0</span><span class="p">,</span><span class="m">0</span><span class="p">,</span><span class="m">0</span><span class="p">,</span><span class="m">.69</span><span class="p">);</span>
<span class="nl">-webkit-box-shadow</span><span class="p">:</span> <span class="m">0</span> <span class="m">1px</span> <span class="m">4px</span> <span class="n">rgba</span><span class="p">(</span><span class="m">0</span><span class="p">,</span><span class="m">0</span><span class="p">,</span><span class="m">0</span><span class="p">,</span><span class="m">.69</span><span class="p">);</span>
<span class="nl">box-shadow</span><span class="p">:</span> <span class="m">0</span> <span class="m">1px</span> <span class="m">4px</span> <span class="n">rgba</span><span class="p">(</span><span class="m">0</span><span class="p">,</span><span class="m">0</span><span class="p">,</span><span class="m">0</span><span class="p">,</span><span class="m">.69</span><span class="p">);</span>
<span class="p">}</span>
</code></pre> TYPO3 Core - Feature #12344 (Closed): Migrate to t3lib_htmlmail to SwiftMailerhttp://forge.typo3.org/issues/123442011-01-18T09:09:06ZErnesto Baschnyeb@cron.eu
<p>We have a new Mailer API in 4.5 based on SwiftMailer and we want to deprecate the use of t3lib_htmlmail. Which means we need to get rid of it all together.</p>
<p>Attached is an untested patch of what this would mean more or less for "linkvalidator". Please take a look at it, test it, and integrate that solution for the RC1 if possible.</p>
<p>See pending documentation at <a class="external" href="http://wiki.typo3.org/Pending_Documentation#t3lib_mail">http://wiki.typo3.org/Pending_Documentation#t3lib_mail</a></p>
<p>Thanks!</p> TYPO3 Core - Bug #12079 (Closed): Not possible to reactivate t3editor after deactivationhttp://forge.typo3.org/issues/120792011-01-10T22:21:26ZErnesto Baschnyeb@cron.eu
<p>When I de-select the checkbox "Deactivate t3editor" which is shown below the Info/Modify form of SETUP (or CONSTANT), there is no way of getting it back "active". If I unselect that checkbox again and SAVE, it is again activated as soon as I enter that form again.</p>
<p>This happens on 4.4 and current trunk. Would be cool to have that fixed for the 4.5.0 final release.</p> TYPO3 Core - Bug #12000 (Closed): Topbar: Cache and Favorites submenus shifts when in Workspaceshttp://forge.typo3.org/issues/120002011-01-07T18:44:03ZErnesto Baschnyeb@cron.eu
<p>Hi,</p>
<p>in Live mode, the Cache (and Favorites) submenu is positioned correctly:</p>
<p><img src="http://forge.typo3.org/attachments/download/4885/clear-cache-live-position.png" alt="" loading="lazy" /></p>
<p>As soon as you switch to a Draft Workspace (thus getting the dashed top bar), the position of the submenu is wrong:</p>
<p><img src="http://forge.typo3.org/attachments/download/4886/clear-cache-ws-position.png" alt="" loading="lazy" /></p>
<p>It seems that it shifts exactly the size of the Workspace name which is added on the top bar:</p>
<p><img src="http://forge.typo3.org/attachments/download/4887/clear-cache-ws-position-2.png" alt="" loading="lazy" /></p> TYPO3 Core - Feature #15150 (Closed): Get list of content elements for "new content" wizard from TCAhttp://forge.typo3.org/issues/151502005-10-24T23:14:28ZErnesto Baschnyeb@cron.eu
<p>We could remove the "hard-coded" content types from the "new content" wizard (cms/layout/db_new_content_el.php) and have the information about the CTypes come directly from the TCA. So we could add other CTypes to the wizard through extentions.</p>
<p>This means adding more parameters to TCA and have them being evaluated by the wizard.</p>
<p>Relates to 0001628.<br />(issue imported from #M1723)</p> TYPO3 Core - Bug #14984 (Closed): Editpanel confirm dialogs (del/hide) don't display umlauts/etchttp://forge.typo3.org/issues/149842005-09-21T12:57:08ZErnesto Baschnyeb@cron.eu
<p>The edit panel has a hide and delete buttons that open a javascript confirmation dialog. This works nice in englisch, but if the user has set the BE-language to a language that uses non-ascii chars in these strings (e.g. german), the confirmation dialogs appear with these characters displayed as URL-encoded UTF-8 entities.</p>
<p>The problem is that javascript dialogs doesn't support URL-encoded strings and not even UTF-8 entities.</p>
<p>The attached patch solves the problem, and allows us to display the confirmation prompts with umlauts etc. The solution is:</p>
<p>1) t3lib_tsfebeuserauth::extGetLL has a new parameter, allowing us to return the string in the default charset that the BE-user is using (instead of UTF-8 entities)<br />2) In tslib_content::editPanel we now get the strings for "hideConfirm" and "deleteConfirm" using this new parameter<br />3) In tslib_content::editPanelLinkWrap the $confirm parameter goes through $GLOBALS['LANG']->JScharCode() to get properly encoded and displayed in the dialog.</p>
<p>The attached patch was created for current CVS-head, but also applies to TYPO3 3.8.0 nicely.<br />(issue imported from #M1472)</p> TYPO3 Core - Bug #14921 (Closed): XHTML and accessibility of FORM cObjhttp://forge.typo3.org/issues/149212005-08-11T18:06:39ZErnesto Baschnyeb@cron.eu
<p>The cObj FORM currently doesn't render accessible mailforms, even if setting "accessible=1" in its conf. In a discussion in TYPO3-content-rendering mailing list (6.6.2005), ben van't ende proposed a patch, which can be found here:</p>
<p><a class="external" href="http://typo3.org/teams/content-rendering/get-the-x-into-html/">http://typo3.org/teams/content-rendering/get-the-x-into-html/</a></p>
<p>This hasn't been incorporated into CVS yet. I found some bugs in this implementation and added some enhancements, so we could apply it to CVS and have it included in 3.8.1.</p>
<p>What ben's patch solve:</p>
<p>- Added: FORM conf variable: fieldPrefix where we can set a prefix to use for all fields in this form (instead of the default "formName", which is probably an unique-hash).<br />- Added: FORM conf variable: dontMd5FieldNames where we can decide not to md5 the field names in the id fields.<br />- Fixed: generates one ID for each option on radio-fields, instead of reusing the same ID (generating invalid XHTML).<br />- Fixed: In strict XHTML mode, set the FORM ID instead of the NAME attribute.</p>
<p>My additions to ben's patch were:</p>
<p>- Added: In "accessibility" mode, we need to create a <fieldset> for the radio-buttons, so we have an ID to which the LABEL refers to. Else we end up with invalid XHTML (reference to unknown id). This is also the most "accessible" way (the field-label refers to the whole group of radio-buttons).<br />- Added: In radio-buttons, the descriptive text after the radio-button is the LABEL for this specific button. So this will now wrap a <LABEL> tag around the text with the correct ID (so one can click on the text next to the radio-buttons to activate them). Only in accessibilty=1.<br />- Fixed: Check for ctype_digit in formname before generating the prefix, else we might end up having a digit as the first character of the prefix.<br />- Fixed: ben's patch wouldn't work with accessible=0 (generates invalid XHTML).<br />- Fixed: On form elements of type "label", there is no element with an ID, so we should not create a LABEL-tag pointing to an ID that does not exist (generates invalid XHTML).</p>
<p>Attached is a patch that includes ben's and my additions. Read to be included in CVS for 3.8.1 (no change in features, just adds options).</p>
<p>This patch also applies to 3.8.0, for the interested reader! :)</p>
<p>(issue imported from #M1369)</p> TYPO3 Core - Bug #14914 (Closed): config.disableImgBorderAttr should override anythinghttp://forge.typo3.org/issues/149142005-08-08T14:32:13ZErnesto Baschnyeb@cron.eu
<p>The fix added to 3.8.0 for <a class="external" href="http://bugs.typo3.org/view.php?id=797">http://bugs.typo3.org/view.php?id=797</a> had a bug in that the disableImgBorderAttr was checked wrongly. Now there is a fix for it in CVS, but it still isn't right:</p>
<p>class.tslib_content.php, line 2518:</p>
<pre><code>if (!t3lib_div::inList('xhtml_strict,xhtml_11,xhtml_2',$GLOBALS['TSFE']->config['config']['doctype']) || !$GLOBALS['TSFE']->config['config']['disableImgBorderAttr']) {<br /> return $borderAttr;<br /> }</code></pre>
<p>I would like the disableImgBorderAttr attribute to override any other setting, so that I could turn off the border-tags even if my doctype is xhtml_trans. This is not possible. A simple solution would be to change the logic in the test from OR (||) to AND (&&).</p>
<p>(issue imported from #M1360)</p> TYPO3 Core - Feature #14894 (Closed): stdWrap.age should differenciate between singular/pluralhttp://forge.typo3.org/issues/148942005-08-02T13:39:17ZErnesto Baschnyeb@cron.eu
<p>The .age stdWrap parameter currently only allows us to specify " min| hrs| days| yrs", which will also show plural text if we have a quantity of "1". The attached patch (for typo3/sysext/cms/tslib/class.tslib_content.php) changes the possible value of the .age setting to allow 8 values:</p>
<p>" min| hrs| days| yrs| min| hour| day| year"</p>
<p>The second set is the singular variant. So we can have outputs like "1 hour" and "1 year". It remains backwards compatible, in that older TYPO3 (with newer TypoScript) will still show the "good-old" plural variants.</p>
<p>In a remote future this text should become language-dependent, so that we have different outputs depending on the language of the site. This should also be prepared for situations where not always is the "1" unit singular and all others plural. There are languages where there are other rules for plurals (see gettext, PO-setting "Plural-Forms").<br />(issue imported from #M1333)</p> TYPO3 Core - Feature #14889 (Closed): Place ADMINPANEL where I want tohttp://forge.typo3.org/issues/148892005-07-29T17:14:28ZErnesto Baschnyeb@cron.eu
<p>Currently the ADMIN-PANEL is just appended to the webpages output (even after the closing </html>. Usually this is ok, but sometimes not: Especially if we have XHTML-strict pages where layouting is controlled by CSS, the admin-panel might appear "who knows where", while also destroying the XHTML-validity, making browsers render the page "who knows how".</p>
<p>My feature-request would be a way to place the ADMIN PANEL wherever I want through TypoScript, maybe having it as a cObject, e.g.</p>
<p>page.10.marks.PANEL = ADMINPANEL</p>
<p>and then maybe have some ways to configure the admin panel in this object.</p>
<p>Good? Bad? Any objection?</p>
<p>(issue imported from #M1323)</p> TYPO3 Core - Feature #14886 (Closed): stdWrap for TMENUITEM's ATagParamshttp://forge.typo3.org/issues/148862005-07-29T15:55:41ZErnesto Baschnyeb@cron.eu
<p>Currently the ATagParams of a TMENUITEM is just a string. But sometimes you want to do fancy stuff with this information, like e.g:</p>
<pre><code>ATagParams = accesskey="{field:tx_govaccesskey_accesskey}" tabindex="{field:tx_govaccesskey_tabindex}"</code></pre>
<p>This doesn't work right now, because the ATagParams is not going through stdWrap.</p>
<p>So this feature-request, which is already implemented using the attached patch (for 3.8-release), simply passes the ATagParam through stdWrap if there are stdWrap properties. With this patch applied, this would allow something like:</p>
<pre><code>ATagParams = accesskey="{field:tx_govaccesskey_accesskey}" tabindex="{field:tx_govaccesskey_tabindex}" <br /> ATagParams.insertData = 1</code></pre>
<p>(issue imported from #M1320)</p> TYPO3 Core - Bug #14601 (Closed): XHTML compliance of GMENU with onmouseover imageshttp://forge.typo3.org/issues/146012005-03-08T13:11:59ZErnesto Baschnyeb@cron.eu
<p>Currently a GMENU is transformed into links like:</p>
<p><a onmouseover="over('...')" onmouseout="over('...')" href="..."><img name="..." .../></a></p>
<p>The problem is the "name" attribute in the <img> tag, which is not allowed in XHTML 1.1. The proper replacement is the "id" attribute.</p>
<p>But replacing this breaks the over() and out() JavaScript functions (at least on IE).</p>
<p>So the solution is to:</p>
<p>- use 'id' instead of 'name' in tslib/class.tslib_menu.php<br />- fallback to getElementById(name) in the generated javascript, so that IE will find the img we are referring to</p>
<p>Attached is a patch on the current (8.3.2005) CVS HEAD with these changes.</p>
<p>(issue imported from #M874)</p> TYPO3 Core - Bug #14491 (Closed): XHTML 1.0 strict compliance of FORM objects (hidden fields)http://forge.typo3.org/issues/144912005-01-13T13:41:15ZErnesto Baschnyeb@cron.eu
<p>FORM objects generate hidden fields that are not enclosed by any other block-level tags. This is not legal according to XHTML 1.0 strict, so e.g. pages with a mailform content object fail to validate. Attached is a patch to solve this problem (it just adds a <div> around the hidden fields block).</p>
<p>(issue imported from #M678)</p>