TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-02-20T21:37:54ZTYPO3 Forge
Redmine TYPO3 Core - Bug #90453 (Closed): Unused variable in dashboard controllerhttp://forge.typo3.org/issues/904532020-02-20T21:37:54ZRichard Haeserrichard@richardhaeser.com
<p>An unused parameter is passed to the Fluid template</p> TYPO3 Core - Feature #90354 (Closed): Status report widget for dashboardhttp://forge.typo3.org/issues/903542020-02-11T12:20:52ZRichard Haeserrichard@richardhaeser.com
<p>As a system administrator I would like to have the option to see if my current installation has any issues so I know if I have to check more specific things.</p>
<p>Status report just like it is in the About modules page. Showing a red widget with text when there are issues and a normal widget when everything is fine.</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 - Bug #88994 (Closed): Pages with set canonical field should be removed from sitemaphttp://forge.typo3.org/issues/889942019-08-21T22:19:29ZRichard Haeserrichard@richardhaeser.com
<p>Pages with a canonical set in the page properties, should not be shown in the XML sitemap.</p> TYPO3 Core - Bug #88970 (Closed): Remove Temporary Assets doesn't remove processed files from 3rd...http://forge.typo3.org/issues/889702019-08-16T16:14:20ZRichard Haeserrichard@richardhaeser.com
<p>Currently when you want to remove processed files in the install tool, it doesn't take the processed files on 3rd party FAL drivers into account. This is because the configuration of extensions is not parsed when checking the FAL-drivers if there are processed files.</p> TYPO3 Core - Bug #88064 (Closed): Error in upgrade wizards not visiblehttp://forge.typo3.org/issues/880642019-04-03T19:24:36ZRichard Haeserrichard@richardhaeser.com
<p>When you have an exception in your upgrade wizard, the screen containing the AJAX-error is very small and you need to scroll to see the trace.</p>
<p>See screenshot.</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 #85987 (Closed): Menus doesn't respect language settings and show non translated...http://forge.typo3.org/issues/859872018-08-27T09:29:58ZRichard Haeserrichard@richardhaeser.com
<p><strong>Scenario:</strong><br />- You have a 1-on-1 translated website<br />- TypoScript settings: config.sys_language_mode = strict and config.sys_language_overlay = hideNonTranslated<br />- Page in default language is enabled<br />- No translation</p>
<p><strong>Output:</strong><br />If you use a menu (HMENU or menu element doesn't matter) in the secondary language, the page from the default language is shown. So it is falling back on the default language.</p>
<p><strong>Expectation:</strong><br />Because you've set the mode to strict with no fallback, you expect this page to not show up in the menu.</p> TYPO3 Core - Bug #85720 (Closed): config.noPageTitle = 2 not working in masterhttp://forge.typo3.org/issues/857202018-08-01T23:41:54ZRichard Haeserrichard@richardhaeser.com
<p>If you sate a website title in your template record and you set config.noPageTitle = 2, you still get the website title as your title tag. This is because of missing type casting.</p> TYPO3 Core - Bug #85126 (Closed): Subproperties of TwitterCardMetaTagManager not acceptedhttp://forge.typo3.org/issues/851262018-05-30T22:47:25ZRichard Haeserrichard@richardhaeser.com
<p>You can't set subproperties of TwitterCardMetaTagManager properties like e.g. twitter:image:alt because in the TwitterCardMetaTagManager the definition of the subProperties is not done correctly.</p> TYPO3 Core - Bug #83479 (Closed): Minimal install of CMS9 causes warning in backendhttp://forge.typo3.org/issues/834792018-01-05T11:40:56ZRichard Haeserrichard@richardhaeser.com
<p>When you do not install any extensions, but just composer require typo3/minimal, you get a warning:<br /><pre>
PHP Warning: Invalid argument supplied for foreach() in /var/www/cms9/Web/typo3/sysext/backend/Classes/Domain/Repository/Module/BackendModuleRepository.php line 192
</pre></p>
<p>This is because the variable <pre>$GLOBALS['TBE_MODULES_EXT']</pre> might not be set yet.</p> TYPO3 Core - Bug #77979 (Closed): Setting [SYS][dbClientCompress] resolves in an errorhttp://forge.typo3.org/issues/779792016-09-17T13:43:56ZRichard Haeserrichard@richardhaeser.com
<p>In the install-tool it is possible to set <code>[SYS][dbClientCompress]</code> but after enabling it, and going back to the install-tool again, this option is migrated by the <code>SilentConfigurationUpgradeService</code>. This service sets <code>[DB][Connections][Default][driverOptions]</code> to <code>true</code>, but in <code>Doctrine\DBAL\Driver\Mysqli\Driver::connect()</code> the argument for driverOptions should be an array and not a boolean.</p> TYPO3 Core - Bug #73444 (Closed): newContentElementWizard override not working in PageLayoutViewhttp://forge.typo3.org/issues/734442016-02-15T20:03:54ZRichard Haeserrichard@richardhaeser.com
<p>There is a possibility to override the newContentElementWizard by setting <code>mod.newContentElementWizard.override</code>. This is not working for the PageLayoutView. In this module the link is hard-coded to <code>BackendUtility::getModuleUrl('new_content_element', $urlParameters)</code></p>
<p>As a developer I would like to override this link as well so I can implement my own wizard for adding new content elements.</p> TYPO3 Core - Bug #25117 (Closed): Error on upgrading workspaces 4.4.6 => 4.5.0http://forge.typo3.org/issues/251172011-02-21T12:30:22ZRichard Haeserrichard@richardhaeser.com
<p>I just upgraded an environment from 4.4.6 to 4.5.0. When trying to update the workspaces in the install-tool, I get an error:</p>
<p>Fatal error: Call to a member function includeLLFile() on a non-object in [.....]/typo3_src-4.5.0/typo3/sysext/em/classes/install/class.tx_em_install.php on line 72</p>
<p>(issue imported from #M17688)</p> TYPO3 Core - Bug #24458 (Closed): Installing extension: Dependency Window has a Back Button which...http://forge.typo3.org/issues/244582011-01-03T13:50:12ZRichard Haeserrichard@richardhaeser.com
<p>If you try to import an extension that depends on an extension that's not installed yet, you have the "import now" option.<br />After opening the popup and installing the needed extension, you have the link to close the popup. This link is working. But in the top left corner of that window there is the button "Back". This one is not working. If you click that option, the popup will not close, but it shows the content of the extension manager in the popup.</p>
<p>(issue imported from #M16897)</p>