Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status changed on entry edit based on user permissions #477

Closed
robinsowell opened this issue Jul 24, 2020 · 3 comments · Fixed by #3334
Closed

Status changed on entry edit based on user permissions #477

robinsowell opened this issue Jul 24, 2020 · 3 comments · Fixed by #3334
Assignees
Labels
under review An EE team member is reviewing this issue

Comments

@robinsowell
Copy link
Contributor

Description of the problem
Member group 'a' only has permission to post in 'Pending' status. They post, superadmin checks it, switches status to 'open'. Works fine. But if the group 'a' edits, the status reverts to 'Pending'. It shouldn't disallow an existing status based on the member's permissions.

How To Reproduce
Steps to reproduce the behavior:
See above

Environment Details:

  • Version: [e.g. 5.3.2]
  • PHP Version [e.g. 7.1]
  • MySQL Version [e.g. 5.7]
  • OS: [e.g. Linux, macOS, Windows]
  • Web Server: [e.g. Apache, nginx, MAMP, etc.]
@intoeetive
Copy link
Contributor

@robinsowell I think this might be subject for discussion. I believe the idea behind this behaviour might be intentions - after member edits the entry, it's pending again and requires approval because the changes have been made

@intoeetive intoeetive added the under review An EE team member is reviewing this issue label Feb 24, 2021
@intoeetive
Copy link
Contributor

@TomJaeger need your input here

@intoeetive
Copy link
Contributor

Same, or very similar issue, has been reported in #1877

Copying over my comment from there:

In short, the situation might occur when member has permissions on the channel, but does not have permission to the status that the entry has. While this might be intentional, we probably need to show them a warning that the current status might be lost.

intoeetive added a commit that referenced this issue Apr 25, 2023
…th status that's not accessible to member
intoeetive added a commit that referenced this issue Apr 25, 2023
…th status that's not accessible to member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
under review An EE team member is reviewing this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants