TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-05T06:09:42ZTYPO3 Forge
Redmine TYPO3 Core - Feature #103043 (Resolved): Modernize tree rendering and implement RTL and dark modehttp://forge.typo3.org/issues/1030432024-02-05T06:09:42ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #93773 (Closed): Move SVG Tree to Lit Elementshttp://forge.typo3.org/issues/937732021-03-18T13:41:48ZBenjamin Franzkeben@bnf.dev
<p>The entire SVG Tree should be a HTML element, to allow further<br />reduction of d3 usage in favor of native HTML5 APIs.</p> TYPO3 Core - Bug #93522 (Closed): Too much padding when Installtool is opened in Backendhttp://forge.typo3.org/issues/935222021-02-16T13:49:41ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #93489 (Closed): Use position sticky for docheaderhttp://forge.typo3.org/issues/934892021-02-11T12:53:15ZBenjamin Franzkeben@bnf.dev
<p>Avoid javascript based offset/height calculations.<br />position sticky can do that in all supported browsers for us.</p> TYPO3 Core - Task #93476 (Closed): Improve PageTree search input alignmenthttp://forge.typo3.org/issues/934762021-02-09T19:47:44ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #93473 (Closed): Add a Custom component for Backend Icons inside Shadow DOMhttp://forge.typo3.org/issues/934732021-02-09T13:08:17ZBenjamin Franzkeben@bnf.dev
<p>For components that want to use LitElement with shadow DOM, icons need to be renderable (e.g. as SVGs) inside shadow dom.</p>
<p>A <code><typo3-backend-icon identifier="blub"></code> element would be ideal.</p> TYPO3 Core - Task #93465 (Closed): Remove unused wizard-backendlayout icon definitionhttp://forge.typo3.org/issues/934652021-02-08T14:08:50ZBenjamin Franzkeben@bnf.dev
<p>This wizard-backendlayout icon has been added in <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Remove old and unused images from core (Closed)" href="http://forge.typo3.org/issues/72853">#72853</a><br />as icon for the backend layout wizard, but was later<br />forgotten to be removed when the backend layout wizard was<br />rewritten into an own renderType in TYPO3 v8 (<a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: inline backend layout wizard (Closed)" href="http://forge.typo3.org/issues/75497">#75497</a>),<br />where the icon was no longer used.</p> TYPO3 Core - Task #93464 (Closed): Drop unneeded renderElement from lit-helperhttp://forge.typo3.org/issues/934642021-02-08T13:40:32ZBenjamin Franzkeben@bnf.dev
<p>In <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Clean up Drag&Drop Handling in PageTree (Closed)" href="http://forge.typo3.org/issues/93446">#93446</a> lit-helper.renderElement() was introduced as a helper for patchset 2 – <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/67650/2">https://review.typo3.org/c/Packages/TYPO3.CMS/+/67650/2</a> – but wasn't used in the final patchset.</p>
<p>A renderNodes() element would helper here – returning a NodeList.</p> TYPO3 Core - Task #93442 (Closed): Inject PackageManager and cache into ExpressionLanguage/Provid...http://forge.typo3.org/issues/934422021-02-05T09:30:20ZBenjamin Franzkeben@bnf.dev
<p>..instead of looking these up via global state by using <code>GeneralUtility::makeInstance</code>.</p> TYPO3 Core - Task #93440 (Closed): SiteConfiguration should inject it's cache instancehttp://forge.typo3.org/issues/934402021-02-05T07:01:15ZBenjamin Franzkeben@bnf.dev
<p>..instead of lookup in up via <code>GeneralUtility::makeInstance</code>.</p> TYPO3 Core - Task #92722 (Closed): Refactor TER RemoteRegistry to avoid container usage as it is ...http://forge.typo3.org/issues/927222020-10-27T20:02:20ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #91534 (Closed): Remove deprecated Commands.php loadinghttp://forge.typo3.org/issues/915342020-05-29T20:58:44ZBenjamin Franzkeben@bnf.dev
<p>In favor of DI tag based configuration as introduced by <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/61630">https://review.typo3.org/c/Packages/TYPO3.CMS/+/61630</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> TYPO3 Core - Bug #91074 (Rejected): typo3conf/ folder is not created when using a custom app-dir ...http://forge.typo3.org/issues/910742020-04-17T01:15:10ZBenjamin Franzkeben@bnf.dev
<p>In composer mode in composer.json:</p>
<pre><code>"extra": {<br /> "typo3/cms": {<br /> "app-dir": "custom",<br /> "web-dir": "public" <br /> }<br /> },</code></pre>
<p>In this case Environment::$projectPath would be /path/to/root/custom and Environment::$publicPath would be /path/to/root/public.</p>
<p>The typo3conf folder is then generated in /path/to/root/custom/typo3conf instead of /path/to/root/public/typo3conf.</p>
<p>This is actually by accident, because "custom" and "public" have the same length.<br />Reason is the code in <a class="external" href="https://git.typo3.org/Packages/TYPO3.CMS.git/blob/9fb677f6f3b3a1cd584b9ef183b35da771d3e25d:/typo3/sysext/install/Classes/FolderStructure/DefaultFactory.php#l134">https://git.typo3.org/Packages/TYPO3.CMS.git/blob/9fb677f6f3b3a1cd584b9ef183b35da771d3e25d:/typo3/sysext/install/Classes/FolderStructure/DefaultFactory.php#l134</a><br /><pre>
$publicPath = substr(Environment::getPublicPath(), strlen(Environment::getProjectPath())+1);
</pre><br />which tries to substract the project path from the public path, while assuming that project path is an ancestor, which results in a public path <code>""</code> to be calculate.<br />The result should rather be <code>"../public"</code>.</p>
<p>We should rather generate a relative path and adapt the FolderStructur Factory to handle relative paths, include partent dots ("..").</p> TYPO3 Core - Bug #86492 (Closed): stdWrap on config.additionalHeaders is broken for (fully) cache...http://forge.typo3.org/issues/864922018-10-01T09:56:28ZBenjamin Franzkeben@bnf.dev
<p>The feature to use stdWrap for additionalHeaders was introduced in v9 development cycle: <a class="external" href="https://review.typo3.org/c/50142/">https://review.typo3.org/c/50142/</a><br />It seems this is broken since the initial commit (and is still in master).</p>
<p>Suppose using the following TypoScript (as suggested in the documentation):</p>
<pre>
config.additionalHeaders {
10 {
# The header string
header = X-TYPO3-foo:
header.dataWrap = |{page:uid}
}
}
</pre>
<p>Both the original commit 2124bba49f68f5c35705c5c499abe6a0ee95a6cf and current master result in an Exception for a page that is read from cache because <code>TypoScriptFrontendController->cObj</code> is not initialized:</p>
<pre>
? $this->cObj->stdWrap(trim($header), $options['header.'])
Oops, an error occurred!
Call to a member function stdWrap() on string.
</pre>
<p>cObj is initialized in TSFE::newCObj, which is called by <code>TSFE::preparePageContentGeneration</code>, which itself is only called if the page is uncached or rendered initially (for good reasons).</p>
<p>I'm not sure whether we should revert this feature, instead of fixing this and implcitly allowing uncached stuff to be executed (through stdWrap) for a fully cached page. Things like these may be better handled by middlewares.</p>