You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Trying the TYPO3 Headless API on a new TYPO3 version 13, including the new TYPO3 CMS Content Blocks extension, results in an error when requesting the JSON response.
To Reproduce
Steps to reproduce the behavior:
Perform a fresh TYPO3 13.2.1 installation.
Add a new content block with the following command:
Expected behavior
A JSON response with the newly added content based on the content blocks.
Screenshots
TYPO3 version and TYPO3 Headless version
TYPO3: 13.2.1
TYPO3 Headless API: 4.3.2
TYPO3 CMS Content Blocks: 0.8.0
Additional context
We have been using your headless plugin for a while and would love to have support for TYPO3 version 13 when requesting new content blocks.
The text was updated successfully, but these errors were encountered:
Hi @stattmal I have this on roadmap for new major version of our extension, but for I have to wait for final API in core to start adapting it for ext:headless
howto get headless running with TYPO3 13?
I set up a new composer based TYPO3 13.2.1 - downloaded the last master from headless and changed the dependencies to TYPO3 13.2. So I could install headless but the backend results in 500 Error. @tmotyl is there a release plan for headless for TYPO3 13.2 ?
Describe the bug
Trying the TYPO3 Headless API on a new TYPO3 version 13, including the new TYPO3 CMS Content Blocks extension, results in an error when requesting the JSON response.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A JSON response with the newly added content based on the content blocks.
Screenshots
TYPO3 version and TYPO3 Headless version
Additional context
We have been using your headless plugin for a while and would love to have support for TYPO3 version 13 when requesting new content blocks.
The text was updated successfully, but these errors were encountered: