Allow editors to manage drop downs with giving them access to Developer section
In the main my editors do NOT have access to developer backend but I have a scenario when they are adding new content they select an item from a drop down. The content of the dropdown can change or it may be that I didnt get all the items in the first place.
Either way i want to give the user the ability to "manage" this drop down without having to contact me and without giving them access to the developer section or the data type itself.
Is there an easy way to do this or is it best practise to just give them access to the developer section?
Instead of giving editors access to the developer section you should consider creating a root for your dropdown items at the same level as your website.
So you create a documentype that you call for instance "DropdownRoot" and then you create a documentype for the dropdown value called "Dropdown" for instance and make sure that it can be created directly under "DropdownRoot".
Then you can define a datatype based on the "ultimate picker" datatype where you selected the "DropdownRoot" as the source and make the type a dropdown.
Now you can use this datatype as a property on your documents and the client can manage the values from the content section instead.
Allow editors to manage drop downs with giving them access to Developer section
In the main my editors do NOT have access to developer backend but I have a scenario when they are adding new content they select an item from a drop down. The content of the dropdown can change or it may be that I didnt get all the items in the first place.
Either way i want to give the user the ability to "manage" this drop down without having to contact me and without giving them access to the developer section or the data type itself.
Is there an easy way to do this or is it best practise to just give them access to the developer section?
Appreciate any coments.
S
Hi Stephen
Instead of giving editors access to the developer section you should consider creating a root for your dropdown items at the same level as your website.
So you create a documentype that you call for instance "DropdownRoot" and then you create a documentype for the dropdown value called "Dropdown" for instance and make sure that it can be created directly under "DropdownRoot".
Then you can define a datatype based on the "ultimate picker" datatype where you selected the "DropdownRoot" as the source and make the type a dropdown.
Now you can use this datatype as a property on your documents and the client can manage the values from the content section instead.
Hope this makes sense.
/Jan
is working on a reply...