[magnolia-dev] [JIRA] (BLOSSOM-231) Blossom seems to have no location in metadata

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-231 
 
 
 
  Blossom seems to have no location in metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 

Fix Version/s:
 
 3.1.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3858) Status indicator is always red for empty optional areas

[JIRA (on behalf of Diana Racho)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diana Racho created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3858 
 
 
 
  Status indicator is always red for empty optional areas  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 status_indicator.png 
 
 
 

Created:
 

 22/Apr/16 4:38 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Diana Racho 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Empty optional areas show always a red status indicator although the page is activated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
  

[magnolia-dev] [JIRA] (DOCU-712) Add graphics to High level project overview page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-712 
 
 
 
  Add graphics to High level project overview page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Julie Legendre Christoph Meier 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-715) LOGTOOLS Module page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-715 
 
 
 
  LOGTOOLS Module page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-698) Update Maven setup page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-698 
 
 
 
  Update Maven setup page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-729) Update i18n pages (and others) regarding new i18n files location and best practices

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-729 
 
 
 
  Update i18n pages (and others) regarding new i18n files location and best practices  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint 9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-718) List of apps page contains items in list that are not apps

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-718 
 
 
 
  List of apps page contains items in list that are not apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint 9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-722) Create "How to participate on the Magnolia documentation"

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-722 
 
 
 
  Create "How to participate on the Magnolia documentation"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-676) mgnl-conf-2016 workshop#

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-676 
 
 
 
  mgnl-conf-2016 workshop#   
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-723) On-demand walkthrough (temp.) documentation

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-723 
 
 
 
  On-demand walkthrough (temp.) documentation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-712) Add graphics to High level project overview page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-712 
 
 
 
  Add graphics to High level project overview page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-711) Provide examples how to use protected content with PUR module.

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-711 
 
 
 
  Provide examples how to use protected content with PUR module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-697) Document the i18n key generators and best practices

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-697 
 
 
 
  Document the i18n key generators and best practices  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-713) Prepare VN sessions

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-713 
 
 
 
  Prepare VN sessions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  8  9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-234) Upgrade sample to Magnolia 5.4.6 and Spring 4.2.5

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-234 
 
 
 
  Upgrade sample to Magnolia 5.4.6 and Spring 4.2.5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 

Summary:
 
 Upgrade sample to Magnolia 5.4.6 and  Site module 1  Spring 4 . 0 2 .5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-234) Upgrade sample to Magnolia 5.4.6 and Spring 4.2.5

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-234 
 
 
 
  Upgrade sample to Magnolia 5.4.6 and Spring 4.2.5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 Site module 1.0.6DAM 2.1.4 Should also include a site definition with template availability configured. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LOGTOOLS-13) Refresh the view when the Levels grid is updated

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-13 
 
 
 
  Refresh the view when the Levels grid is updated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 When a new log level is set up, the grid is not refreshed, meaning, in some cases, the user is not shown that the content was actually updated. The old Logging app used to do this. The cases are:- when changing a logger's level that inherits it from its parent, the tick should disappear- when changing a parent's log level, the children should also get the update 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LOGTOOLS-12) Fix the "Inherited" column value

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-12 
 
 
 
  Fix the "Inherited" column value  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Story Points:
 
 1 0.5 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LOGTOOLS-13) Refresh the view when the Levels grid is updated

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-13 
 
 
 
  Refresh the view when the Levels grid is updated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Story Points:
 
 2 1 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3855) RichTextField required property not functioning properly

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3855 
 
 
 
  RichTextField required property not functioning properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 If i set to required: true, the "*" does not appear in the label.If the richtextfield is required: true, and if other field in the form failed the validation, this richtextfield, even if it has value, will show error. This only happens when you are creating the data. Updating the data will not encounter this issue.  As reported by a user on our forum https://forum.magnolia-cms.com/forum/thread.html?threadId=8c6c0b0f-380d-4e91-be56-c7528856b5f6 and verified personally by yours truly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-3855) RichTextField required property not functioning properly

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3855 
 
 
 
  RichTextField required property not functioning properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Summary:
 
 RichTextField  mandatory asterisk does  required property  not  appear in label  functioning properly 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-234) Upgrade sample to Magnolia 5.4.6 and Site module 1.0.5

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-234 
 
 
 
  Upgrade sample to Magnolia 5.4.6 and Site module 1.0.5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 

