Bug #88184

Backend JS and CSS is not compressed with Viewhelper f:be.container and TYPO3 in subdirectory

Added by Tim Horstmann about 1 month ago. Updated 11 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2019-04-23
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I have an extension with a backend module and some js and css for backend, that is added with viewhelper f:be.container like

<f:be.container
    includeCssFiles="{0: '{f:uri.resource(path:\'Styles/styles.css\')}'}" 
    includeJsFiles="{
        0: '{f:uri.resource(path:\'JavaScript/search.js\')}',
        1: '{f:uri.resource(path:\'JavaScript/import.js\')}'
    }" 
>

This works fine, if TYPO3 is installed in the root directory of domain. It also works if backend js does not get compressed, which is most likely the case for development environment with BE/debug = 1.

If both conditions are not met, the files are not included.

I have TYPO3 installed under somedomain.tld/subdir, BE/debug = 0 and tried with and without a site configuration. The error happens somewhere between class PageRenderer and RessourceCompressor. In class ResourceCompressor the filepaths are not determined correctly and the file can not be read. I am not sure, where to fix this issue. Perhaps, this not only affects this certain viewhelper and the scope of this bug is bigger.

In my case, I tested with extension ig_ldap_sso_auth, but this should not be relevant for the bug.
My workaround is to set BE/debug = 1.

History

#1 Updated by Christian Hackl about 1 month ago

perhaps in connection with https://forge.typo3.org/issues/88150

#2 Updated by Frank Naegler 11 days ago

  • Category changed from Backend JavaScript to Backend API

Also available in: Atom PDF