- Issue created by @Deepthi kumari
- 🇷🇺Russia Chi
Load the revision data accordingly instead of rendering the latest published version.
That's expected behavior. Isn't it? Why would we display unpublished nodes?
- Status changed to Closed: works as designed
12 months ago 7:27am 6 January 2024 - 🇺🇸United States dzinkevich
Coming here with the same issue. One use case is that I inherited a client who has a hero image which is configured at the node level but displayed outside of the node's content region.
When a user submits this node for approval, we don't want to display the current revision, we want to show the revision of the page that we get from the route.
Going to look into this and see how difficult a patch would be.
- 🇺🇸United States dzinkevich
Looks like a patch was very very easy :)
I'm not sure if this is the direction maintainers would like to go, but this adds a twig function that finds the field of a given revision.