[magnolia-dev] [JIRA] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 At the moment we're using several ways to  colorize and  display  and colorize  messages to users. - plain {{console.log(...)}}- {{helper. printError() | printSuccess() | printImportant() | printInfo()}} using the {{chalk}} library to colorize messages- {{npmlog}} package, the one used by npm itself.We should decide for one approach and stick to it, so that CLI output looks consistent. I'd favour using {{npmlog}} for all of our messaging needs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Sprint: 
 Basel 81  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-4127) Applauncher layout without JCR config

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4127  
 
 
  Applauncher layout without JCR config   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Attachment: 
 screenshot-1.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-4127) Applauncher layout without JCR config

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4127  
 
 
  Applauncher layout without JCR config   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 In QA Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-4081) readOnly checkbox doesn't appear in JCR data

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4081  
 
 
  readOnly checkbox doesn't appear in JCR data   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 

  
 
 
 
 

 
 Thanks to [~sfroger] in SUPPORT-6874, currently when user set field's config 'readOnly' to 'true', our 'defaultValue' is no longer used when populating its value. This issue leads to no value saved into their JCR persistent.Expected result: Separate logic of 'defaultValue' and 'readOnly' in fields which means: 1. When a field is readOnly, make it read only from editors. 2. When user set its 'defaultValue', put that value to field's value.Grep code: {code}info.magnolia.ui.form.field.factory.AbstractFieldFactory.setPropertyDataSourceDefaultValue(Property) {...if (defaultValue != null && !definition.isReadOnly()) {property.setValue(defaultValue);}}{code}Solution: supress suppress  property's readOnly while setting default value  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)

[magnolia-dev] [JIRA] (MGNLUI-4081) readOnly checkbox doesn't appear in JCR data

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4081  
 
 
  readOnly checkbox doesn't appear in JCR data   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 

  
 
 
 
 

 
 Thanks to [~sfroger] in SUPPORT-6874, currently when user set field's config 'readOnly' to 'true', our 'defaultValue' is no longer used when populating its value. This issue leads to no value saved into their JCR persistent.Expected result: Separate logic of 'defaultValue' and 'readOnly' in fields which means: 1. When a field is readOnly, make it read only from editors. 2. When user set its 'defaultValue', put that value to field's value.Grep code: {code}info.magnolia.ui.form.field.factory.AbstractFieldFactory.setPropertyDataSourceDefaultValue(Property) {...if (defaultValue != null && !definition.isReadOnly()) {property.setValue(defaultValue);}}{code} Solution:  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-4081) readOnly checkbox doesn't appear in JCR data

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4081  
 
 
  readOnly checkbox doesn't appear in JCR data   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 

  
 
 
 
 

 
 Thanks to [~sfroger] in SUPPORT-6874, currently when user set field's config 'readOnly' to 'true', our 'defaultValue' is no longer used when populating its value. This issue leads to no value saved into their JCR persistent.Expected result: Separate logic of 'defaultValue' and 'readOnly' in fields which means: 1. When a field is readOnly, make it read only from editors. 2. When user set its 'defaultValue', put that value to field's value.Grep code: {code}info.magnolia.ui.form.field.factory.AbstractFieldFactory.setPropertyDataSourceDefaultValue(Property) {...if (defaultValue != null && !definition.isReadOnly()) {property.setValue(defaultValue);}}{code}Solution: supress property's readOnly while setting default value  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)

[magnolia-dev] [JIRA] (MGNLUI-4131) Prevent triggering actionbar actions twice by doubleclick

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4131  
 
 
  Prevent triggering actionbar actions twice by doubleclick   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Assignee: 
 Roman Kovařík  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-4131) Prevent triggering actionbar actions twice by doubleclick

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4131  
 
 
  Prevent triggering actionbar actions twice by doubleclick   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Project: 
 Magnolia  pages module  UI  
 
 
Key: 
 PAGES MGNLUI - 122 4131  
 
 
Affects Version/s: 
 5.5  
 
 
Affects Version/s: 
 5.4.6  
 
 
Affects Version/s: 
 5.5  
 
 
