>You may try to explain these "valid reasons". You are unlikely to get anything added to the core on your say so.
>I agree BTW.
read only field - you have a value that you want someone to be able to see but not necessarily update themselves. i.e. a date that an certain action happened on the node (which is not the publish date etc).
hidden field - you have a value that you want to store against a node but its not relevant for anyone to see or potentially edit this field. A calculated value, for example.
are these only applicable to umbraco 4.0.x? we're on 4.5.2, and soon 4.6
imo some of the packages out there that include core functionality that a CMS really needs to provide "out of the box" should be incorporated into the product rather than being add-ons.
but im sure these sorts of considerations have already been made for the umbraco 5 roadmap :)
BTW, it's possible to have a readonly field by using the Label datatype to render a string, (and if it's a value the editor isn't concerned with, I tend to 'hide' them away on the generic properties tab), but it would be good to have the functionality offered by the tab hider and disabled properties packages built into Umbraco.
umbraco properties - read-only or hidden completely
an umbraco property should have the ability to be editable (default) but to also be either "read-only" or hidden completely from the dashboard.
theres definitely valid reasons for needing both of these options and this functionality should be incorporated into the umbraco core asap.
You may try to explain these "valid reasons". You are unlikely to get anything added to the core on your say so.
I agree BTW.
there's packages in the project section for that: http://our.umbraco.org/projects/developer-tools/axendo-disabled-properties and http://our.umbraco.org/projects/backoffice-extensions/attackmonkey-tab-hider
Cheers,
/Dirk
>You may try to explain these "valid reasons". You are unlikely to get anything added to the core on your say so.
>I agree BTW.
read only field - you have a value that you want someone to be able to see but not necessarily update themselves. i.e. a date that an certain action happened on the node (which is not the publish date etc).
hidden field - you have a value that you want to store against a node but its not relevant for anyone to see or potentially edit this field. A calculated value, for example.
>>there's packages in the project section for that: our.umbraco.org/.../axendo-disabled-properties and our.umbraco.org/.../attackmonkey-tab-hider
>>Cheers,
>>/Dirk
are these only applicable to umbraco 4.0.x? we're on 4.5.2, and soon 4.6
imo some of the packages out there that include core functionality that a CMS really needs to provide "out of the box" should be incorporated into the product rather than being add-ons.
but im sure these sorts of considerations have already been made for the umbraco 5 roadmap :)
Hi Andrew,
BTW, it's possible to have a readonly field by using the Label datatype to render a string, (and if it's a value the editor isn't concerned with, I tend to 'hide' them away on the generic properties tab), but it would be good to have the functionality offered by the tab hider and disabled properties packages built into Umbraco.
Cheers,
Hendy
is working on a reply...