Summary:
 
 Upgrade sample to Magnolia 5.4. 5 6  and Site module 1.0.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-8 
 
 
 
  Allow reading the npm auth-token from .npmrc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changed. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal / {code} Note: the tailing '/' is important. Otherwise it will add an entry with 'https://npm.magnolia-cms.com/repository' in .npmrc. Weird..   Reference:http://blog.npmjs.org/post/118393368555/deploying-with-npm-private-moduleshttps://books.sonatype.com/nexus-book/reference/usertoken.html (nexus 2)https://books.sonatype.com/nexus-book/3.0/reference/security.html#realms (nexus 3) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-8 
 
 
 
  Allow reading the npm auth-token from .npmrc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changed. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code}Reference: http://blog.npmjs.org/post/118393368555/deploying-with-npm-private-modules https://books.sonatype.com/nexus-book/reference/usertoken.html (nexus 2)https://books.sonatype.com/nexus-book/3.0/reference/security.html#realms (nexus 3)  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-8 
 
 
 
  Allow reading the npm auth-token from .npmrc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changed. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code} Reference:https://books.sonatype.com/nexus-book/reference/usertoken.html (nexus 2)https://books.sonatype.com/nexus-book/3.0/reference/security.html#realms (nexus 3) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-232) Annotations for declaring template parameters

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-232 
 
 
 
  Annotations for declaring template parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 Right now template parameters can be set using a post create callback. For completeness it would be nice if these could be declared using annotations along with other template settings. Since parameters are defined on the RenderableDefinition interface this annotation should be usable on @Area too.The annotation is a candidate for a repeatable annotation as introduced in Java 8. Magnolia is currently on Java 7 so the annotation should be designed so that it can be used as a repeatable annotation once Magnolia goes to Java 8.https://docs.oracle.com/javase/tutorial/java/annotations/repeating.html In a class hierarchy the annotations should be evaluated from top to bottom (superclass first) so that a subclass can override parameters in its superclass. The post create callback style that's necessary now:{code:java}@PreRegisterpublic void preRegister(ConfiguredTemplateDefinition definition) {Map params = new HashMap<>();params.put("name", "value");definition.setParameters(params);}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-232) Annotations for declaring template parameters

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-232 
 
 
 
  Annotations for declaring template parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 Right now template parameters can be set using a post create callback. For completeness it would be nice if these could be declared using annotations along with other template settings. Since parameters are defined on the RenderableDefinition interface this annotation should be usable on @Area too.The  annotation is a candidate for a repeatable annotation as introduced in Java 8. Magnolia is currently on Java 7 so the annotation should be designed so that it can be used as a repeatable annotation once Magnolia goes to Java 8.https://docs.oracle.com/javase/tutorial/java/annotations/repeating.htmlThe  post create callback style that's necessary now:{code:java}@PreRegisterpublic void preRegister(ConfiguredTemplateDefinition definition) {Map params = new HashMap<>();params.put("name", "value");definition.setParameters(params);}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-8 
 
 
 
  Allow reading the npm auth-token from .npmrc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changes. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-8 
 
 
 
  Allow reading the npm auth-token from .npmrc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has  changes  changed . Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-8 
 
 
 
  Allow reading the npm auth-token from .npmrc  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 22/Apr/16 11:06 AM 
 
 
 

Fix Versions:
 

 1.0.1 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
   

[magnolia-dev] [JIRA] (BLOSSOM-232) Annotations for declaring template parameters

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-232 
 
 
 
  Annotations for declaring template parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 Right now template parameters can be set using a post create callback. For completeness it would be nice if these could be declared using annotations along with other template settings.  Since parameters are defined on the RenderableDefinition interface this annotation should be usable on @Area too. The post create callback style that's necessary now:{code:java}@PreRegisterpublic void preRegister(ConfiguredTemplateDefinition definition) {Map params = new HashMap<>();params.put("name", "value");definition.setParameters(params);}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-234) Upgrade sample to Magnolia 5.4.5 and Site module 1.0.5

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-234 
 
 
 
  Upgrade sample to Magnolia 5.4.5 and Site module 1.0.5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 Should also include a site definition with template availability configured. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (BLOSSOM-234) Upgrade sample to Magnolia 5.4.5 and Site module 1.0.5

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-234 
 
 
 
  Upgrade sample to Magnolia 5.4.5 and Site module 1.0.5  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Tobias Mattsson 
 
 
 

Created:
 

 22/Apr/16 10:07 AM 
 
 
 

Fix Versions:
 

 3.1.3 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (BLOSSOM-233) Duplicate registration of templates with multiple @RequestMapping methods

[JIRA (on behalf of Tobias Mattsson)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Mattsson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-233 
 
 
 
  Duplicate registration of templates with multiple @RequestMapping methods  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 3.1.2 
 
 
 

Assignee:
 
 Tobias Mattsson 
 
 
 

Created:
 

 22/Apr/16 9:57 AM 
 
 
 

Fix Versions:
 

 3.1.3 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tobias Mattsson 
 
 
 
 
 
 
 
 
 
 
While this has no negative impact it is unnecessary and the log output lists the template more than once. 
TemplateExporter should skip registration for template ids that it has already registered. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
   

[magnolia-dev] [JIRA] (LOGTOOLS-12) Fix the "Inherited" column value

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-12 
 
 
 
  Fix the "Inherited" column value  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Fix Version/s:
 
 1.0.1 
 
 
 

Fix Version/s:
 
 1.0 
 
 
 

Account:
 
 
 
 
 

Affects Version/s:
 
 1.0 
 
 
 

Affects Version/s:
 
 1.0.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: 

[magnolia-dev] [JIRA] (LOGTOOLS-14) Improve keyboard navigation in the Log Levels sub app

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-14 
 
 
 
  Improve keyboard navigation in the Log Levels sub app  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 

Created:
 

 22/Apr/16 9:35 AM 
 
 
 

Fix Versions:
 

 1.x 
 
 
 

Labels:
 

 UX 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
Navigating in the Log Levels sub app with a keyboard is unnatural. For instance, the grid is not focused when the view opens, but it should since it's the only element there. In a limited time span, this ticket should implement a few quick wins when navigating with PgUp, PgDown, the keypad, Tab and Shift-Tab. 
 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (PAGES-73) Add action to open the page in a browser tab

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-73 
 
 
 
  Add action to open the page in a browser tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (LOGTOOLS-13) Refresh the view when the Levels grid is updated

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-13 
 
 
 
  Refresh the view when the Levels grid is updated  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 

Created:
 

 22/Apr/16 9:29 AM 
 
 
 

Fix Versions:
 

 1.0.1 
 
 
 

Labels:
 

 UX 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
When a new log level is set up, the grid is not refreshed, meaning, in some cases, the user is not shown that the content was actually updated. The old Logging app used to do this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 

[magnolia-dev] [JIRA] (LOGTOOLS-12) Fix the "Inherited" column value

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-12 
 
 
 
  Fix the "Inherited" column value  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.0.1 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 

Created:
 

 22/Apr/16 9:26 AM 
 
 
 

Fix Versions:
 

 1.0 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
In the Log Levels sub app, the "Inherited" column seems to show true when it should show false (and vice-versa), when compared to the legacy Logging app. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment