TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-10-28T10:45:03ZTYPO3 Forge
Redmine TYPO3 Core - Bug #95811 (Accepted): File Meta Data translations not displayed in backendhttp://forge.typo3.org/issues/958112021-10-28T10:45:03ZAnonymous
<p><strong>Way to reproduce:</strong></p>
<p>- Create a new content element containing a FAL relation field.<br />- add a file<br />- edit the file and add some meta data like title, alt and description<br />- translate the file (meta data) and fill up translation content for those fields (this two steps could also be done before within the File module)<br />- translate the content element<br />- now the file meta data of the translated content shows default language content in sys_file_metadata fields</p>
<p><strong>Some Backgrounds:</strong><br />- this was testet with a plain installation and official introduction package installed<br />- TYPO3 10.4.21 shows the correct translated field contents<br />- TYPO3 11.5.1 shows field content of default language in translations</p>
<p><strong><br />Maybe Related:</strong><br />- In a client project (TYPO3 10.4.21) I have old content elements using flexforms - there the behaviour is also, that default language is shown in translations - but not in TCA field - there its correct translated.</p> TYPO3 Core - Task #91505 (Accepted): Disallow using fileadmin and co. for the storage of e.g. .ph...http://forge.typo3.org/issues/915052020-05-27T11:16:47ZSimon Gillitypo3@gilbertsoft.org
<p>Since years it's suggested to use sitepackages or normal extension for e.g. .php files and co. and not longer use the fileadmin folder for this type of files.</p>
<p>The default .htaccess (and webconf) should include a directive to block the access to this files by default.</p>
<p>See also discussion at Slack:<br /><a class="external" href="https://typo3.slack.com/archives/C0K5MU94J/p1590567620046600">https://typo3.slack.com/archives/C0K5MU94J/p1590567620046600</a><br /><a class="external" href="https://typo3.slack.com/archives/C0K5MU94J/p1590569590049700">https://typo3.slack.com/archives/C0K5MU94J/p1590569590049700</a></p> TYPO3 Core - Bug #91220 (Accepted): ExtensionManager dependency calculation does not take extensi...http://forge.typo3.org/issues/912202020-04-28T11:40:12ZBenjamin Franzkeben@bnf.dev
<p>When one extension depends on two extensions where both extensions depend on a third one, but with a different set of matching versions, then ExtensionManager is unable to find the common dependency version that is allowed by both extensions, because it decided for a very too early.</p>
<p>Sound very complicated in written words, therefore an example:</p>
<p>Two custom extensions: "master" and "other_ext"</p>
<p>EXT:master (allowing powermail v6-v8 and depending on `other_ext`)</p>
<pre><code>'constraints' => array(<br /> 'depends' => array(<br /> 'typo3' => '9.5.0-9.5.99',<br /> 'powermail' => '6.0.0-8.99.99',<br /> 'other_ext' => '*',<br /> ),<br /> ),<br />EXT:other_ext (allowing only powermail v6)</code></pre>
<pre><code>'constraints' => array(<br /> 'depends' => array(<br /> 'typo3' => '9.5.0-9.5.99',<br /> 'powermail' => '6.0.0-6.99.99',<br /> ),<br /> ),</code></pre>
<p>When installing "master" on 9.5 the error "powermail was requested to be downloaded in different versions (6.2.0 and 7.4.0)." will be thrown.</p>
<p>That is because the latest version of powermail is used when checking dependencies for "EXT:master" – the compatible v6 should/could be taken into account as both extensions are marked to be compatible with it and v6 itself is marked to be v9.5 compatible.</p>
<p>Note: This is <strong>not</strong> a bug that was introduced with <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/64308/">https://review.typo3.org/c/Packages/TYPO3.CMS/+/64308/</a> (that patch is fine) – it's just an additional and more complex case.</p>
<p><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Special dependencies are not checked during install of dependencies (Closed)" href="http://forge.typo3.org/issues/91179">#91179</a> is therefore related, but not the source of this bug.</p>