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.It's the first time I've installed this module on a site since the change, and it is perplexing.
I can see the use case, but doesn't this behaviour differs from every other pane type?
Via admin section, editing panes, the changes don't show even though the latest revision is "published"
Via Contextual links, you edit the most recent version, and the changes never show.
Forcing a revision on the parent container also doesn't refresh the pane version save (node/X/edit), the only way to show is to use the customise display options for IPE or content settings.
Permissions to access the latter two areas that generally not granted to the average site admins we deal with, so as is the revisioning system is completely unusable for the majority of clients with panels enabled.
Since the aim appears to be to couple edits with the parent containers revision, a possible simple workaround would be similar to this?
So glad the original method of direct reference exists, and will switch to this by default :)
| Comment | File | Size | Author |
|---|---|---|---|
| 1a3e7fdcaf5b45fdbfa3cc07f4a03d54.png | 17.29 KB | Alan D. |
Comments
Comment #2
Alan D. CreditAttribution: Alan D. commentedThe admin settings could be updated to reflect this too.
Show the latest published or the revision that was embedded when viewing the FPP pane?
( ) Entity ID: FPPs will always show the latest published revision. This will not work with the parent pages revisioning system.
(*) Revision ID (non-reusable FPPs only): FPP revision associated with the parent page revision are locked together. This will also force each FPP update to create a new revision.
This controls whether the reference to FPP entities is stored using by entity ID or revision ID.
For example, a panelized entity can revert the entity to previous revision and FPPs will also revert if they are referenced by revision ID. This also allows for editorial workflows using e.g. the Workbench Moderation or Revisioning modules.
Final point, legacy is a bad term to use, as it means somethings obsolete and that this feature will likely be dropped in the future. Clearly a strong use-case to keep this feature!