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.For Drupal 8 to support "forward revisions" it must declare during node_save whether the given node object is meant to go in the node table or not. Agentrickard has started a patch to this end at #218755-106: Support revisions in different states
The addition of the is_live property means that many modules implementing hook_node_update() will have to check that the given revision is going live.
For instance, the path module should not change the alias for node/123 if the revision of 123 being saved is not going to the node table.
This patch is a start. There are UI implications to this change. With this patch, data entered in the URL alias field is discarded if the revision isn't going live.
Finally I think this patch will fail testing as it does not include the is_live property from #218755-106: Support revisions in different states and some tests will have to be modified/added to deal with is_live anyway.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | isDefaultRevision-check-in-hook-node-update-1522154-6.patch | 2.52 KB | stevector |
| #1 | is_live-1522154-1.patch | 3.99 KB | stevector |
Comments
Comment #1
stevectorComment #3
Gábor HojtsyRetitled for the current implementation.
Comment #4
hass CreditAttribution: hass commentedI really need to know if something goes live in hook_node_update(). Otherwise I cannot run code in linkchecker only if the node get's published. I already have troubles with D7 workbench moderation now. Please let us solve this finally for D8.
Comment #5
stevectorThanks for bumping this hass. I forgot about this patch. It still needs a reroll. For the purposes of linkchecker in D8 you can check the isDefaultRevision property. This patch is to make sure the rest of core is checking that property too.
Comment #6
stevectorReroll.