http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-01-24T20:06:45ZTYPO3 ForgeTYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3557192018-01-24T20:06:45ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Category</strong> set to <i>Backend API</i></li></ul> TYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3635092018-04-15T11:19:32ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>Solution was in v8 to remove the necessity for setBackPath - this is now resolved, as you just use assets with EXT: prefix or relative to PATH_site.</p>
<p>Is this OK for you?</p> TYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3635182018-04-15T12:01:21ZThomas Mayer
<ul></ul><p>Thank you for reporting back. Is this this change: <a class="external" href="https://docs.typo3.org/typo3cms/extensions/core/Changelog/8.0/Breaking-73763-RemovedBackPathFromPageRenderer.html">https://docs.typo3.org/typo3cms/extensions/core/Changelog/8.0/Breaking-73763-RemovedBackPathFromPageRenderer.html</a> ?</p>
<p>To my knowledge, metaseo still runs with v8 LTS whereas the 7.6 related workaround is still applied in the code. As long as setting the backPath does not have any effect any more since 8.0, that would render this issue obsolete for v8 LTS and later versions.</p>
<p>The final test would be to remove our workaround (<a class="external" href="https://github.com/mblaschke/TYPO3-metaseo/issues/150">https://github.com/mblaschke/TYPO3-metaseo/issues/150</a> <a class="external" href="https://github.com/webdevops/TYPO3-metaseo/commit/247ef20449270874abd6670bb009324c0afabacf">https://github.com/webdevops/TYPO3-metaseo/commit/247ef20449270874abd6670bb009324c0afabacf</a>) for v8 LTS, as well as setting the backPath itself. I'll report back how that plays out (via <a class="external" href="https://github.com/webdevops/TYPO3-metaseo/issues/521">https://github.com/webdevops/TYPO3-metaseo/issues/521</a>).</p> TYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3682392018-07-03T00:18:34ZRiccardo De Contardierredeco@gmail.com
<ul></ul><p>Is it ok to close this issue or is there still work that should be done? Thank you.</p> TYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3682422018-07-03T01:45:40ZThomas Mayer
<ul></ul><p>In theory, this issue is only relevant for 7 LTS. According to my earlier investigation (<a class="external" href="https://github.com/webdevops/TYPO3-metaseo/issues/521">https://github.com/webdevops/TYPO3-metaseo/issues/521</a>), my workaround for 7 LTS should not have any effect in 8 LTS any more and can safely be removed (when testing against 8 LTS).</p>
<p>Respectively, when this is not fixed for 7 LTS any more (and I assume, it's not), this issue can be closed.</p> TYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3682482018-07-03T09:11:33ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Closed</i></li></ul><p>I close this one for now;</p>
<p>If you think that this is the wrong decision, please reopen or ping me. Thank you.</p> TYPO3 Core - Bug #69319: Instanciation of TSFE sets backPath of PageRenderer to frontend context. Backend assets 404.http://forge.typo3.org/issues/69319?journal_id=3682502018-07-03T09:21:11ZBenni Mackbenni@typo3.org
<ul></ul><p>Yes, won't fix that one in TYPO3 v7, as we conceptually fixed that for v8.</p>