4 results found
-
Explain why fields are read-only and clearly show the active content version
When content fields are read-only, editors should be able to understand why and identify the version they are viewing without checking the URL or adding a Versions gadget.
Currently, historical versions show disabled fields with crossed-out pencil icons, but there is no prominent explanation beside the fields. Version information is available through a small toolbar status icon, the Options menu and the Versions gadget, but these indicators are easy to overlook while editing.
For example, an editor can select a historical version in Compare, leave Compare and return to Properties. The historical version remains open, with fields locked, but there…
1 vote -
Automatic per-edit revision history with before-and-after diff
There is no automatic per-edit revision history. The Change Log records that a save or publish occurred, by which user and when, but identifies content only by machine references (ContentGuid, ContentLink, ContentTypeId) and does not show what changed. The Versions gadget requires manually creating version records and is capped at 20, which does not work for frequently edited pages. Request: automatic per-edit versioning with a visual before-and-after diff and no practical version cap. Our current platform provides this natively, including who made each edit, plus a site-level activity view.
2 votes -
SaaS CMS -- undo/redo feature within versions
On PaaS CMS, there's an ability to roll back/undo changes made within a content version during the current session (see screenshot).
For ex: if I make multiple changes to this page, then clicking that "Undo" link will revert the last change (and clicking it again will revert the prior change, etc) all within the current content version.
In PaaS, if you leave the CMS, or just change pages within the CMS, that link goes away, but it can be helpful at times -- would be great to have this available in SaaS CMS.
10 votes -
Show "Versions" gadget by default
When a new user accesses the CMS for the first time, they must manually add the "Versions" gadget to the UI. Can we have that included by default?
3 votes
- Don't see your idea?