- 🇬🇧United Kingdom jonathan1055
New features will first be done in the 3.x branch.
In
#3083615: Check if scheduled transitions are valid for editing user →
, a feature was introduced which denies users access to editing nodes that are scheduled to a transition they don't have access to.
While this is the right way to do in most cases, there might be situations where this behavior is not desired.
In our case, we have a Person node type, which represents employees of a company. Some of them might have fixed-term contracts, so we use the Scheduler module to make sure they get unpublished automatically when the contract ends. We're also using Content Moderation with a pretty much default setup with an Editor role that is not allowed to publish or archive.
In this scenario, it feels wrong to deny access to editors. They should be able to create new drafts, which may be published by users with the appropriate permission, until finally the node gets unpublished automatically when the 2-year period is over.
Allow admins to opt in or out to this behavior through a configuration setting. Perhaps it's even necessary to do this on a per-bundle basis.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
New features will first be done in the 3.x branch.