Skip to content
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

[FEATURE] add .dataprocessing capability #117

Merged
merged 1 commit into from
Jun 29, 2018

Conversation

pniederlag
Copy link
Contributor

ContentController will now execute any dataprocessors that are
configured via .setting.dataProcessing{} in TypoScript.

This Feature works exactly like the .dataProcessing property of
FLUIDTEMPLATE cObject.

@pniederlag
Copy link
Contributor Author

Another approach/idea might be to change the whole architecture of rendering of the ContentObjects to use a vanilla FLUIDTEMPLATE (instead of a USER cObject with ContentController) and inject the object via a dataprocessor.

To me that sounds logic and nice. Maybe you want to think about it.

Other than that, with this patch you can add any dataprocessors, for example the one provided in the themes extension.

ContentController will now execute any dataprocessors that are
configured via .setting.dataProcessing{} in TypoScript.

This Feature works exactly like the .dataProcessing property of
FLUIDTEMPLATE cObject.
@lochmueller lochmueller merged commit d29ed68 into lochmueller:master Jun 29, 2018
@lochmueller
Copy link
Owner

Nice idea... i merged the first step and will check the data processor handling next....

@pniederlag pniederlag deleted the feature/dataProcessing branch July 5, 2018 08:33
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.

None yet

2 participants