I love the thinking behind this extension and the now "built-in" nested content. But there's one thing I feel is still missing from them and that is "blueprints, templates, pre-filled defaults" call them what you will.
v7.7 is offering this out of the box for an entire doctype/page but I was wondering if the same could be possible for the modular fragments that are possible with your extensions?
If it could be added it would essentially do away with the "repo nodes" which are a very common way of picking re-usable content via an MNTP picker. The annoying thing about working this way is you need to write a lot of extra code to render them out plus you end with nodes that will never have a useable url in the tree.
doctype templates/blueprints/defaults
I love the thinking behind this extension and the now "built-in" nested content. But there's one thing I feel is still missing from them and that is "blueprints, templates, pre-filled defaults" call them what you will.
v7.7 is offering this out of the box for an entire doctype/page but I was wondering if the same could be possible for the modular fragments that are possible with your extensions?
If it could be added it would essentially do away with the "repo nodes" which are a very common way of picking re-usable content via an MNTP picker. The annoying thing about working this way is you need to write a lot of extra code to render them out plus you end with nodes that will never have a useable url in the tree.
Any thoughts welcome.
Martin
is working on a reply...