The patch applied as a result from #3083615: Check if scheduled transitions are valid for editing user created a bug.

If you have a role that is allowed to edit but not to publish (but to save a draft or similar) this role can not edit any nodes anymore.

The added hook will need to add a way to remove the check for node listings (admin/content) and direct edit access.

Comments

killes@www.drop.org created an issue. See original summary.

volkerk’s picture

volkerk commented
Status: Active » Postponed (maintainer needs more info)

Initial requirement from #3019678: [Meta] User stories for restricted editors was to deny access to editors when a node is scheduled.

As a restricted editor I want be able to create and edit draft revisions.
As a restricted editor I am not be able to edit scheduled nodes.

These requirement was implemented in #3083615: Check if scheduled transitions are valid for editing user by removing access to a scheduled node when the user does not have sufficient rights on the content_moderation transition.

At that time I also added an issue in scheduler module (#3020250: Deny edit access to scheduled content for unprivileged users), outcome was that editing should be possible and scheduling information should be preseved.

Is this what you want for scmi as well?

volkerk’s picture

volkerk commented
Status: Postponed (maintainer needs more info) » Needs review

It seems to me that the check in scheduler_content_moderation_integration_entity_access needs to be updated.

https://github.com/thunder/scheduler_content_moderation_integration/pull/20 uses value from date field for determining access.

  • volkerk authored 5ed97f5 on 8.x-1.x 
    Issue #3115866 by killes@www.drop.org, volkerk: Followup: Check if...
volkerk’s picture

volkerk commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.