On a current project, it is very important that revisions are created any time certain node data is updated. Let's say I am editing node A that has a CER with node B. When I update the value of the field on node A (and then node B gets updated), I would like for a new revision to be created for node B.
There is not necessarily much need for UI changes. The only thing I can think of is providing some kind of configuration settings to enable/disable these revisions or to set the revision message text (including tokens)
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | cer-create_revisions_on_sync-3477490-3.patch | 1.38 KB | megakeegman |
| #2 | cer-create_revisions_on_sync-3477490-2.patch | 953 bytes | megakeegman |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
megakeegman commentedHere is a basic patch that does what I need it to. Very happy if anyone has improvements or recommendations for improvements.
Comment #3
megakeegman commentedUpdating the patch. Patch 2 was missing the parens on a function call. Patch 3 adds a revision timestamp and user id.
Comment #4
socialnicheguru commentedComment #5
anybody@megakeegman totally agree ,could you create a MR please?
Comment #6
smustgrave commentedPossible duplicate of #3326089: Module is auto publishing pages configured with a cer relationship
Comment #8
smustgrave commented@anybody I made an MR and confirmed this creates a revision for us. The pipeline errors are from other areas.
Comment #9
megakeegman commentedThanks for following up here. Sorry I missed this.
Comment #10
anybodyGREAT work @smustgrave! I thought we should maybe make this configurable to allow opt-out, but on the other hand it doesn't need settings for anything.
With the MR it works as expected IMHO, so RTBC from my side. If maintainers think different, please change status again. Thank you!!
Comment #11
anybody