[MGNLDEMO-361] Eric can edit & publish while Peter is powerless on apps without workflow Created: 10/Oct/14 Updated: 18/Aug/21 Resolved: 18/Aug/21 |
|
| Status: | Closed |
| Project: | Magnolia Demo Projects |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Description |
|
Peter cannot publish pages in Community Edition. This issue is specific to CE since it doesn't have workflow. (In EE, Peter can approve a workitem. The new action availability constraint was not added to /modules/workflow/messageViews/publish/actions/approve.) Update: In 4.5 we had workflow as part of CE and peter was never able to 'activate' anything on a workspace. He was only able to publish from workItems from the inbox. One possible solution is to change the writePermissionRequired to 'false' in CE and switching it to 'true' when installing workflow for that app. which IMO is only an ugly workaround to a conceptual problem we're facing. OTOH, why should peter be able to push something to a public instance (which is a much more harmful action) and not be able to publish (activate) something which is more likely do much less harm, than pushing it to public. My vote goes for reverting or at least change the default of the writePermssionRequired to 'false'. |
| Comments |
| Comment by Espen Jervidalo [ 15/Oct/14 ] |
|
Peter is not able to publish in any apps anymore, except the app is using workflow or he accidentally has write permission on the workspace. |
| Comment by Mikaël Geljić [ 28/Oct/14 ] |
|
Questions:
This issue has to be solved on UX level first, before we implement some silly workaround. Side note: |