EXT:flux v10.0.x is not compatible with TYPO3 10.4 about flux HOT 4 OPEN

First issue is solved by 843526a.

Second issue will be investigated.

Third issue: can you provide additional information on how to reproduce? This is not occurring in my 10.4 setup.

Re: 10.4 support in General - Flux always tries to support ELTS as long as this is possible. Only in cases where it is 100% technically impossible to maintain this support will it be dropped.

from flux.

@NamelessCoder I can confirm the second issue in 10.4.37 version.
It seems cache is flushed anyway. However, our deployment just fails due to this issue.
Is this something that is not reproduceable in 11.5 version? If that's the case, we'll just omit the problem for now, as we're in the middle of an upgrade to 11.5.

from flux.

@instruccionesaldorso @bahammes The second issue may be fixable by ensuring that ENV TYPO3_PATH_ROOT is defined when you call your CLI scripts. The problem is that TYPO3 makes an assumption that the absolute site path is always a longer string than the relative path to the entry point script; and this isn't the case if TYPO3 cannot resolve this context information from apache/nginx context. Setting the ENV should circumvent that problem.

TYPO3v11 does not appear to have that issue since it does an additional resolving of the absolute script path when context is CLI. The assumption that the absolute base path is longer than the relative script path should therefore always be fulfilled.

from flux.

@NamelessCoder

Thank you for your feedback.

I have created a pull request for the command line problem (second issue).

Third issue: sorry, i cannot recreate the error in the page module any more. It seems to have been a problem in my TYPO3 installation.

from flux.