[magnolia-dev] [JIRA] (JSMODELS-11) Javascript "undefined" value should be treated as null value in freemarker

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-11  
 
 
  _javascript_ "undefined" value should be treated as null value in freemarker   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
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] (MGNLDEMO-215) Allow to use YAML export in Tours app

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-215  
 
 
  Allow to use YAML export in Tours app   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 

  
 
 
 
 

 
 Instead of using {{info.magnolia.ui.framework.action.ExportActionDefinition}} Tours app should use {{info.magnolia.ui.framework.action. OpenCreateDialogActionDefinition OpenExportDialogActionDefinition }} with {{ui-admincentral:export}} dialog which allows to select XML or YAML export.  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Assignee: 
 Antonín Juran  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 

  
 
 
 
 

 
 Use {{info.magnolia.ui.framework.action.OpenExportDialogActionDefinition}} class in configuration of export action  instead of {{info . magnolia.ui.framework.action.OpenCreateDialogActionDefinition}}.  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Sprint: 
 Kromeriz 100  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 

  
 
 
 
 

 
 Use {{ info.magnolia.ui.framework.action. OpenExportDialogActionDefinition}} class in configuration of export action.  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 

  
 
 
 
 

 
 Use {{ { OpenExportDialogActionDefinition}} }  class in configuration of export action.  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 

  
 
 
 
 

 
 Use ```OpenExportDialogActionDefinition``` class in configuration of export action  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 

  
 
 
 
 

 
 Use  ```  {{{ OpenExportDialogActionDefinition ``` }}}  class in configuration of export action .  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-136) Change definition of export action

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-136  
 
 
  Change definition of export action   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 5.5.4  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 19/Jun/17 9:54 AM  
 
 
Fix Versions: 
 5.5.5  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Antonín Juran  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

[magnolia-dev] [JIRA] (MGNLCACHE-180) EhCache module throws IllegalStateException – State is UNINITIALIZED

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-180  
 
 
  EhCache module throws IllegalStateException – State is UNINITIALIZED   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Fix Version/s: 
 5.5.5  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-215) Allow to use YAML export in Tours app

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-215  
 
 
  Allow to use YAML export in Tours app   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Fix Version/s: 
 1.1.4  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-102) Adjust SearchTemplatingFunctions to query whole workspace

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-102  
 
 
  Adjust SearchTemplatingFunctions to query whole workspace   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Affects Version/s: 
 1.1.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] (MTE-102) Adjust SearchTemplatingFunctions to query whole workspace

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-102  
 
 
  Adjust SearchTemplatingFunctions to query whole workspace   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Fix Version/s: 
 1.1.3  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLRESTCL-26) Context attribute is not installed during installation

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Castelli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 REST Client /  MGNLRESTCL-26  
 
 
  Context attribute is not installed during installation   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 1.0.9  
 
 
Assignee: 
 Antonín Juran  
 
 
Attachments: 
 rest-easy install message.png  
 
 
Created: 
 22/May/17 1:24 PM  
 
 
Labels: 
 to-estimate  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Andrea Castelli  
 

  
 
 
 
 

 
 In the installation I receive this message. Do I need to configure something? is it expected? 

 
Magnolia RESTEasy client module (version 1.0.9)
Module '/modules/standard-templating-kit' is not installed. Context attribute is not installed. 

  
 

  
 
 
 
 

 
 
 

 
 
  

[magnolia-dev] [JIRA] (MGNLCACHE-134) Allow to use multiple cache implementations at time

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-134  
 
 
  Allow to use multiple cache implementations at time   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Fix Version/s: 
 5.5.5  
 
 
Fix Version/s: 
 5.4.4  
 

  
 
 
 
 

 
 
 

 
 
 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] (PAGES-131) Use new JCR export dialog

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-131  
 
 
  Use new JCR export dialog   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Assignee: 
 Antonín Juran  
 

  
 
 
 
 

 
 
 

 
 
 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-4179) JCR Export improvements

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Isn't possible to import yaml file on Ubuntu 16.04 (tested on Firefox and Chrome browsers). Mime type of yaml file is "application/x-yaml" which is not allowed in upload field.  
 

  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4179  
 
 
  JCR Export improvements   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
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: 

