[MAGNOLIA-5400] It is not possible to activate or deactivate a user Created: 16/Oct/13  Updated: 21/Oct/13  Resolved: 21/Oct/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.1
Fix Version/s: 5.1.1

Type: Bug Priority: Blocker
Reporter: Jan Haderka Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLSTK-1254 Set mgnl:lastActivated property for d... Closed
dependency
depends upon MGNLSTK-1254 Set mgnl:lastActivated property for d... Closed
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:
Sprint: 5.1.1

 Description   

To reproduce:

  • go to security app
  • change some property on user
  • activation status stays green (expected: amber)(reason: mgnl:lastActivated date is missing in user node)
  • publish user
  • changes are not visible on public (expected: changes are propagated to public instance)


 Comments   
Comment by Jozef Chocholacek [ 17/Oct/13 ]

I cannot reproduce the last step, i.e. I see the changes on public instance. Both on my development environment and the (ATM) last 5.1.1-SNAPSHOT (#28) of the EE bundle. For the rest (activation status) it should be enough to fix the bootstrap files of core & demo-project to use new format with metadata as mixing properties.

Comment by Jozef Chocholacek [ 17/Oct/13 ]

Moved to Magnolia project, as the fix is in magnolia_main.

Comment by Jozef Chocholacek [ 18/Oct/13 ]

User superuser and superuser + anonymous role are now in "changed since last activation" status after the installation, as they are in fact changed by some other module installation after the Core module sets their activation status.

Comment by Jan Haderka [ 18/Oct/13 ]

Update task is fine, but for installation please fix the bootstrap files instead.

Generated at Mon Feb 12 04:04:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.