TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-03-30T08:04:09ZTYPO3 Forge
Redmine TYPO3 Core - Bug #93831 (Closed): Failing unit tests after update of symfony/mailerhttp://forge.typo3.org/issues/938312021-03-30T08:04:09ZRichard Haeserrichard@richardhaeser.com
<p>In symfony/mailer 5.2.6 and 4.4.21 symfony/mime is updated as well which has a change that will escape the name of the recipient of emails which cause our tests to fail.</p>
<p>See <a class="external" href="https://github.com/symfony/mime/compare/v5.2.5...v5.2.6">https://github.com/symfony/mime/compare/v5.2.5...v5.2.6</a></p> TYPO3 Core - Bug #93796 (Closed): Tree element doesn't hide overflowhttp://forge.typo3.org/issues/937962021-03-22T10:17:02ZRichard Haeserrichard@richardhaeser.com
<p>In current master, the select tree element is showing all nodes without an overflow which causes some nasty screens.</p>
<p><img src="http://forge.typo3.org/attachments/download/35964/Screenshot2021-03-22at10.59.39.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #93715 (Closed): Stabilize acceptance testshttp://forge.typo3.org/issues/937152021-03-12T08:39:19ZRichard Haeserrichard@richardhaeser.com
<p>The install tool login is directly checking if the text "The<br />Install Tool is locked" while this text comes from an<br />async request which might take some time to show.</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 #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 - Feature #90521 (Closed): AdminOnly widgetshttp://forge.typo3.org/issues/905212020-02-24T14:46:23ZRichard Haeserrichard@richardhaeser.com
<p>It should be possible to add widgets that should only be shown to admins to prevent information disclosure.</p> TYPO3 Core - Feature #90509 (Closed): Dashboard widget: pages without metadescriptionhttp://forge.typo3.org/issues/905092020-02-23T12:50:33ZRichard Haeserrichard@richardhaeser.com
<p>Add a widget showing the 5 most recently edited pages without a meta description.</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 #86526 (Closed): Wrong type is returned when no enhancers are configuredhttp://forge.typo3.org/issues/865262018-10-01T21:18:12ZRichard Haeserrichard@richardhaeser.com
<p>If you have a setup without page enhancers, the type parameter is not working anymore.</p>
<p>For example if you want to access the XML sitemap with ?type=1533906435 you will get the page-type 0.</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>