You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most contentlets, when you view them in the back end they are shown with textboxes, dropdown lists, etc. If you try to edit them, the screen flashes but then if you try to edit them again you can. However in all cases the changes won't "take" until you lock the contentlet for editing (which also changes the buttons available).
For consistency and predictability, pages should work the same way. Instead of textboxes and dropdown lists, though, there would be "Add content" buttons and such, just like when you're editing them.
The text was updated successfully, but these errors were encountered:
The alternative would be to make all the other contents work like pages--give a "view only" presentation (e.g. no dropdown lists, just show the selected value) until the user locks them for editing. That would be a more standard approach anyway, but I think it might break custom fields.
For most contentlets, when you view them in the back end they are shown with textboxes, dropdown lists, etc. If you try to edit them, the screen flashes but then if you try to edit them again you can. However in all cases the changes won't "take" until you lock the contentlet for editing (which also changes the buttons available).
For consistency and predictability, pages should work the same way. Instead of textboxes and dropdown lists, though, there would be "Add content" buttons and such, just like when you're editing them.
The text was updated successfully, but these errors were encountered: