[MGNLWORKFLOW-134] pages under workflow should not be editable Created: 02/Sep/13 Updated: 07/Oct/13 Resolved: 07/Oct/13 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Boris Kraft | Assignee: | Espen Jervidalo |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| 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 |
|
It seems that currently a page under workflow can still be edited. Is that what we want? Previously a page under workflow was locked from editing and I believe that is the best way to do it, as it makes sure that what is signed off is also what gets published. SO, IMHO you need to make sure that you cannot edit a page once it is in workflow. |
| Comments |
| Comment by Boris Kraft [ 03/Sep/13 ] |
|
The correct behavior is that the version of the page under workflow is not editable. The page itself is. It was my impression that I can actually edit that version in 5, which would be wrong. The confusing "action" is that from the message in Pulse I can "preview" the item, which will show the correct version under workflow. There however I have an "edit" action. Granted, this edits the current version, not the one under workflow, which might make sense, but to me it implied that I can actually edit the version that is under workflow, so it confuses me. Interaction designer, help! |
| Comment by Espen Jervidalo [ 07/Oct/13 ] |
|
This has been fixed in 5.1. Indeed the actions were not disabled, but editing was not possible on the actual versioned node. |