Default revision is exchanged with a non-default for published editing

Created on 28 October 2019, about 5 years ago
Updated 5 September 2024, 4 months ago

When content moderation is enabled and a user is editing the published version the entity in the form state is still replaced with an entity, which is not the default revision.

The whole process is started by the hook implementation content_moderation_entity_prepare_form().

Unfortunately this creates a problem - for example the conflict 2.x module checks whether the entity being editing is in the default revisions and enables its functionality only in this case.

Now with content moderation enabled and even if not working on drafts conflict 2.x will not be able to do its work.

Could we swap the entity only if the user saves a draft instead of swapping the entity before even building the form?

πŸ› Bug report
Status

Closed: duplicate

Version

11.0 πŸ”₯

Component
Content moderationΒ  β†’

Last updated 20 days ago

  • Maintained by
  • πŸ‡¦πŸ‡ΊAustralia @Sam152
Created by

πŸ‡©πŸ‡ͺGermany hchonov πŸ‡ͺπŸ‡ΊπŸ‡©πŸ‡ͺπŸ‡§πŸ‡¬

Live updates comments and jobs are added and updated live.
  • Contributed project blocker

    It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024