Yup, it's umbraco controlled, and don't see why you'd change that? Any reason for doing so?
isDoc attribute is just there to identify document xml nodes (general umbraco properties are defined as attributes on a document xml node) rather than custom properties nodes (properties you define on a document type) which are stored as child xml nodes of a document xml node
It makes sense why it's controlled by Umbraco, but I just have some document types that really don't need to have their own page. Its fine since I can just test the node type in XSLT and filter through the nodes I need. I just thought that if I could maybe control the IsDoc attribute then I could make things easier.
One reason for trying to keep something from being a document is:
XSLTsearch makes use of the IsDoc property to determine which nodes to use by default.
Of course I can edit the macro to exclude doc types, but then upgrades of XSLTsearch will break that.
I would vote for a setting of "Not a Document", and then have that override the Umbraco controlled IsDoc flag where checks are made. Or something along those lines.
I would add another vote for this feature ... along with the ability to hide the property from some user types (e.g. so that only developers could set/unset the flag).
How do I change the isDoc attribute of a node?
Self explanatory really. How can I change the isDoc of any content I create? Or is this controlled by Umbraco?
Yup, it's umbraco controlled, and don't see why you'd change that? Any reason for doing so?
isDoc attribute is just there to identify document xml nodes (general umbraco properties are defined as attributes on a document xml node) rather than custom properties nodes (properties you define on a document type) which are stored as child xml nodes of a document xml node
Hope this helps.
Regards,
/Dirk
It makes sense why it's controlled by Umbraco, but I just have some document types that really don't need to have their own page. Its fine since I can just test the node type in XSLT and filter through the nodes I need. I just thought that if I could maybe control the IsDoc attribute then I could make things easier.
I agree. Some child nodes or child nodes of a certain document type should not be posted as a page on the website.
Vote 1+ for having a property to set this either on the content or preferably even on the document type.
One reason for trying to keep something from being a document is:
XSLTsearch makes use of the IsDoc property to determine which nodes to use by default.
Of course I can edit the macro to exclude doc types, but then upgrades of XSLTsearch will break that.
I would vote for a setting of "Not a Document", and then have that override the Umbraco controlled IsDoc flag where checks are made. Or something along those lines.
I would add another vote for this feature ... along with the ability to hide the property from some user types (e.g. so that only developers could set/unset the flag).
Yes that is what I was after
what did node represent in the old schema as opposed to IsDoc in the new schema?
I'm just trying to figure out what value i need to get this thing working
is working on a reply...