TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-11-13T08:13:16ZTYPO3 Forge
Redmine 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 - Task #90353 (Closed): Acceptance tests for dashboardhttp://forge.typo3.org/issues/903532020-02-11T11:39:42ZRichard Haeserrichard@richardhaeser.com
<p>As the dashboard is all about the UI, we should include acceptance tests to the extension.</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 #89502 (Closed): Add possibility to set site title in Site configurationhttp://forge.typo3.org/issues/895022019-10-24T16:20:24ZRichard Haeserrichard@richardhaeser.com
<p>It should be possible to set the title of the website in the Site configuration and not in the Template record as it is now. It should be possible to set it on a language base so you could have a localized site title.</p>
<p>This information will be used for generating the page title but later on for schema.org as well.</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 #88648 (Closed): Add possibility to set Twitter card type in backendhttp://forge.typo3.org/issues/886482019-06-27T22:35:26ZRichard Haeserrichard@richardhaeser.com
<p>It should be possible to set the type of Twitter card to show from the backend of TYPO3. Now by default type summary is shown.</p> TYPO3 Core - Task #88251 (Closed): Add functional tests for hreflang generatorhttp://forge.typo3.org/issues/882512019-04-30T21:15:49ZRichard Haeserrichard@richardhaeser.com
<p>We definitely need some functional tests for the hreflang generator</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 - Task #86419 (Closed): Add default cropping ratio for social share imageshttp://forge.typo3.org/issues/864192018-09-28T13:49:08ZRichard Haeserrichard@richardhaeser.com
<p>Facebook, LindedIn and Twitter do have the same aspect ratio for images of shared URL's. So it would be great if the default aspect ratio of the cropping tool is already providing the 1.91 / 1 ratio.</p> TYPO3 Core - Task #86061 (Closed): Add more automated tests to XML Sitemaphttp://forge.typo3.org/issues/860612018-08-31T13:59:30ZRichard Haeserrichard@richardhaeser.com
<p>The XML sitemap feature needs some more unit- and functional-tests.</p> TYPO3 Core - Feature #85679 (Closed): Add robot.txt functionalityhttp://forge.typo3.org/issues/856792018-07-29T22:02:06ZRichard Haeserrichard@richardhaeser.com
<p>TYPO3 should deliver an out-of-the-box robots.txt to prevent certain directories (like eg /typo3) to be indexed. Besides that, it should be possible by integrators to block certain parts of the website to be crawled to prevent using crawl budget while it is not needed to be in the index.</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> TYPO3 Core - Feature #84798 (Closed): Add some extra SEO fields to corehttp://forge.typo3.org/issues/847982018-04-19T16:11:02ZRichard Haeserrichard@richardhaeser.com
<p>Every websites benefits from a good SEO and therefor I think it is good to have some extra options in the core. At the moment there are several extensions adding properties to pages to make it possible to set some meta tags for Search Engine Optimization. By adding this to core, we help TYPO3 to provide more SEO options out of the box.</p>
The fields that should be added to TCA (without a "special" function)
<ul>
<li>SEO title => just an input field</li>
<li>robot instructions => two fields: on "Index this page" and "Follow this page". This should be the new toggle feature</li>
<li>OpenGraph-tags => 1 input field title, a textarea for description and a image field</li>
<li>Twitter-tags => 1 input field title, a textarea for description and a image field</li>
</ul>
<p>This should be done in page properties on a new tab called SEO. Also the description field (that is now on the Metadata tab) needs to be moved to the SEO tab.</p>
<p>If you have any question, please ask <a class="user active user-mention" href="http://forge.typo3.org/users/5127">@Richard Haeser</a></p>
<p>See <a class="external" href="https://decisions.typo3.org/t/include-some-basic-seo-options-to-core/289">https://decisions.typo3.org/t/include-some-basic-seo-options-to-core/289</a></p>