TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-04-21T07:03:17ZTYPO3 Forge
Redmine TYPO3 Core - Bug #93961 (Closed): Images not converting to webp in image viewhelpershttp://forge.typo3.org/issues/939612021-04-21T07:03:17ZRichard Haeserrichard@richardhaeser.com
<p>By default the images viewhelpers (f:image and f:uri.image) are not converted to webp if you specify webp as the target file extension.</p>
<pre><code class="html syntaxhl" data-language="html"><span class="nt"><f:image</span> <span class="na">src=</span><span class="s">"{fileLocation}"</span> <span class="na">fileExtension=</span><span class="s">"webp"</span> <span class="nt">/></span>
</code></pre>
<p>This will not do anything and just returning the original image. This is because webp is not seen as a "valid" image extension as defined by <code>$GLOBALS['TYPO3_CONF_VARS'][GFX][imagefile_ext]</code></p> TYPO3 Core - Bug #92830 (New): Preserve selected page after filter reset in pagetreehttp://forge.typo3.org/issues/928302020-11-13T08:13:16ZRichard Haeserrichard@richardhaeser.com
<p>If I choose to use the filter function in the page tree to find a page by page id, the page is shown in the page tree and all parent pages is shown. If I then click on the page in the page tree and disables the filter focus one of two things happens.</p>
<blockquote>
<p>Focus is preserved - if the page was a visible part of the page tree before filtering</p>
</blockquote>
<p>or</p>
<blockquote>
<p>Focus is lost - if the page was not visible in the page tree before filtering</p>
</blockquote>
<p>It would be great if focus is preserved..</p> TYPO3 Core - Bug #92191 (New): Page tree not showing in workspace renamed page title after movehttp://forge.typo3.org/issues/921912020-09-04T08:19:48ZRichard Haeserrichard@richardhaeser.com
<p>The page tree is not showing the correct name after moving a renamed record in a non-live workspace.</p>
<p>How to reproduce:<br />- Create page in live workspace<br />- Go to other workspace<br />- Rename a page<br />- You will see the new name in the page tree<br />- Move the renamed page to another parent<br />- You will now see the old name again</p> TYPO3 Core - Bug #91113 (Closed): Fix paths to AJAX urls of Dashboardhttp://forge.typo3.org/issues/911132020-04-18T14:47:40ZRichard Haeserrichard@richardhaeser.com
<p>/Build/Sources/TypeScript/dashboard/Resources/Public/TypeScript/Grid.ts<br />86:46 error ["dashboard_save_widget_positions"] is better written in dot notation dot-notation</p>
<p>/Build/Sources/TypeScript/dashboard/Resources/Public/TypeScript/WidgetContentCollector.ts<br />32:68 error ["dashboard_get_widget_content"] is better written in dot notation dot-notation</p> TYPO3 Core - Bug #91093 (Closed): Mark internal API in Dashboardhttp://forge.typo3.org/issues/910932020-04-17T16:29:51ZRichard Haeserrichard@richardhaeser.com
<p>Mark everything that is no public API as @internal</p> TYPO3 Core - Bug #91028 (Closed): Startup module option: First module in menu not working anymorehttp://forge.typo3.org/issues/910282020-04-14T15:20:49ZRichard Haeserrichard@richardhaeser.com
<p>The option "First module in menu" as the startup module in user settings is not working anymore. When choosing this option, you just got forwarded to the About modules module.</p> TYPO3 Core - Bug #90852 (Closed): Not all sizes of dashboard widget workhttp://forge.typo3.org/issues/908522020-03-27T12:37:41ZRichard Haeserrichard@richardhaeser.com
<p>You have the possibility to set the width and height of a widget. It seems that not all values from 1-6 in width and 1-4 in height work correctly. Maybe we need to add small, medium, large and xlarge for width and height instead, because h4 for height is not descriptive about the size.</p> TYPO3 Core - Bug #90687 (Closed): Backend search is corrupted due to missing fields in dashboardhttp://forge.typo3.org/issues/906872020-03-09T09:42:30ZRichard Haeserrichard@richardhaeser.com
<p>When you have installed the dashboard extension and try to search in the backend, you will receive an error Unknown column 'configuration' in 'where clause'.</p> TYPO3 Core - Bug #89848 (Under Review): Database Analyzer crashes with undefined enum fieldshttp://forge.typo3.org/issues/898482019-12-04T15:45:23ZRichard Haeserrichard@richardhaeser.com
<p>When you have a field in a column of type enum that is not specified in a sql file in the installation, the Database Analyzer in the install tool will crash and throws the error "array_map(): Argument #2 should be an array in /var/www/html/typo3/sysext/core/Classes/Database/Schema/Types/EnumType.php line 38". When you have the definition in a sql file of an extension, this won't cause an issue.</p>
<p>How to reproduce:<br />- Create a new field in tt_content with type enum and some values and a random name<br />- Go to Database Analyzer in install tool and run it</p> TYPO3 Core - Feature #88771 (New): Page Title Templateshttp://forge.typo3.org/issues/887712019-07-15T21:44:05ZRichard Haeserrichard@richardhaeser.com
<p>In stead of using TypoScript options `config.noPageTitle`, `config.pageTitleFirst`, `config.pageTitleSeparator` and `config.pageTitle` to define how your title tags will look like in frontend, we should work with a template for page titles.</p>
<p>This template is bound to a site language so you can be as flexible as possible.</p> TYPO3 Core - Feature #87826 (Accepted): Render og:locale and og:locale:alternate by defaulthttp://forge.typo3.org/issues/878262019-03-03T16:13:35ZRichard Haeserrichard@richardhaeser.com
<p>It would be really cool if the og:locale and og:locale:alternate are rendered by default. As you can see on <a class="external" href="http://ogp.me/">http://ogp.me/</a> the og:locale is giving information about in which locale the og tags are set. It is done in the format language_TERRITORY and the default is en_US.</p>
<p>See:<br />- <a class="external" href="http://ogp.me/">http://ogp.me/</a><br />- <a class="external" href="https://developers.facebook.com/docs/sharing/webmasters/">https://developers.facebook.com/docs/sharing/webmasters/</a></p> TYPO3 Core - Bug #87399 (New): Wrong default cropping when adding new cropVarianthttp://forge.typo3.org/issues/873992019-01-11T10:13:29ZRichard Haeserrichard@richardhaeser.com
<p>Situation:<br />You have for example a page and in the resources field you have configured 2 cropVariants already. The editors added content and have set their specific crops for all cropVariants.</p>
<p>After a while they decide they want a third cropVariant for the same field. When you add this configuration something strange happens. If you don't open the page properties in the backend, the frontend will correctly render the image with the new cropVariant and will be cropped from the center of the image. But when someone is checking the page properties and for example open the IRRE field for the already added images, the cropping of the new image is based on the first cropVariant instead of the original image. This only occurs with already connected images. When you add a new image, this is working as expected.</p>
<p>Tested and is "wrong" in v8 and v9.</p> TYPO3 Core - Bug #86421 (Closed): Preview of translated pages not working anymorehttp://forge.typo3.org/issues/864212018-09-28T14:07:59ZRichard Haeserrichard@richardhaeser.com
<p>When you want to open the page you are editing by using the eye-icon in the backend, it won't generate the correct link to the frontend anymore resulting in a page with the original language.</p>
<p>Seems to be after <a class="external" href="https://review.typo3.org/#/c/58149/">https://review.typo3.org/#/c/58149/</a></p>
<p>See screenshot for more information.</p> TYPO3 Core - Bug #86157 (Closed): Pages with no_index,follow shouldn't be in XML sitemaphttp://forge.typo3.org/issues/861572018-09-05T16:18:57ZRichard Haeserrichard@richardhaeser.com
<p>Only pages with no_index = 0 should be in XML sitemap. Pages with follow = 1 shouldn't show up.</p> TYPO3 Core - Feature #84805 (New): Detect change-state of field earlierhttp://forge.typo3.org/issues/848052018-04-20T10:05:06ZRichard Haeserrichard@richardhaeser.com
<p>With the new feature to only activate the save button when something changed, the change state should be checked earlier. Now if you are editing a field, but don't leave the field, the field is still in "not-changed" state and therefor, you don't have an activated save button.</p>