Affects Version/s: 
 5.4.6  
 
 
Fix Version/s: 
 5.5.2  
 
 
Fix Version/s: 
 5.4.10  
 
 
Fix Version/s: 
 5.4.10  
 
 
Fix Version/s: 
 5.5.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (MGNLUI-4131) Prevent triggering actionbar actions twice by doubleclick

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4131  
 
 
  Prevent triggering actionbar actions twice by doubleclick   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Story Points: 
 13  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-4131) Prevent triggering actionbar actions twice by doubleclick

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4131  
 
 
  Prevent triggering actionbar actions twice by doubleclick   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 

  
 
 
 
 

 
 When an application takes little more time to load the dialog box  f.e.  to edit the component of a page, some of our application editors tries to click the edit button multiple times which opens up multiple dialog box.Is there a way to limit it to open a single dialog, even for a multiple tries to edit the same component.Attached the recordings for your reference.Note: When the multiple dialog box opens up and editor tries to author the top one and save it, the underlying dialog box pops out without the latest changes saved in the top dialog box of the same component, which leads confusions to the editor whether the content has been saved or not.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (PAGES-122) Prevent triggering actionbar actions twice by doubleclick

2017-02-01 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 shubha gowda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-122  
 
 
  Prevent triggering actionbar actions twice by doubleclick   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.4.6, 5.5  
 
 
Assignee: 
 Roman Kovařík  
 
 
Created: 
 01/Feb/17 2:11 PM  
 
 
Fix Versions: 
 5.4.10, 5.5.2  
 
 
Labels: 
 support  
 
 
Priority: 
  Major  
 
 
Reporter: 
 shubha gowda  
 

  
 
 
 
 

 
 When an application takes little more time to load the dialog box to edit the component of a page, some of our application editors tries to click the edit button multiple times which opens up multiple dialog box. Is there a way to limit it to open a single dialog, even for a multiple tries to edit the same component. Attached the recordings for your reference. Note: When the multiple dialog box opens up and editor tries to author the top one and save it, the underlying dialog box pops out without the latest changes saved in the top dialog box of the same component, which leads confusions to the editor whether the content has been saved or not.

[magnolia-dev] [JIRA] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Assignee: 
 Federico Grilli  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Fix Version/s: 
 1.0.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-61) Jumpstart should allow getting bundle without travel demo

2017-02-01 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-61  
 
 
  Jumpstart should allow getting bundle without travel demo   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLRSSAGG-209) The servlet should not give error 500 on non existing feeds.

2017-02-01 Thread on behalf of Roman Kovařík 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-209  
 
 
  The servlet should not give error 500 on non existing feeds.
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Assignee: 
 Jan Haderka Roman Kovařík  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

2017-02-01 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 It was noticed that if the text area stretcher is attached to a field which belongs to a layout which is not our FormView - the extension fails on the client-side and causes the whole layout to break.The cause for that is the usage of the {{form}} field which is initialised in {{TextAreaStretcherConnector#initFormView}} - the field may end up being null, but  than  then  in the rest of the class it is used as if it non-null. The right way of doing it would probably be that the extension does nothing and doesn't show itself if it is not in a Magnolia dialog (all the calculations would anyway be wrong).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

2017-02-01 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Feb/17 1:08 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 It was noticed that if the text area stretcher is attached to a field which belongs to a layout which is not our FormView - the extension fails on the client-side and causes the whole layout to break. The cause for that is the usage of the form field which is initialised in TextAreaStretcherConnector#initFormView - the field may end up being null, but than in the rest of the class it is used as if it non-null.  The right way of doing it would probably be that the extension does nothing and doesn't show itself if it is not in a Magnolia dialog (all the calculations would anyway be wrong).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (NPMCLI-95) Help users with outdated Node versions

2017-02-01 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-95  
 
 
  Help users with outdated Node versions   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Fix Version/s: 
 1.0.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-95) Help users with outdated Node versions

2017-02-01 Thread JIRA (on behalf of Robert Kowalski) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Kowalski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-95  
 
 
  Help users with outdated Node versions   
 

  
 
 
 
 

 
Change By: 
 Robert Kowalski  
 

  
 
 
 
 

 
 Provide a nice warning with instructions how to continue to users with outdated Node versions.The warning can be required in our main entry point.Pseudocode:{code}require('./node-version-warning.js'){code}{code}// node-version-warning.jsif (/.6/.test(process.version)) { throw new Error('please download Node 6 from example.org')}{code} Real world example: https://github.com/apache/couchdb-fauxton/blob/master/version-check.js  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-95) Help users with outdated Node versions

2017-02-01 Thread JIRA (on behalf of Robert Kowalski) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Kowalski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-95  
 
 
  Help users with outdated Node versions   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Feb/17 11:39 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Robert Kowalski  
 

  
 
 
 
 

 
 Provide a nice warning with instructions how to continue to users with outdated Node versions. The warning can be required in our main entry point. Pseudocode: 

 

require('./node-version-warning.js')
 

 

 


// node-version-warning.js
if (/.6/.test(process.version)) { throw new Error('please download Node 6 from example.org')}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (MGNLRSSAGG-209) The servlet should not give error 500 on non existing feeds.

2017-02-01 Thread on behalf of Roman Kovařík 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-209  
 
 
  The servlet should not give error 500 on non existing feeds.
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 In QA Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-93) Jumpstart command does not update magnolia.properties reliably

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-93  
 
 
  Jumpstart command does not update magnolia.properties reliably   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-16) As a workflow editor, I would like to configure my user task directly in the editor properties panel

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-16  
 
 
  As a workflow editor, I would like to configure my user task directly in the editor properties panel   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-15) As a workflow editor, I would like to configure my task directly in the editor properties panel

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-15  
 
 
  As a workflow editor, I would like to configure my task directly in the editor properties panel   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-11) As a developer, I want to create a tutorial on how to install and use the module

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-11  
 
 
  As a developer, I want to create a tutorial on how to install and use the module   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-14) As a developer, I want to externalize the task input/ouput parameters to the JCR task config

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-14  
 
 
  As a developer, I want to externalize the task input/ouput parameters to the JCR task config   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-8) As a workflow editor, I want to be able to send email at different step of my workflow

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-8  
 
 
  As a workflow editor, I want to be able to send email at different step of my workflow   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-17) As a workflow editor, I would like to configure my call activities directly in the editor properties panel

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-17  
 
 
  As a workflow editor, I would like to configure my call activities directly in the editor properties panel   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-7) As a workflow editor, I want the default input variable to be added automatically on save

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-7  
 
 
  As a workflow editor, I want the default input variable to be added automatically on save   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-18) As a workflow editor, I would like to be able to create decision node without any knowledges of Magnolia internal variables & classes

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-18  
 
 
  As a workflow editor, I would like to be able to create decision node without any knowledges of Magnolia internal variables & classes   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (MGNLWKLED-10) As a developer, I want to document the module wiki page

2017-02-01 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-10  
 
 
  As a developer, I want to document the module wiki page   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Fix Version/s: 
 0.0.2  
 
 
Fix Version/s: 
 0.0.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 At the moment we're using several ways to colorize and display messages to users. - plain {{console.log(...)}}- {{helper. printError() | printSuccess() | printImportant() | printInfo()}} using the {{chalk}} library to colorize messages- {{ npm-log npmlog }} package, the one used by npm itself.We should decide for one approach and stick to it, so that CLI output looks consistent. I'd favour using {{npm-log}} for all of our messaging needs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 At the moment we're using several ways to colorize and display messages to users. - plain {{console.log(...)}}- {{helper. printError() | printSuccess() | printImportant() | printInfo()}} using the {{chalk}} library to colorize messages- {{npmlog}} package, the one used by npm itself.We should decide for one approach and stick to it, so that CLI output looks consistent. I'd favour using {{ npm-log npmlog }} for all of our messaging needs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 At the moment we're using several ways to colorize and display messages to users. - plain {{console.log(...)}}- {{helper. printError() | printSuccess() | printImportant() | printInfo() }} using the {{chalk}} library to colorize messages- {{npm-log}} package, the one used by npm itself.We should decide for one approach and stick to it, so that CLI output looks consistent. I'd favour using {{npm-log}} for all of our messaging needs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (NPMCLI-94) Use consistent logging style

2017-02-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Feb/17 10:29 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Federico Grilli  
 

  
 
 
 
 

 
 At the moment we're using several ways to colorize and display messages to users.  
 
plain console.log(...) 
helper. printError() | printSuccess() | printImportant() | printInfo() }} using the {{chalk library to colorize messages 
npm-log package, the one used by npm itself. 
 We should decide for one approach and stick to it, so that CLI output looks consistent. I'd favour using npm-log for all of our messaging needs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-349) Deletion workflow message should not be identical to publishing changes

2017-02-01 Thread JIRA (on behalf of Milan Divilek) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Milan Divilek reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-349  
 
 
  Deletion workflow message should not be identical to publishing changes   
 

  
 
 
 
 

 
Change By: 
 Milan Divilek  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 In QA Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-795) Referencing a template with an ID

2017-02-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-795  
 
 
  Referencing a template with an ID   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 17 , Docu Sprint 18  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-771) Add an example of a filtered select field

2017-02-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-771  
 
 
  Add an example of a filtered select field   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 17 , Docu Sprint 18  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-925) Review My first content app tutorial

2017-02-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-925  
 
 
  Review My first content app tutorial   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 16, Docu Sprint 17 , Docu Sprint 18  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-741) Update multisite docs

2017-02-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-741  
 
 
  Update multisite docs   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 12, Docu Sprint 16, Docu Sprint 17 , Docu Sprint 18  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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-926) Release notes for 5.4.11

2017-02-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-926  
 
 
  Release notes for 5.4.11   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 17 , Docu Sprint 18  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




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] (YAMLEXT-8) Definitions app crashes in 5.5.1 (maybe invalid yaml?)

2017-02-01 Thread JIRA (on behalf of Florian Fuchs) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florian Fuchs created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Yaml extensions /  YAMLEXT-8  
 
 
  Definitions app crashes in 5.5.1 (maybe invalid yaml?)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 
 
Created: 
 01/Feb/17 8:55 AM  
 
 
Environment: 
 Magnolia EE 5.5.1 / light-yaml 1.1  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Florian Fuchs  
 

  
 
 
 
 

 
 It looks like the definitions app crashes now, maybe if there is some invalid yaml? Without the dependency it doesn't crash. 

 
[2017-01-30 10:56:44,224][ERROR] info.magnolia.ui.admincentral.AdmincentralErrorHandler [http-nio-8080-exec-4]: AdmincentralUI has encountered an unhandled exception.
com.vaadin.ui.Table$CacheUpdateException: Error during Table cache update. Additional causes not shown.
	at com.vaadin.ui.Table.maybeThrowCacheUpdateExceptions(Table.java:1767)
	at com.vaadin.ui.Table.refreshRenderedCells(Table.java:1756)
	at com.vaadin.ui.Table.enableContentRefreshing(Table.java:3279)
	at com.vaadin.ui.Table.changeVariables(Table.java:3121)
...
Caused by: java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.util.Map
	at org.mgnlconfig.yaml.MgnlYaml.parseYamlConfigData(MgnlYaml.java:66)
	at org.mgnlconfig.yaml.YamlConfigurationDataProvider.parseConfigurationData(YamlConfigurationDataProvider.java:64)
	at org.mgnlconfig.YamlDefinitionProvider.refreshYamlData(YamlDefinitionProvider.java:101)
	at org.mgnlconfig.YamlDefinitionProvider.get(YamlDefinitionProvider.java:76)
	at org.mgnlconfig.YamlDefinitionProvider.isValid(YamlDefinitionProvider.java:90)
	at info.magnolia.config.registry.AbstractDefinitionProviderWrapper.isValid(AbstractDefinitionProviderWrapper.java:71)
	at info.magnolia.definitions.app.overview.data.DefinitionProviderId.getStyle(DefinitionProviderId.java:116)
	at