[magnolia-dev] [JIRA] (MGNLUI-322) Location fragment should be escaped

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-322  
 
 
  Location fragment should be escaped   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Fix Version/s: 
 5.5.4  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-139) Wrong nodes order after publishing

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-139  
 
 
  Wrong nodes order after publishing   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Fix Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-139) Wrong nodes order after publishing

[on behalf of Antonín Juran]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonín Juran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-139  
 
 
  Wrong nodes order after publishing   
 

  
 
 
 
 

 
Change By: 
 Antonín Juran  
 
 
Assignee: 
 Antonín Juran  
 

  
 
 
 
 

 
 
 

 
 
 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] (TASKMGMT-26) Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Task Management /  TASKMGMT-26 
 
 
 
  Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 1.1.3 
 
 
 

Fix Version/s:
 
 1.1.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (TASKMGMT-26) Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Task Management /  TASKMGMT-26 
 
 
 
  Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 1.1.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (TASKMGMT-26) Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Task Management /  TASKMGMT-26 
 
 
 
  Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Project:
 
 Magnolia Task Management 
 
 
 

Key:
 
 MAGNOLIA TASKMGMT - 6875 26 
 
 
 

Security:
 
 Public 
 
 
 

Affects Version/s:
 
 1.2 
 
 
 

Affects Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (TASKMGMT-26) Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Task Management /  TASKMGMT-26 
 
 
 
  Duplicate libs in bundle cglib-2.2 and cglib-nodep-3.2.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 1.2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLDEMO-193) Can't logout from travel-demo on WebSphere AS

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-193 
 
 
 
  Can't logout from travel-demo on WebSphere AS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 1.1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLDEMO-193) Can't logout from travel-demo on WebSphere AS

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-193 
 
 
 
  Can't logout from travel-demo on WebSphere AS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 1.1 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4070) When starting About Magnolia app on WebSphere AS 9, 'ERROR info.magnolia.about.app.AboutPresenter: java.lang.VerifyError' is thrown.

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4070 
 
 
 
  When starting About Magnolia app on WebSphere AS 9, 'ERROR info.magnolia.about.app.AboutPresenter: java.lang.VerifyError' is thrown.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 08/Nov/16 3:44 PM 
 
 
 

Environment:
 

 WebSphere AS 9 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
When starting About Magnolia app on WebSphere AS, 'ERROR info.magnolia.about.app.AboutPresenter: java.lang.VerifyError' is thrown. It causes that information about Database and Java DB Driver is unknown. 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLDEMO-193) Can't logout from travel-demo on WebSphere AS

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-193 
 
 
 
  Can't logout from travel-demo on WebSphere AS  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 08/Nov/16 3:24 PM 
 
 
 

Environment:
 

 WebSphere AS 9 
 
 
 

Fix Versions:
 

 1.1 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Can't logout from travel-demo on WebSphere AS. Request parameter mgnlLogout needs to have some value. 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4022) Move dialog actions from ui-admincentral to ui-dialog module

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4022 
 
 
 
  Move dialog actions from ui-admincentral to ui-dialog module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4022) Move dialog actions from ui-admincentral to ui-dialog module

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4022 
 
 
 
  Move dialog actions from ui-admincentral to ui-dialog module  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Sep/16 8:23 AM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3883) Dialogs have Cancel and Save Changes actions by default

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3883 
 
 
 
  Dialogs have Cancel and Save Changes actions by default   
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4015) Install new app icon for Google Analytics app

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4015 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Affects Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4015) Install new app icon for Google Analytics app

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4015 
 
 
 
  Install new app icon for Google Analytics app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Project:
 
 Magnolia  Google Analytics Visualization  UI 
 
 
 

Key:
 
 MGNLGAV MGNLUI - 36 4015 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 1.1 
 
 
 

Fix Version/s:
 
 1.0.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-4012) Move property isn't possible

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4012 
 
 
 
  Move property isn't possible  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Sprint:
 
 Kromeriz 60 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4012) Move property isn't possible

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4012 
 
 
 
  Move property isn't possible  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Priority:
 
 Neutral Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4012) Move property isn't possible

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4012 
 
 
 
  Move property isn't possible  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-4012) Move property isn't possible

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4012 
 
 
 
  Move property isn't possible  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 08/Sep/16 11:12 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 

[magnolia-dev] [JIRA] (MGNLRSSAGG-196) Raise dependency for rometools from 1.0 to 1.7

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-196 
 
 
 
  Raise dependency for rometools from 1.0 to 1.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 2.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3961) Adjust test to changes in MAGNOLIA-6686

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3961 
 
 
 
  Adjust test to changes in MAGNOLIA-6686  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-196) Raise dependency for rometools from 1.0 to 1.7

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-196 
 
 
 
  Raise dependency for rometools from 1.0 to 1.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Raise dependency for rometools from 1.0 to 1. 6 7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-196) Raise dependency for rometools from 1.0 to 1.6

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-196 
 
 
 
  Raise dependency for rometools from 1.0 to 1.6  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3961) Adjust test to changes in MAGNOLIA-6686

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3961 
 
 
 
  Adjust test to changes in MAGNOLIA-6686  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 25/Jul/16 1:53 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3928) Security Problem Sample-App: Allows cross site scripting

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3928 
 
 
 
  Security Problem Sample-App: Allows cross site scripting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.3.16 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3928) Security Problem Sample-App: Allows cross site scripting

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3928 
 
 
 
  Security Problem Sample-App: Allows cross site scripting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Security Problem Sample-App: Allows cross site  scriting  scripting 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3928) Security Problem Sample-App: Allows cross site scriting

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3928 
 
 
 
  Security Problem Sample-App: Allows cross site scriting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLACTIVATION-131) Activation fails because of content type is not set

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-131 
 
 
 
  Activation fails because of content type is not set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.3.6 
 
 
 

Fix Version/s:
 
 5.4.4 
 
 
 

Fix Version/s:
 
 5.4.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLACTIVATION-131) Activation fails because of content type is not set

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-131 
 
 
 
  Activation fails because of content type is not set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.3.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLACTIVATION-131) Activation fails because of content type is not set

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-131 
 
 
 
  Activation fails because of content type is not set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.4.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (MGNLACTIVATION-131) Activation fails because of content type is not set

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-131 
 
 
 
  Activation fails because of content type is not set  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Jun/16 1:14 PM 
 
 
 

Fix Versions:
 

 5.3.x 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
Activation fails because of content type is not set. See stack trace bellow: 2016-06-22 14:14:29,535 ERROR dule.exchangetransactional.TransactionalSyndicator: Failed to activate content. info.magnolia.cms.exchange.ExchangeException: Not able to send the activation request http://localhost:8080/magnoliaPublic/.magnolia/activation: no content-type at info.magnolia.module.activation.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:449) at info.magnolia.module.exchangetransactional.TransactionalSyndicator$2.run(TransactionalSyndicator.java:204) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.UnknownServiceException: no content-type at java.net.URLConnection.getContentHandler(URLConnection.java:1241) at java.net.URLConnection.getContent(URLConnection.java:740) at info.magnolia.module.activation.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:434) ... 3 more 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3912) CLONE - Allow to define own implementation of SubAppContext for sub apps

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3912 
 
 
 
  CLONE - Allow to define own implementation of SubAppContext for sub apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Jaroslav Simak Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3912) CLONE - Allow to define own implementation of SubAppContext for sub apps

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3912 
 
 
 
  CLONE - Allow to define own implementation of SubAppContext for sub apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Sprint:
 
 Kromeriz 43 , Kromeriz 48 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3912) CLONE - Allow to define own implementation of SubAppContext for sub apps

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3912 
 
 
 
  CLONE - Allow to define own implementation of SubAppContext for sub apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.3.15 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.4.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3912) CLONE - Allow to define own implementation of SubAppContext for sub apps

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3912 
 
 
 
  CLONE - Allow to define own implementation of SubAppContext for sub apps  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jaroslav Simak 
 
 
 

Created:
 

 14/Jun/16 3:33 PM 
 
 
 

Fix Versions:
 

 5.4.7, 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLDEMO-168) 'Rename tour' action doesn't work.

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-168 
 
 
 
  'Rename tour' action doesn't work.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 0.11 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 03/Jun/16 9:18 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLDEMO-168) 'Rename tour' action in Tours app doesn't work.

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-168 
 
 
 
  'Rename tour' action in Tours app doesn't work.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 'Rename tour' action  in Tours app  doesn't work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGS-123) Import action throws exception

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Sitemap Module /  MGNLGS-123 
 
 
 
  Import action throws exception  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 2.3.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 03/Jun/16 8:56 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
Reproduce: 
 

Add sitemap
 

Export sitemap
 

Add folder
 

Import exported sitemap to added folder
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 

[magnolia-dev] [JIRA] (MGNLUI-3837) Action to expand folders

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3837 
 
 
 
  Action to expand folders  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.4.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3881) Asset App: i18n enabled will force "save changes" button to next line

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3881 
 
 
 
  Asset App: i18n enabled will force "save changes" button to next line  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.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] (MGNLUI-3880) Allow to define own implementation of SubAppContext for sub apps

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3880 
 
 
 
  Allow to define own implementation of SubAppContext for sub apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.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] (MGNLUI-3853) If the last subapp tab title is too long it is unclickable

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Arrow for switching tabs can override arrows for maximizing an app or cross for closing app. See attached picture. 
 
 
 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3853 
 
 
 
  If the last subapp tab title is too long it is unclickable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3853) If the last subapp tab title is too long it is unclickable

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3853 
 
 
 
  If the last subapp tab title is too long it is unclickable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Attachment:
 
 pic.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-61) DefaultValue does not work for page properties

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Isn't updated configuration for create page dialog. 
 
 
 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-61 
 
 
 
  DefaultValue does not work for page properties   
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Status:
 
 pre-integration QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3856) Bar with Trinity icons and login menu area in AdminCentral stays hidden after enlarging an app window and closing the app

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3856 
 
 
 
  Bar with Trinity icons and login menu area in AdminCentral stays hidden after enlarging an app window and closing the app  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 1.png, 2.png, 3.png 
 
 
 

Created:
 

 21/Apr/16 3:31 PM 
 
 
 

Fix Versions:
 

 5.4.7 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Bar with Trinity icons and login menu area in AdminCentral stays hidden after enlarging an app window and closing the app, see attached pictures. 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3837) Action to expand folders

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Use existing event handling of ContentChangedEvent in BrowserPresenter 
 
 
 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3837 
 
 
 
  Action to expand folders  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Status:
 
 pre-integration QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3837) Action to expand folders

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3837 
 
 
 
  Action to expand folders  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Labels:
 
 blocked 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-35) Adjust UI tests to changes in PAGES-67

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-35 
 
 
 
  Adjust UI tests to changes in PAGES-67  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.4.6 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-35) Adjust UI tests to changes in PAGES-67

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-35 
 
 
 
  Adjust UI tests to changes in PAGES-67  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Sprint:
 
 Kromeriz 38 
 
 
 

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] (MGNLCE-35) Modify UI tests

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-35 
 
 
 
  Modify UI tests  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 

Created:
 

 07/Apr/16 2:01 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-35) Adjust UI tests to changes in PAGES-67

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-35 
 
 
 
  Adjust UI tests to changes in PAGES-67  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Modify Adjust  UI tests  to changes in PAGES-67 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-67) Rename texts in "Create new component" dialog

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Breaks UI tests 
 
 
 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-67 
 
 
 
  Rename texts in "Create new component" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3837) Action to expand folders

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3837 
 
 
 
  Action to expand folders  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3820) Content Apps should offer a default action per node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*.  h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item. Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything.     MGNLUI-3774 introduces {{DelegateByNodeTypeAction}} which can be used for the default action. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-3774) Provide action which delegates to another action by node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*.   -It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win. -  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3774) Provide action which delegates to another action by node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*.  -It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win.-  h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item.Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3820) Content Apps should offer a default action per node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*.  It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win. h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item. Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3820) Content Apps should offer a default action per node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*. Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything. MGNLUI-3774 introduces {{DelegateByNodeTypeAction}} which can be used for the default action. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3820) Content Apps should offer a default action per node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3774) Provide action which delegates to another action by node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*. -It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win. -  h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item.Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3774) Provide action which delegates to another action by node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*.  - It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win.    -   h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item.Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3821) Provide API for collapse node

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3821 
 
 
 
  Provide API for collapse node  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 8:33 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3820) Content Apps should offer a default action per node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 CLONE -  Content Apps should offer a default action per node type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3820) CLONE - Content Apps should offer a default action per node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  CLONE - Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 

Components:
 

 content app 
 
 
 

Created:
 

 23/Mar/16 8:20 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Labels:
 

 quickwin support to-specify 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Our content apps 

[magnolia-dev] [JIRA] (MGNLUI-3774) Provide delegate action by node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide delegate action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Content Apps should offer a default Provide delegate  action  per  by  node type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3774) Provide action which delegates to another action by node type

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Provide  delegate  action  which delegates to another action  by node type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-21) Page intro component

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-21 
 
 
 
  Page intro component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-74) Use i18n "best practices" in tempting essentials

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-74 
 
 
 
  Use i18n "best practices" in tempting essentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Sprint:
 
 Kromeriz 29 
 
 
 

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] (MTE-74) Use i18n "best practices" in tempting essentials

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-74 
 
 
 
  Use i18n "best practices" in tempting essentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Roman Kovařík Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-74) Use i18n "best practices" in tempting essentials

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-74 
 
 
 
  Use i18n "best practices" in tempting essentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Do not set i18n-basename, label, description on dialogs and templates - instead make use of autogenerated keys and use bundles within {{mgnl-i18n}} folder.Move keys from "old" bundles  - magnolia-travel-tours/src/main/resources/info/magnolia/module/travel-tours/messages- magnolia-travel-demo/src/main/resources/info/magnolia/module/travel-demo/messages  into {{mgnl-i18n}} folder wherever possible. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-139) Dialog broken for some travel-demo page templates since MTK

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-139 
 
 
 
  Dialog broken for some travel-demo page templates since MTK  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-139) Dialog broken for some travel-demo page templates since MTK

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-139 
 
 
 
  Dialog broken for some travel-demo page templates since MTK  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-139) Dialog broken for some travel-demo page templates since MTK

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-139 
 
 
 
  Dialog broken for some travel-demo page templates since MTK  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 0.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-52) Duplicated component should be selected

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-52 
 
 
 
  Duplicated component should be selected  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 We should offer a way to *add a new component by duplicating an existing component from the same area*. The ability to add a new component by duplicating an existing one is requested on a regular basis. One way to quickly add any type of content is to quickly duplicate an existing element, which has a similar type, is located at a similar location or contains similar content. This is also true for adding new content _on a page_, especially if you build repetitive structures like links, tables, teasers, carousels and the like. In fact, the *marketing team already uses a ["duplicate component" action on the corporate website|^Screenshot of existing implementation.png]*, which we should _at least_ take as a starting point for an implementation in the product, as it has been used in production since Spring 2015.As is the case with duplication of items elsewhere, [duplicating a component should|^2 Duplicate added below and selected.png]:* Add the duplicate *right after the component that was duplicated** *Select the duplicate and make sure it's in view*, so that I can keep working on it right away. Any previously selected element on the page should be deselected before that.We'll [add the "duplicate component" action *between "edit component" and "move component"*|^1 Select and click action.png] to align the order of actions with the one used in other apps. Unfortunately, our current "duplicate" icon lends itself to pages/files too much, but we'll still stick to it to ensure consistency. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (PAGES-49) Offer duplication of an existing component in page editor

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-49 
 
 
 
  Offer duplication of an existing component in page editor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 5.4.4 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-52) Duplicated component should be selected

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-52 
 
 
 
  Duplicated component should be selected  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Affects Versions:
 

 5.4.3 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 

Created:
 

 19/Jan/16 3:34 PM 
 
 
 

Fix Versions:
 

 5.4.4 
 
 
 

Labels:
 

 page-editor quickwin usability ux 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
We should offer a way to add a new component by duplicating an existing component from the same area. The ability to add a new component by duplicating an existing one is requested on a regular basis.  
One way to quickly add any type of content is to quickly duplicate an existing element, which has a similar type, is located at a similar location or contains similar content. This is also true for adding new content on a page, especially if you build repetitive structures like links, tables, teasers, carousels and the like.  
In fact, the marketing team already uses a ["duplicate component" action on the corporate website|^Screenshot of existing 

[magnolia-dev] [JIRA] (PAGES-49) Offer duplication of an existing component in page editor

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-49 
 
 
 
  Offer duplication of an existing component in page editor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 We should offer a way to *add a new component by duplicating an existing component from the same area*. The ability to add a new component by duplicating an existing one is requested on a regular basis. One way to quickly add any type of content is to quickly duplicate an existing element, which has a similar type, is located at a similar location or contains similar content. This is also true for adding new content _on a page_, especially if you build repetitive structures like links, tables, teasers, carousels and the like. In fact, the *marketing team already uses a ["duplicate component" action on the corporate website|^Screenshot of existing implementation.png]*, which we should _at least_ take as a starting point for an implementation in the product, as it has been used in production since Spring 2015.As is the case with duplication of items elsewhere, [duplicating a component should|^2 Duplicate added below and selected.png]:* Add the duplicate *right after the component that was duplicated** *Select the duplicate and make sure it's in view*, so that I can keep working on it right away. Any previously selected element on the page should be deselected before that.  - separated to PAGES-52 We'll [add the "duplicate component" action *between "edit component" and "move component"*|^1 Select and click action.png] to align the order of actions with the one used in other apps. Unfortunately, our current "duplicate" icon lends itself to pages/files too much, but we'll still stick to it to ensure consistency. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3746) Use MessageFormatterUtils instead MessageFormat for message formatting

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3746 
 
 
 
  Use MessageFormatterUtils instead MessageFormat for message formatting  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 13/Jan/16 4:59 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3746) Use MessageFormatterUtils instead MessageFormat for message formatting

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3746 
 
 
 
  Use MessageFormatterUtils instead MessageFormat for message formatting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 MessageFormat throws IllegalArgumentException when formats invalid message pattern. The exception is'n handled in our code. Find please MessageFormat in all modules and use MessageFormatterUtils instead. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (LANG-42) Correct i18n messages to be valid for formatting using MessageFormatterUtils

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Language Bundles /  LANG-42 
 
 
 
  Correct i18n messages to be valid for formatting using MessageFormatterUtils  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Robert Šiška 
 
 
 

Created:
 

 13/Jan/16 5:43 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3701) IllegalArgumentException is thrown when is formatted invalid message pattern

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3701 
 
 
 
  IllegalArgumentException is thrown when is formatted invalid message pattern  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Error deleting new Pages with NON-english user: "Unmatched braces in the IllegalArgumentException is thrown when is formatted invalid message  pattern "  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: