I have a nested content using partial, is it possible to reuse the nested content but for Macro as well? to allow users to add an accordion to a rich text editor?
No. Even if you define your own nested content types, it won't work properly. This feature has been broken since V8 and there is zero indication that it is going to be fixed anytime soon.
Your best option right now is to use Doc Type Grid Editor. If you wanted to put it inside a rich-text editor, then you're out of luck.
I haven't ported it to v8 (yet? Not sure if it will be), but it's probably pretty simple to do.
Only downside is, that Property Value Converters are not run on macro parameters, so you need to convert the json value from your nested content to IEnumerable
Even if you port it into a package.manifest, nested content doesn't seem to work in macros. Can't really figure out what is going wrong.
Error: [$compile:ctreq] Controller 'umbProperty', required by directive 'valServerMatch', can't be found!
Error: [$compile:ctreq] Controller 'valFormManager', required by directive 'valPropertyMsg', can't be found!
F12 says it loads the empty document type properly, and even shows the option to select which type to add to the nested content. It seems just not being implemented.
Nested content + Macro
Hi,
I have a nested content using partial, is it possible to reuse the nested content but for Macro as well? to allow users to add an accordion to a rich text editor?
Thanks
No. Even if you define your own nested content types, it won't work properly. This feature has been broken since V8 and there is zero indication that it is going to be fixed anytime soon.
Your best option right now is to use Doc Type Grid Editor. If you wanted to put it inside a rich-text editor, then you're out of luck.
In v7 you could use this package to add data types (like your nested content data type) as macro parameter editors. https://our.umbraco.com/packages/developer-tools/parameter-editor-generator/
I haven't ported it to v8 (yet? Not sure if it will be), but it's probably pretty simple to do.
Only downside is, that Property Value Converters are not run on macro parameters, so you need to convert the json value from your nested content to IEnumerable
Even if you port it into a package.manifest, nested content doesn't seem to work in macros. Can't really figure out what is going wrong.
F12 says it loads the empty document type properly, and even shows the option to select which type to add to the nested content. It seems just not being implemented.
is working on a reply...