Skip to content

Conversation

@linawolf
Copy link
Contributor

No description provided.

Co-authored-by: Mathias Brodala <mbrodala@pagemachine.de>
@mbrodala
Copy link
Contributor

Strictly speaking we have quite a few versionadded blocks throughout the docs. Do you think it would make sense to mention this everywhere? It should be compact though (e.g. a link) so it won't take too much effort for future changes.

@linawolf
Copy link
Contributor Author

Might make sense. But it might also make sense to always mention with which TYPO3 version this feature was first shipped

So when I am using for example TYPO3 13 I dont have to double check

@s2b
Copy link
Contributor

s2b commented Oct 15, 2025

From a TYPO3 point of view, things are pretty simple: If you use the latest patch-level version, you get the following Fluid versions:

  • TYPO3 v14: will be latest Fluid 5 release
  • TYPO3 v13: latest Fluid 4 release
  • TYPO3 v12: latest Fluid 2 release
  • TYPO3 v11: Fluid 2.7.2

So the exact Fluid version should be irrelevant for TYPO3 users, only the major version matters. If you use Fluid standalone, you should be able to determine your Fluid version, because you already used composer to set it up.

@s2b
Copy link
Contributor

s2b commented Nov 5, 2025

@linawolf Should we maybe add a page/section to the TYPO3 docs listing the TYPO3+Fluid version pairings and then link to that page from all relevant versionadded sections?

@linawolf
Copy link
Contributor Author

linawolf commented Nov 5, 2025

sounds like a good idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants