[MGNLDMS-269] Activation fails when using versioning, but not workflow Created: 22/Apr/13 Updated: 22/Jul/14 Resolved: 27/May/14 |
|
| Status: | Closed |
| Project: | Document Management System (closed) |
| Component/s: | None |
| Affects Version/s: | 1.6.6 |
| Fix Version/s: | 1.6.11 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
to reproduce:
result: expected result: |
| Comments |
| Comment by Jan Haderka [ 02/May/13 ] |
|
current only known workaround is to grant users readonly access to the whole documents workspace (and exclude explicitly what users should not be able to see). |
| Comment by Cedric Reichenbach [ 26/May/14 ] |
|
Are there any news on this, i.e. is there a chance this will ever be fixed for Magnolia 4.5? |
| Comment by Jan Haderka [ 27/May/14 ] |
|
Actually checking on Magnolia 4.5.19 on demo, I'm not able to reproduce this issue. Since it was caused by access rights to version store that are managed by core, rather then by anything directly in this module, it was most likely also fixed by some other fix in core. |
| Comment by Zdenek Skodik [ 22/Jul/14 ] |
|
It's fixed by |