[MAGNOLIA-5626] JCR browser - wrong status lights for component nodes Created: 15/Jan/14  Updated: 31/Jan/14  Resolved: 30/Jan/14

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2

Type: Bug Priority: Major
Reporter: Rainer Blumenthal Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: browser, jcr
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File screenshot-1.jpg    
Issue Links:
duplicate
is duplicated by MGNLUI-2551 Status of site definitions is always ... 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
Release notes required:
Yes
Date of First Response:

 Description   

In the JCR browser the component-nodes appear in "red" - even if they are published.

As we often use this in LIVE environments, this can be really confusing. See screenshot.



 Comments   
Comment by Jan Haderka [ 22/Jan/14 ]

affects also other workspaces. We need to get this back ... mgnl:contentNode should have mgnl:activateable assigned by default as it used to be in 4.5

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