[Neos] Questions on plugin development

Aske Ertmann aske at moc.net
Tue Sep 10 09:14:22 CEST 2013

Hello again

> In my NodeTypes.yaml I define TYPO3.Neos:Plugin as superTypes. What is the difference betwenn those syntaxes:
>  superTypes: ['TYPO3.Neos:Plugin']
> and
>  superTypes:
>    - 'TYPO3.Neos.NodeTypes:Headline'
> ?
There's none, it's just two different ways of defining arrays in Yaml.

> Can I somehow use both superTypes Headline and Plugin to create a Plugin that has a content-editable headline?
I'm not sure if you can do this, because the headline uses Template for rendering in TypoScript where Plugin uses PluginImplementation. However you can as you say use the two super types to get the properties in your node type and then use the PluginImplementation for rendering and then add use the node property inside your plugin. I could however imagine this won't work, but unfortunately there's no way of wrapping your plugin currently.

> The only plugin property I defined was the Album ID (album). By default I get the "Plugin Settings" Package, Subpackage, Controller Name and Action in the Inspector. How can I get rid of these?
You can remove them by setting their group property to none, another solution would be to not extend the plugin super type and just copy some of the properties from it instead. See TYPO3.Neos/Configuration/NodeTypes.yaml

> How can I access a node property in my controller? I guess there is some magic, but I didn't find any hint in the documentation.
IIRC your node should be available in the controller. Rens did a feature to improve this which might help you https://review.typo3.org/#/c/21768/

> My plugin renders a list of images (<a><img></a>) and has inlineEditable set to FALSE. Still Neos somehow feels responsible for the content. After loading the images as expected the rendering changes to what you can see on http://snag.gy/EgBpL.jpg.
> Did I miss something?
No idea, maybe paste your template to understand what you did.


More information about the Neos mailing list