I'm not sure whether to qualify this as a bug or a feature that just hasn't been implemented yet. Regardless it's a huge permission / article state integrity issue.
Joomla! ships with 3 main content contributor roles (groups) Author, Editor, Publisher. In most traditional senses the core concept behind these are:
1. Authors create
Joomla! only partially adheres to this concept.
The author's ability to publish (change article state) should not be dependent on whether the article is already published.
Consider the scenario where an Author creates an article that is then set to "Published" by the Publisher. If an Author/Editor saves a change to that (published) article, those edits are not only saved as a new version but also as the published version.
In practice, when an Author makes changes to a published article, their changes should be saved as a new version, however the previous version should remain published until a Publisher sets that version's state to published.
Effectively publishing an article breaks the integrity of these permissions, and inherent work flow and relationship between Authors, Editors, Publishers.
Unfortunately, it's not as simple as intercepting the Save action, and preventing changes by Authors/Editors to be the new published version.
A pseudo workflow in com_content (or perhaps an entirely new view) is needed. This can be accomplished with the introduction of new states:
Authors create new articles which are automatically saved with the state Awaiting Review.
Editors need a list of all new articles (Awaiting Review), and have the ability to set the state as either (Approved, Rejected, or back to Awaiting Review). Either deescalating back to the Author, escalating to Publishers, or leaving for review by another Editor.
Publishers need a list of all articles approved to be published (Approved) by Editors.
Labels |
Added:
?
|
Labels |
Added:
?
|
Category | ⇒ | Feature Request |
Do we have a tag/label for proposals which should be taken serious in the future? I mean, there is no way to solve that issue right now, but the proposal should be kept in sight until com_content will be refactored.
Labels |
Added:
?
|
||
Build | master | ⇒ | staging |
Labels |
Added:
?
|
Added the label
It may be possible to do today. But I doubt we find someone willing to put that much time into that feature.
Closing as this issue have the Re-evaluate for v4.0 label
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-07-16 11:36:23 |
Closed_By | ⇒ | zero-24 |
Milestone |
Added: |
Milestone |
Added: |
This is something to think about in the future but not doable without someone willing to put a lot of time on it. It requires a workflow editor and to make sure things stay backward compatible. Maybe something for a GSoC.