TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-06-26T10:19:09ZTYPO3 Forge
Redmine TYPO3 Core - Bug #88631 (Accepted): Page type parameter is ignored in POST requests/parametershttp://forge.typo3.org/issues/886312019-06-26T10:19:09ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>Since TYPO3 9 the page type parameter is ignored when set in POST parameters (for example from a form field). If it's set in GET parameters (query string) everything is fine. This is because the PageArguments object is instantiated at several points with only the type parameter from the query params (for example in \TYPO3\CMS\Frontend\Middleware\PageResolver) not respecting the POST parameters. On the other hand the TypoScriptFrontendController is instantiated in \TYPO3\CMS\Frontend\Middleware\TypoScriptFrontendInitialization with GeneralUtility::_GP('type') handling both POST and GET parameters. This is inconsistent behaviour and should be fixed as soon as possible. Or is this intended and not a bug?</p> TYPO3 Core - Bug #88519 (Closed): Wrong image reference handling during flexform translation in ...http://forge.typo3.org/issues/885192019-06-07T13:58:38ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>References in flexforms having type=inline are not processed correctly<br />during translations in workspaces as the remapping is not done. It's only done for group and select fields inside the flexform.</p>
<p>When a content element is translated in a draft workspace containing FAL references in a flexform inline field the references of the translation gets moved to the content element with default language upon publishing. As long as the content elements are in the draft workspace everything is fine. <br />This is due to the fact that the file reference of the new place holder version (t3ver_state = -1) of the translated content element is pointing to the content element (uid_foreign) in the default language. The value of uid_foreign for the draft version reference is correct.</p>
<p>Steps to reproduce:<br />1. Add an extension with a plugin and a flexform for that plugin. <br />2. Add an inline image field in flexform like the following:<br /><pre>
<image>
<TCEforms>
<label>Add image</label>
<config>
<type>inline</type>
<appearance type="array">
<createNewRelationLinkTitle>Image</createNewRelationLinkTitle>
<enabledControls type="array">
<delete>1</delete>
<dragdrop>1</dragdrop>
<hide>1</hide>
<info>1</info>
<localize>1</localize>
</enabledControls>
<headerThumbnail type="array">
<field>uid_local</field>
<height>45c</height>
<width>45</width>
</headerThumbnail>
<useSortable>1</useSortable>
</appearance>
<behaviour type="array">
<localizationMode>select</localizationMode>
<localizeChildrenAtParentLocalization>1</localizeChildrenAtParentLocalization>
</behaviour>
<filter type="array">
</filter>
<foreign_field>uid_foreign</foreign_field>
<foreign_label>uid_local</foreign_label>
<foreign_match_fields type="array">
<fieldname>galleryImage</fieldname>
</foreign_match_fields>
<foreign_selector>uid_local</foreign_selector>
<foreign_selector_fieldTcaOverride type="array">
<config type="array">
<appearance type="array">
<elementBrowserAllowed>jpg,jpeg,png,gif,svg</elementBrowserAllowed>
<elementBrowserType>file</elementBrowserType>
</appearance>
</config>
</foreign_selector_fieldTcaOverride>
<foreign_sortby>sorting_foreign</foreign_sortby>
<foreign_table>sys_file_reference</foreign_table>
<foreign_table_field>tablenames</foreign_table_field>
<foreign_types type="array">
<numIndex index="0" type="array">
<showitem>--palette--;LLL:EXT:lang/Resources/Private/Language/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette</showitem>
</numIndex>
<numIndex index="1" type="array">
<showitem>--palette--;LLL:EXT:lang/Resources/Private/Language/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette</showitem>
</numIndex>
<numIndex index="2" type="array">
<showitem>--palette--;LLL:EXT:lang/Resources/Private/Language/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette</showitem>
</numIndex>
<numIndex index="3" type="array">
<showitem>--palette--;LLL:EXT:lang/Resources/Private/Language/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette</showitem>
</numIndex>
<numIndex index="4" type="array">
<showitem>--palette--;LLL:EXT:lang/Resources/Private/Language/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette</showitem>
</numIndex>
<numIndex index="5" type="array">
<showitem>--palette--;LLL:EXT:lang/Resources/Private/Language/locallang_tca.xlf:sys_file_reference.imageoverlayPalette;imageoverlayPalette,--palette--;;filePalette</showitem>
</numIndex>
</foreign_types>
<maxitems>1</maxitems>
<minitems>0</minitems>
</config>
</TCEforms>
</image>
</pre><br />3. Set up workspaces to have at least a draft workspace.<br />4. Switch to non-live workspace and create a plugin record for the default language.<br />5. Add an image reference.<br />6. Translate the record. At this point everything looks okay. But in the database the new version placeholder (t3ver_state = -1) of the translated file reference (sys_file_reference) points to the plugin record in the default language not to the record in the translated language. The file reference record for the draft workspace version points to the correct record.<br />7. Publish changes to live. The file references of the translated plugin record get moved to the default plugin record leaving the translation without references and the default record with 2 references.</p>
<p>I hope I explained it well enough to understand the problem.</p>
<p>Can also be reproduced with the gridelements extension. If there is a container with inline FAL references this happens, too.</p>
<p>P.S. I found the solution through the issue <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Copied flexform element is missing FAL images (Closed)" href="http://forge.typo3.org/issues/59664">#59664</a> as there seemed to be a similar problem.</p> TYPO3 Core - Bug #81520 (Closed): form validation in backend not working onloadhttp://forge.typo3.org/issues/815202017-06-08T15:57:14ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>When a form is loaded (e.g. when adding a new page) required fields are not evaluated on load of the form. As soon as I change a field all required fields are evaluated and marked when empty. <br />This is a problem as the form can be saved successfully as long as no inputs are done even though fields are required.</p>
<p>I experience this bug since TYPO3 7.6.17. In TYPO3 7.6.16 everything works fine.</p>
<p>I think this commit is the cause for this bug: <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/commit/e6b3d3c3ddfbff752426e8002914b14ef2e5893c">https://github.com/TYPO3/TYPO3.CMS/commit/e6b3d3c3ddfbff752426e8002914b14ef2e5893c</a></p>
<p>related issue: <a class="external" href="https://forge.typo3.org/issues/80481">https://forge.typo3.org/issues/80481</a></p> TYPO3 Core - Bug #80327 (Closed): "L" parameter not excluded in TYPO3\CMS\Frontend\ContentObject\...http://forge.typo3.org/issues/803272017-03-17T14:26:14ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>Let's say someone calls a page with a bad "L" parameter like index.php?id=1&L=bad-value. With the TypoScript config.linkVars = L(0-2) this value is not valid and get's not added to links created on that page. Except there is a typolink with addQueryString set and not addQueryString.exclude = L</p>
<p>When config.prefixLocalAnchors = all is set the method TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::getUrlToCurrentLocation is called. In this method there is no way to add the "L" parameter to the excluded parameters (addQueryString.exclude) if it has a invalid value. This is because the "L" parameter is invalid due to config.linkVars = L(0-2). Therefore $GLOBALS['TSFE']->linkVars is empty which leads to not having the "L" parameter excluded although it has to. So when the current URL get's a bad "L" parameter added, a link is generated with a bad "L" parameter.</p>
<p>This might open security holes and can lead to conflicts with extensions like realurl.</p>
<p>Additionally I wonder if it's necessary to not exclude the L parameter for every addQueryString after all. Users should have configured config.linkVars correctly for multi language sites. With that TYPO3 takes care of adding the "L" parameter itself when valid.</p> TYPO3 Core - Bug #78021 (Closed): cHashIncludePageId and links to the domain with parameters failhttp://forge.typo3.org/issues/780212016-09-21T11:11:29ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>If the new option cHashIncludePageId is set to true links to the domain/root page will fail if parameters and a cHash is appended. This is because the id Parameter is missing. I think that's normal for links to the root page/domain so this needs to be fixed.</p>
<p>Error message: ID parameter<br />needs to be passed for the cHash calculation! As a temporary not recommended<br />workaround, you can set $GLOBALS['TYPO3_CONF_VARS']['FE']['cHashIncludePageId'] to<br />false to avoid this error.</p> TYPO3 Core - Bug #76628 (Closed): Linkvalidator checks hard for deleted fieldhttp://forge.typo3.org/issues/766282016-06-14T14:33:55ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>The linkvalidator checks in LinkAnalyzer::getLinkStatistics hard for the deleted field. But maybe the table to be checked has no deleted field or it's named differenty. That's why the configured field from the TCA should be checked. (['ctrl']['delete'])</p> TYPO3 Core - Bug #76441 (Closed): Update storage index (scheduler) and file mountshttp://forge.typo3.org/issues/764412016-06-03T08:40:47ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>If the CLI BE user has file mounts in a storage, the Update storage index (scheduler) task will only index files in the first file mount. This is because of the call $this->storage->getRootLevelFolder() in TYPO3\CMS\Core\Resource\Index\Indexer::processChangesInStorages()</p>
<p>Maybe the file mounts shouldn't be respected at that point but later when each file is checked. This way changed files would be detected in all file mounts.</p>
<p>I added the root folder (/) as a file mount as workaround.</p> TYPO3 Core - Feature #65119 (Rejected): syslog floodhttp://forge.typo3.org/issues/651192015-02-17T10:02:42ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<p>When a database error or something similar occurs, the syslog is possibly flooded. If you send fatal errors for example via mail then this could easily overfill the mailbox given you have a website with several cronjobs running and many visitors per minute.</p>
<p>I thing there should be some kind of locking so syslog logs the same error only once a minute (could be configurable) or so.</p>
<p>If you consider this feature also as valuable, then we would be glad to contribute a solution.</p>