Great extension -- using it to get around the (supremely annoying) fact that doctypes can't be nested under each other after they've been created.
Works as advertised, except for properties whose alias names start with "umbraco", which it seems to consistently ignore. Is there a specific reason for this? Some of the most useful properties to inherit/mixin are umbracoRedirect, umbracoUrlName, umbracoUrlAlias and umbracoNaviHide, but none of them show up.
Sorry for the delay in getting back to you. Hmm, we might have put code in to block "umbraco" prefixed fields in a bid not to copy all the default ones, but as you rightly point out, it also blocks the special keywords. I'll take a look and see if we can't add a whitelist.
Seems to ignore all "umbraco*" property aliases?
Hi guys,
Great extension -- using it to get around the (supremely annoying) fact that doctypes can't be nested under each other after they've been created.
Works as advertised, except for properties whose alias names start with "umbraco", which it seems to consistently ignore. Is there a specific reason for this? Some of the most useful properties to inherit/mixin are umbracoRedirect, umbracoUrlName, umbracoUrlAlias and umbracoNaviHide, but none of them show up.
Hoping it can be fixed!
[I'm on Umbraco 4.7.0]
Hey Dan,
Sorry for the delay in getting back to you. Hmm, we might have put code in to block "umbraco" prefixed fields in a bid not to copy all the default ones, but as you rightly point out, it also blocks the special keywords. I'll take a look and see if we can't add a whitelist.
Many thanks
Matt
Hi Matt,
I figured that was probably the reason. If you're able to add a whitelist for the specific keywords, that'd be great!
- Dan
Hey Dan,
We've just released a 1.3 release that should now allow "umbraco" prefixed fields. It also adds nice icons to identify Mixins too =)
Cheers
Matt
Hi Matt,
Awesome work, both on the whitelisting and the new icons. Works exactly as advertised -- thanks!
- Dan
is working on a reply...