-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rendering is empty when PLUGIN_TYPE_CONTENT_ELEMENT is used #19
Comments
From reading the code, it creates a structure with Can you please verify if the content element works at all? And can you please paste the generated Ajax URI here? |
For both plugin types, the FE content elements works and displays its content. The plugin needs to be set in the content element in different ways, though: PLUGIN_TYPE_CONTENT_ELEMENT:
PLUGIN_TYPE_PLUGIN:
(So the URLs are the same in both cases.) |
Was a bit tougher to fix than expected. Should work now however. Thanks for the report! |
Thanks! ❤️ |
This issue is a spin-off from PR #18.
When registering a plugin using \TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin with $pluginType = \TYPO3\CMS\Extbase\Utility\ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT (instead of the default type PLUGIN_TYPE_PLUGIN), the output is completely empty. (The corresponding action also never gets called.)
We most probably will be able to test this using the ajax_example extension (although I haven't checked yet).
From my debugging, I found out that PLUGIN_TYPE_PLUGIN creates a TS setup structure like tt_content.list.20.pluginname = USER while PLUGIN_TYPE_CONTENT_ELEMENT does not create it, but the typoscript_rendering extension relies on this when rendering the content element.
The text was updated successfully, but these errors were encountered: