TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692022-12-18T18:31:48ZTYPO3 Forge
Redmine TYPO3 Core - Task #99391 (New): Deprecate files DataProcessor in menu elementshttp://forge.typo3.org/issues/993912022-12-18T18:31:48ZChristoph Lehmannchristoph.lehmann@networkteam.com
<p>The files DataProcessor is configured many menu elements, but its result is not used in the template. This leads to superflous unnecessary database queries.</p>
<p>Example:</p>
<ul>
<li>fluid_styled_content/Configuration/TypoScript/ContentElement/MenuAbstract.typoscript </li>
<li>fluid_styled_content/Resources/Private/Templates/MenuAbstract.html</li>
</ul> TYPO3 Core - Bug #99198 (Needs Feedback): MenuProcessor returns wrong menuhttp://forge.typo3.org/issues/991982022-11-25T16:16:01ZOliver Schmidtoliver.schmidt@ph-karlsruhe.de
<p>Hello together,<br />in our pagetree we use folders in rootline to organize our multidomain typo3 instance:</p>
<pre>
- domain[0] (folder)
-- subdomain[0].domain[0] (page site_root)
-- subdomain[1].domain[0] (page site_root)
- domain[1] (folder)
-- subdomain[0].domain[1] (page site_root)
-- subdomain[1].domain[1] (page site_root)
...
</pre>
<p>At TYPO3 Version 11 the MenuProcessor returned a menu based on site_root and included only pages of the correct domain. At TYPO3 Version 12 the MenuProcessor returns a menu based on pid 0 with all root pages.</p>
<pre>
dataProcessing {
10 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
10 {
levels = 4
as = mainnavigation
}
}
</pre>
<p>At TYPO3 Version 11 the var leveluid:0 returned the id of site_root. At TYPO3 Version 12 the var leveluid:0 returns the folder id.<br />Is this a bug, or the new intended behavior? If it is intended, is there a workaround to use folders as described above?</p>
<p>Thank you. Greetings<br />Oliver</p> TYPO3 Core - Feature #97765 (New): [FEATURE] Add fetchpriority attribute to imageshttp://forge.typo3.org/issues/977652022-06-13T16:51:47ZMarcus Förster
<p><a class="external" href="https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/fetchPriority">https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/fetchPriority</a></p>
<p>btw/ also includes a FIX for <a class="external" href="https://git.typo3.org/typo3/typo3/-/commit/c0e99719e17b275a2a85a676ea9ed60c22999476#0699b190324a5112dfae21e20ce8d9fbbff53e64_24_26">https://git.typo3.org/typo3/typo3/-/commit/c0e99719e17b275a2a85a676ea9ed60c22999476#0699b190324a5112dfae21e20ce8d9fbbff53e64_24_26</a></p> TYPO3 Core - Feature #97255 (Needs Feedback): Media queries for fschttp://forge.typo3.org/issues/972552022-03-29T19:00:18ZBernhard Ecklbernhard@eckl-medien.de
<p>Fluid styled content still has no media queries in the default css styles. Nowadays css with media queries should be included (even if no bootstrap package is used).</p> TYPO3 Core - Feature #93780 (New): New File Icons for Uploadshttp://forge.typo3.org/issues/937802021-03-19T09:33:01ZNils Hodyaspost@dietantejensen.de
<p>The icon set we're using is around since at least v4. They now are too small, and they should be SVG instead of GIF. Oh, and extensions are missing.<br />I'd be happy to work on that issue.</p>
<p>(Actually, I believe the extension-icon should be provided as a background-image via CSS, but that is a different issue.)</p>
<p>Related: <a class="wiki-page" href="#75572">#75572</a></p> TYPO3 Core - Bug #93375 (New): Superfluous p-tags added by lib.parseFunc.makelinks when link is p...http://forge.typo3.org/issues/933752021-01-28T11:26:45ZTorben Hansenderhansen@gmail.com
<p>When <code>lib.parseFunc.makelinks = 1</code> is set (default), superfluous p-tags are added when the string contains additional tags (e.g. em or strong).</p>
<p>Raw input created with CK Editor in the TYPO3 backend:</p>
<pre>
<p>This text contains an string URL https://www.typo3.org and no superfluous p-tags are added by lib.parseFunc.makelinks</p>
<p>This text <em>contains</em> an string URL https://www.typo3.org and <em>superfluous</em> p-tags are by lib.parseFunc.makelinks.</p>
<p>This text <strong>contains</strong> an string URL https://www.typo3.org and <strong>superfluous</strong> p-tags are added by lib.parseFunc.makelinks.</p>
<p>This text <strong>contains</strong> an linked URL <a href="https://www.typo3.org">https://www.typo3.org</a> and no <strong>superfluous</strong> p-tags are added by lib.parseFunc.makelinks.</p>
</pre>
<p><strong>Expected Result (screenshot):</strong></p>
<p><img src="http://forge.typo3.org/attachments/download/35808/fsc-input.png" alt="" loading="lazy" /></p>
<p><strong>Current Result (screenshot):</strong></p>
<p><img src="http://forge.typo3.org/attachments/download/35809/fsc-output.png" alt="" loading="lazy" /></p> TYPO3 Core - Feature #93247 (New): Modernize "Textmedia" and extend "Media Adjustments"http://forge.typo3.org/issues/932472021-01-08T15:22:50ZJan Kornblumjan.kornblum@googlemail.com
<p>Options for "Textmedia" set by "Media Adjustments" should be modernized. In my opinion "imagewidth" and "imageheight" don't make sense any longer in times of responsive websites. Instead, two new options should be added:</p>
<p>1. text_media_ratio<br />Pallete "Media Adjustments" should get an additional select box "text_media_ratio". Using this, an editor can select values like 1:1, 2:1, 1:2 for the aspectratio between text and media (affecting imageorient "in text" and "besides text").</p>
<p>2. media_aspectratio<br />Pallete "Media Adjustments" should get an additional select box "media_aspectratio". Using this, an editor can select values like 2:1, 4:3, 1:1, 3:4, 1:2 (like sys_file_reference crop variants) for the aspectratio of all assigned media elements (including youtube!). This way a content elements different media files (image, video, youtube) could be rendered with the same aspectratio easily.</p>
<p>For both, fluid_styled_content css should be extended to deliver the additional styles. For "media_aspectratio", youtube and vimeo iframe embeds should be scaled using "padding-bottom" hack to be repsonsive per default.</p>
<p>Plase contact me for a live demo.</p> TYPO3 Core - Task #89259 (Accepted): Create new icons and replace icons for "Page enabled in menu...http://forge.typo3.org/issues/892592019-09-25T09:39:35ZFrank Näglerfrank.naegler@typo3.org
<p>With <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Show "Page enabled in menus" in ContextMenu for pages (Closed)" href="http://forge.typo3.org/issues/85918">#85918</a> a new entry for "Page enabled in menus" was introduced in the context menus.<br />The currently used icons are not the best choice, but because of missing existing alternatives, we will merge it.</p>
<p>We need two new icons as a replacement for both menu items (s. screenshot)</p>
<p><img src="http://forge.typo3.org/attachments/download/34579/image.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #89158 (New): defaultHeaderType register no longer workshttp://forge.typo3.org/issues/891582019-09-12T15:20:42ZStig Nørgaard Færch
<p>It can be discussed if this is a bug or a feature.<br />The reason I have chosen to report it as a bug, is that before ext:fluid_styled_content this feature worked.</p>
<p>So...<br />Before ext:fluid_styled_content it was possible to set the register variable defaultHeaderType to decide which header type should be used when default was selected as type. Using the register for this, made it possible to choose the default header type, for each content area. <br />With ext:fluid_styled_content we only have a general default header type, which means all content areas have the same type.</p>
<p>I made a simple solution, where I in the Header.html partial use a TypoScript Object in fluid to fetch the register value (or the styles.content.defaultHeaderType constant as fallback)<br /><a class="external" href="https://gist.github.com/stigfaerch/23595d8eab8ccc9b1eeb81d09c5df410">https://gist.github.com/stigfaerch/23595d8eab8ccc9b1eeb81d09c5df410</a></p>
<p>I also tried another solution where I made a custom getRegister viewhelper. This also worked fine, but required a bit more code.</p> TYPO3 Core - Bug #89147 (Under Review): Media additionalConfig no-cookie attribute is added to vi...http://forge.typo3.org/issues/891472019-09-11T12:09:10ZJarvis H
<a name="Description"></a>
<h2 >Description:<a href="#Description" class="wiki-anchor">¶</a></h2>
<p>Typo3 version: 9.5.9</p>
<p>no-cookie attribute is added to <video> tags causing html validation errors</p>
<a name="How-to-reproduce"></a>
<h2 >How to reproduce:<a href="#How-to-reproduce" class="wiki-anchor">¶</a></h2>
<p>Add a media element using an mp4 video file.</p>
<a name="Suspected-cause"></a>
<h2 >Suspected cause:<a href="#Suspected-cause" class="wiki-anchor">¶</a></h2>
<p>The 'no-cookie' attribute is used for embedded youtube videos and is set via typoscript like this:</p>
<pre>
lib.contentElement.settings.media.additionalConfig.no-cookie = 1
</pre>
<p>which causes output like this:<br /><pre>
<video controls no-cookie>...</video>
</pre></p>
<p>In the <code>\TYPO3\CMS\Core\Resource\Rendering\VideoTagRenderer</code> class we see that all values found in <code>additionalConfig</code> are added as attributes in addition to all values from <code>additionalAttributes</code><br /><pre>
if (isset($options['additionalConfig']) && is_array($options['additionalConfig'])) {
foreach ($options['additionalConfig'] as $key => $value) {
if ((bool)$value) {
$attributes[] = htmlspecialchars($key);
}
}
}
</pre></p>
<a name="Possible-solution"></a>
<h2 >Possible solution:<a href="#Possible-solution" class="wiki-anchor">¶</a></h2>
<p>The above lines could be removed entirely, as <code>additionalAttributes</code> are already available.</p> TYPO3 Core - Feature #88442 (Needs Feedback): Allow iframe / video (youtube) javascript loading w...http://forge.typo3.org/issues/884422019-05-26T21:55:42ZChristian Hackl
<p>Allow loading a video through a kind of "defer" loading.<br />For example, the f:media viewhelper with an additional attribute defer = "true".</p>
<p>This makes it necessary to include additional JavaScript, as described here:<br /><a class="external" href="https://varvy.com/pagespeed/defer-videos.html">https://varvy.com/pagespeed/defer-videos.html</a></p>
<p>This could potentially improve the load time of the website.</p>