[MGNLSTK-543] demo users: eric can't activate Created: 09/Dec/09  Updated: 23/Jan/13  Resolved: 17/Dec/09

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: 1.2
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Zdenek Skodik
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File log    
Issue Links:
relation
is related to MAGNOLIA-2971 workflow: base role should grant read... Closed
is related to MGNLSTK-545 demo users: daniela is not allowed to... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When you try to activate a page with user from templating-kit-editors group,
the request is not send to inbox and can't read workflow definition [activation] dialog message appears
(the full stacktrace is attached).



 Comments   
Comment by Zdenek Skodik [ 09/Dec/09 ]

to fix that the following ACL have be added to the templating-kit-editor role:

  • workspace: config
  • permissions: readOnly for Selected and sub nodes
  • path: /modules/workflow/config/flows

It makes sense to add that to all templating-kit-* roles right away to protect the other use cases from this bug also.

Comment by Philipp Bärfuss [ 15/Dec/09 ]

Two things:

  • update tasks are missing
  • and I would add the permission to the workflow-base role instead to each role in STK
Comment by Zdenek Skodik [ 15/Dec/09 ]

well from my point of view the templating-kit roles should have these permissions
as well - if you have a look at sample users, there are sample developer/editors
whose have templating-kit-* groups assigned and in the the configuration of that
groups any workflow-base role isn't added, the activation is templating-kit-* roles driven.

Comment by Philipp Bärfuss [ 15/Dec/09 ]

We have to guarantee that this base roles are added where needed (actually if you are in the editors group you should just have them)

Generated at Mon Feb 12 07:28:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.