Skip to content

Basic TYPO3 v13 support#589

Open
RSCW-Duisburg wants to merge 2 commits intohoogi91:developfrom
RSCW-Duisburg:develop
Open

Basic TYPO3 v13 support#589
RSCW-Duisburg wants to merge 2 commits intohoogi91:developfrom
RSCW-Duisburg:develop

Conversation

@RSCW-Duisburg
Copy link
Copy Markdown

Q A
Bug fix? yes/no
New feature? yes/no
BC breaks? no
Deprecations? yes/no
Tests pass? yes/no
Fixed tickets #...

Copy link
Copy Markdown
Contributor

@saitho saitho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just roughly reviewed the changes without testing them.

{
// Get the Fluid namespaces from the global configuration
$namespaces = $GLOBALS['TYPO3_CONF_VARS']['SYS']['fluid']['namespaces'] ?? [];
$resolver = (new Typo3Version())->getMajorVersion() > 11
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dadurch geht mindestens die Kompatibilität mit TYPO3 11 verloren, welche laut Dependencies noch gewährleistet wird.

$view->getRenderingContext()->getTemplatePaths()->setTemplateSource($template);

// Set the ViewHelperResolver from TYPO3Fluid
$resolver = new ViewHelperResolver();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Können wir die Instanz via GeneralUtility::makeInstance initialisieren? Ebenfalls oben bei TemplateVIew

"typo3/cms-fluid": "^11.5 || ^12.4",
"typo3/cms-fluid-styled-content": "^11.5 || ^12.4",
"typo3/cms-frontend": "^11.5 || ^12.4"
"typo3/cms-backend": "^11.5 || ^12.4 || ^13",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependencies zu prüfen – je nach Änderungen ((Nicht)Verwendung ObjectManager o. RequireJS?) könnte Support für ältere Versionen wegfallen.

@sorenmalling
Copy link
Copy Markdown

@saitho @RSCW-Duisburg Is any of you doing active work on updating this PR?

@saitho
Copy link
Copy Markdown
Contributor

saitho commented Nov 20, 2025

Nope :)

@RSCW-Duisburg
Copy link
Copy Markdown
Author

not planed

@sorenmalling
Copy link
Copy Markdown

@hoogi91 Anything on your schedule to merge and release?

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.

4 participants