Description of the bug
The Revision settings for a content type are not clear. The options under Revision settings are:
- Show option to create new revisions Revisions allow content editors to view changes over time and revert changes if needed.
- Create new revision by default
The current functionality is that the "Show option to create new revisions" actually enables or disables revisions for the content type. If "Show option to create new revisions" is off, the "Create new revision by default" is ignored.
Steps To Reproduce
To reproduce the behavior: 1. Open the configuration page for a content type. 2. Set the Revision settings to uncheck "Show option to create new revisions" and check "Create new revision by default" 3. Edit a node of the content type that was edited. 4. View the revisions of the edited node.
Actual behavior
No revisions is saved for the edited node.
Expected behavior
Since the Revision settings are showing "Show option to create new revisions" unchecked and "Create new revision by default" checked, the revision setting shouldn't be shown on the node edit page, but the revision should be saved.
Alternatively, the Revision settings can be reworded to reflect the actual behavior. Maybe: - Enable the option to create new revisions Revisions allow content editors to view changes over time and revert changes if needed. - Create new revision by default And "Create new revision by default" should be hidden if the first option is disabled.
Additional information
In my use case, I want revisions saved for every node edit without the option to not save a revision. I am able to accomplish this by enabling both check boxes under Revision settings and using the Simplify module to remove the revision setting from the node edit form.
Add any other information that could help, such as: - Backdrop CMS version: 1.24.2
Recent comments
The inability to check for and install updates makes website development and maintenance extremely difficult. Managing over ten websites across two different hosting providers—one of which is...
Unable to run update - fails with Connection timed out
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'