Conversation
NamelessCoder
force-pushed
the
development
branch
from
October 28, 2017 21:19
1b71705 to
de70f1e
Compare
NamelessCoder
force-pushed
the
development
branch
from
January 11, 2018 01:00
379ca34 to
35d4b47
Compare
NamelessCoder
force-pushed
the
development
branch
from
July 10, 2018 13:21
88236e3 to
3d45411
Compare
NamelessCoder
force-pushed
the
development
branch
from
October 10, 2019 10:42
b115805 to
f64cde9
Compare
NamelessCoder
force-pushed
the
development
branch
from
June 16, 2022 12:24
703e5ab to
546c966
Compare
NamelessCoder
force-pushed
the
development
branch
3 times, most recently
from
January 23, 2025 16:44
4de2e5a to
319535d
Compare
NamelessCoder
force-pushed
the
development
branch
from
January 23, 2025 21:37
0077383 to
f3826ca
Compare
Selects backend-non-preview as context when no request is found, which happens in CLI context. Close: #2172
To my knowledge, this feature has never been used except in my own proof-of-concept environments. Given that it would need a rather excessive workaround to function on v13 it's probably best to simply remove the feature.
Rather than allowing TYPO3 to fail with a hard exception, we allow
Flux to operate in a limited-support mode where no TypoScript is
available. Although this isn't ideal, it's preferable to both alternatives:
1. Let TYPO3 throw an exception, making uncached operation completely
impossible.
2. Recreating the 8-class-dependency, 260-lines-of-code, non-API
TypoScript reading from PrepareTypoScriptFrontendRendering,
which is both final and readonly and completely impossible to extend.
"Fun" fact: TYPOv13 no longer has any short-API way of reading TypoScript
unless it is put into ServerRequest->attributes['frontend.typoscript'] -
and this simply does not happen in uncached (INT) contexts. Great.
There's no service, no utility, no API. The only way is to manually fetch
and parse every TS template from the root line and use the significantly
complex AST-based parsing mechanism.
…#2223) Adds a fallback handling which delivers template path setup based on Flux and provider extensions' paths when TypoScript can not be resolved. If TypoScript can be resolved, the path setup is read from plugin.tx_yourext (where "yourext" is your provider extension key) as usual.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @monosize
Is it possible to merge the current development branch from FluidTYPO3 into your fork? I would like to test it in a current Typo3v8.7 instance.