On the datatype Muliti Node Tree Piceker from Ucomponents, I would like to be able to add some nodes in the left pabe, before the user choose his preferences.
Would be extra nice, if the pre selected values cant be removed by user.
This is not something that is diretctly supported in the MNTP.
However I'm thinking you could do something like this...
1: Install the tabhider package by Tim Payne (aka AttackMonekey)
2: Define a special tab, which the webmaster/editor user type cannot see where you can select the nodes you want to make sure is always present in the left pane.
3: If it's always the same node types that should be pre-selected on certain document types you could consider installing the standard values package and make sure the nodes are always selected in the tab, which is hidden for certain user types.
Please be aware though that this can get messy if a user is able to delete those special nodes so it might also be an idea to remove the "delete" option on these two nodes for the user types.
Could this approach work for you perhaps? The downside is that it's not fully transparent to the end user where these nodes are defined...but it all depends on the context and the user scenario I suppose.
MNTP: Add pre selected values on node load.
Hi,
On the datatype Muliti Node Tree Piceker from Ucomponents, I would like to be able to add some nodes in the left pabe, before the user choose his preferences.
Would be extra nice, if the pre selected values cant be removed by user.
Can this be done somehow?
Hi Peter
This is not something that is diretctly supported in the MNTP.
However I'm thinking you could do something like this...
1: Install the tabhider package by Tim Payne (aka AttackMonekey)
2: Define a special tab, which the webmaster/editor user type cannot see where you can select the nodes you want to make sure is always present in the left pane.
3: If it's always the same node types that should be pre-selected on certain document types you could consider installing the standard values package and make sure the nodes are always selected in the tab, which is hidden for certain user types.
Please be aware though that this can get messy if a user is able to delete those special nodes so it might also be an idea to remove the "delete" option on these two nodes for the user types.
Could this approach work for you perhaps? The downside is that it's not fully transparent to the end user where these nodes are defined...but it all depends on the context and the user scenario I suppose.
Hope this gives some inspiration at least :)
/Jan
is working on a reply...