Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When not creating a new revision is there any particular reason that the "Set Revision as default" option is still available? If a new revision is not being created then why would this option still be available? In my testing, unchecking the "Create new revision" option and then "Set Revision as default" results in the changes to fields not being saved! I recommend adding some logic to that field so it has no effect if "Create new revision" is disabled.
Comment | File | Size | Author |
---|---|---|---|
#2 | bean-n1891358.patch | 1.67 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaClarified the title and bumped the priority as this is a dataloss bug.
Comment #2
DamienMcKennaThis patch overrides default_revision if the is_new_revision option was unchecked, thus avoiding the dataloss bug.
Comment #3
DamienMcKennaComment #4
indytechcook CreditAttribution: indytechcook commentedTagging with release blocker
Comment #5
indytechcook CreditAttribution: indytechcook commentedThanks!
http://drupal.org/commitlog/commit/22232/669c32d046585e6c3e929c8e0c442bd...