[magnolia-dev] [JIRA] (MGNLCE-38) Add more Log Tools UI tests

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-38  
 
 
  Add more Log Tools UI tests   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Story Points: 
 3 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] (MGNLCE-38) Add more Log Tools UI tests

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-38  
 
 
  Add more Log Tools UI tests   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLGROOVY-161) Groovy createAppScript causes a Definitions app problem

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Groovy Module /  MGNLGROOVY-161  
 
 
  Groovy createAppScript causes a Definitions app problem   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLGROOVY-161) Groovy createAppScript causes a Definitions app problem

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Groovy Module /  MGNLGROOVY-161  
 
 
  Groovy createAppScript causes a Definitions app problem   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Story Points: 
 2  
 
 
Sprint: 
 Basel 95  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLGROOVY-161) Groovy createAppScript causes a Definitions app problem

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Groovy Module /  MGNLGROOVY-161  
 
 
  Groovy createAppScript causes a Definitions app problem   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 2.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 11/May/17 10:47 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 

 

Property [workspace] not found in class [info.magnolia.ui.contentapp.definition.ConfiguredEditorDefinition], property is not assigned
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[magnolia-dev] [JIRA] (MGNLCE-83) The UI tests create screenshots with excessively long filenames

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-83  
 
 
  The UI tests create screenshots with excessively long filenames   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 05/May/17 9:04 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 Which, on some systems, Windows, but also Ubuntu using encfs, can lead to the following exception: 

 

java.lang.AssertionError: IOException while moving screenshot /tmp/screenshot3392632734016174118.png to 0064-By_xpath_contains_class_v_actionbar_contains_class_v_actionbar_section_and_not_aria_hidden_li_class_v_action_text_Edit_page_properties_ : java.io.FileNotFoundException: target/surefire-reports/screenshots/PersonalizationUITest#testStandardPersonalizationWorkflow/0064-By_xpath_contains_class_v_actionbar_contains_class_v_actionbar_section_and_not_aria_hidden_li_class_v_action_text_Edit_page_properties_.png (File name too long)
 

 A total number of characters should be set. Based on my research 142 should be good to fix issues with Ubuntu, however an even shorter name wouldn't cause any harm.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[magnolia-dev] [JIRA] (BUILD-255) Maven version check during release is cumbersome

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Build /  BUILD-255  
 
 
  Maven version check during release is cumbersome   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (BUILD-255) Maven version check during release is cumbersome

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Build /  BUILD-255  
 
 
  Maven version check during release is cumbersome   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 The check might have been useful at some point, but what I'm seeing these days is that it's terribly cumbersome:- it's only done when you're actually performing the release, meaning you can lose a lot of time preparing it, for nothing- the versions required by Maven are not easily installed with either brew or apt[~mmuehlebach] and I think either of the following should be done:- remove the check completely- enforce the check on all release steps- let Jenkins do the release so we don't have to worry about correct local setups (longer story, but worth thinking about) We should also use the occasion to consider, or at least schedule, an update to the parent POMs, so that we get rid of the following pain point: https://git.magnolia-cms.com/projects/BUILD/repos/poms/commits/45e47ca54f903683d886cd3a192d8a412fdc6a41  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   

[magnolia-dev] [JIRA] (MGNLUI-4190) Firefox's CTRL-F is extremely slow

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4190  
 
 
  Firefox's CTRL-F is extremely slow   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 A 5.5 change has slowed down the performance of Firefox's CTRL-F feature dramatically. To reproduce:1. open the Configuration app2. open the modules folder3. scroll till the end4. hit CTRL-FI could reproduce it on Ubuntu as well as on Windows. I couldn't reproduce on 5.4.12-SNAPSHOT. The problem is there but barely noticeable on OS X.It is not an issue on Chrome, though, as  they show  the CTRL-F popup is  an overlay  popup , which doesn't resize all elements on the page. The resizing of all elements seems to be what's slowing Firefox down.  
 

  
 
 
 
 

 
 
 

 
 
 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-4190) Firefox's CTRL-F is extremely slow

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4190  
 
 
  Firefox's CTRL-F is extremely slow   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 A 5.5 change has slowed down the performance of Firefox's CTRL-F feature dramatically. To reproduce:1. open  the  Configuration app2. open the modules folder3. scroll till the end4. hit CTRL-FI could reproduce it on Ubuntu as well as on Windows. I couldn't reproduce on 5.4.12-SNAPSHOT. The problem is there but barely noticeable on OS X.It is not an issue on Chrome, though, as they show an overlay popup, which doesn't resize all elements on the page. The resizing of all elements seems to be what's slowing Firefox down.  
 

  
 
 
 
 

 
 
 

 
 
 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-4190) Firefox's CTRL-F is extremely slow

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4190  
 
 
  Firefox's CTRL-F is extremely slow   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 A  recent  5.5  change has slowed down the performance of Firefox's CTRL-F feature dramatically. To reproduce:1. open Configuration app2. open the modules folder3. scroll till the end4. hit CTRL-FI could reproduce it on Ubuntu as well as on Windows. I couldn't reproduce on 5.4.12-SNAPSHOT. My bet  The problem  is  it comes from some CSS anim property we removed when fixing the tree table jumping issues  there but barely noticeable on OS X .It is not an issue on Chrome, though, as they show an overlay popup, which doesn't resize all elements on the page.  This animation  The resizing of all elements  seems to be what's slowing Firefox down.  
 

  
 
 
 
 

 
 
 

 
 
 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 

[magnolia-dev] [JIRA] (MGNLUI-4190) Firefox's CTRL-F is extremely slow

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4190  
 
 
  Firefox's CTRL-F is extremely slow   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 A recent change has slowed down the performance of Firefox's CTRL-F feature dramatically. To reproduce:1. open Configuration app2. open the modules folder3. scroll till the end4. hit CTRL-FI could reproduce it on Ubuntu as well as on Windows. I couldn't reproduce on 5.4.12-SNAPSHOT.My bet is it comes from some CSS anim property we removed when fixing the tree table jumping issues.It is not an issue on Chrome, though, as they  have  show  an overlay popup, which doesn't resize all elements on the page. This animation seems to be what's slowing Firefox down.  
 

  
 
 
 
 

 
 
 

 
 
 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-4190) Firefox's CTRL-F is extremely slow

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4190  
 
 
  Firefox's CTRL-F is extremely slow   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.3  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 12/Apr/17 11:42 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 A recent change has slowed down the performance of Firefox's CTRL-F feature dramatically. To reproduce: 1. open Configuration app 2. open the modules folder 3. scroll till the end 4. hit CTRL-F I could reproduce it on Ubuntu as well as on Windows. I couldn't reproduce on 5.4.12-SNAPSHOT. My bet is it comes from some CSS anim property we removed when fixing the tree table jumping issues. It is not an issue on Chrome, though, as they have an overlay popup, which doesn't resize all elements on the page. This animation seems to be what's slowing Firefox down.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[magnolia-dev] [JIRA] (MGNLFORUM-296) Thread creation and comment posting fail

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-296  
 
 
  Thread creation and comment posting fail   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 Since MAGNOLIA-5209, it is now impossible to create and save forum threads, nor post comments, as old Content API functions used in Path were removed  (deprecated since 5.2.2) :{code:java}java.lang.NoSuchMethodError: info.magnolia.cms.core.Path.getUniqueLabel(Linfo/magnolia/cms/core/Content;Ljava/lang/String;)Ljava/lang/String;{code}  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLFORUM-296) Thread creation and comment posting fail

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-296  
 
 
  Thread creation and comment posting fail   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 Since MAGNOLIA-5209, it is now impossible to create and save forum threads, nor post comments, as old Content API functions  (deprecated since 5.2.2)  used in Path were removed :{code:java}java.lang.NoSuchMethodError: info.magnolia.cms.core.Path.getUniqueLabel(Linfo/magnolia/cms/core/Content;Ljava/lang/String;)Ljava/lang/String;{code}  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLFORUM-296) Thread creation and comment posting fail

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-296  
 
 
  Thread creation and comment posting fail   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Summary: 
 Thread creation  fails  and comment posting fail  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLFORUM-296) Thread creation fails

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-296  
 
 
  Thread creation fails   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 Since MAGNOLIA-5209, it is now impossible to create and save forum threads,  nor post comments,  as old Content API functions used in Path were removed (deprecated since 5.2.2):{code:java}java.lang.NoSuchMethodError: info.magnolia.cms.core.Path.getUniqueLabel(Linfo/magnolia/cms/core/Content;Ljava/lang/String;)Ljava/lang/String;{code} This is yet another reminder that we should take a decision on the status of the Forum and Commenting modules.  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLFORUM-296) Thread creation fails

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-296  
 
 
  Thread creation fails   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 3.6.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 31/Mar/17 10:17 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 Since MAGNOLIA-5209, it is now impossible to create and save forum threads, as old Content API functions used in Path were removed (deprecated since 5.2.2): 

 

java.lang.NoSuchMethodError: info.magnolia.cms.core.Path.getUniqueLabel(Linfo/magnolia/cms/core/Content;Ljava/lang/String;)Ljava/lang/String;
 

 This is yet another reminder that we should take a decision on the status of the Forum and Commenting modules.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[magnolia-dev] [JIRA] (MGNLCE-78) Manage Jackson version in CE

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-78  
 
 
  Manage Jackson version in CE   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Project: 
 Magnolia  Enterprise  Community  Edition  
 
 
Key: 
 MGNLEE MGNLCE - 484 78  
 

  
 
 
 
 

 
 
 

 
 
 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-121) Image SEO attributes should be helpful

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-121  
 
 
  Image SEO attributes should be helpful   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 20/Mar/17 11:40 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 As discussed in the following PR: https://git.magnolia-cms.com/projects/BUILD/repos/npm-cli/pull-requests/65/overview?commentId=14380 We should help users give meaningful values to those fields, for usability and SEO benefits. We already something similar here in MTK: https://git.magnolia-cms.com/projects/MODULES/repos/templating-essentials/browse/magnolia-templating-kit/src/main/resources/mtk/templates/macros/image.ftl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[magnolia-dev] [JIRA] (LANG-68) Missing "r" in the end of the "Selectionne" button in pages app

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Language Bundles /  LANG-68  
 
 
  Missing "r" in the end of the "Selectionne" button in pages app   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-167) The 'Pragma: no-cache' header is obsolete and causes issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-167  
 
 
  The 'Pragma: no-cache' header is obsolete and causes issues   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 09/Mar/17 11:43 AM  
 
 
Fix Versions: 
 5.6  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 During the investigation done for MGNLUI-4126, Mikaël Geljić and I both arrived to the conclusion that the 'Pragma: no-cache' header is obsolete. It was meant for HTTP 1.0 which has been updated to 1.1 a long, long time ago. See for instance: "I encountered an old smartphone browser that didn't support it [HTTP 1.1] about 9 years ago, but that's the last example I can think of where I'd even heard of an HTTP client that didn't." Source: http://stackoverflow.com/questions/535053/which-webbrowsers-use-http-1-1-by-default (2009) It is also unclear what the header was ever meant for. It would therefore make sense to try to remove it, in order to hopefully avoid more IE / legacy-software issues like the one I mentioned above.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[magnolia-dev] [JIRA] (MGNLUI-3846) Edit bars and actions are missing in IE11 on Windows 10.1

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3846  
 
 
  Edit bars and actions are missing in IE11 on Windows 10.1   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-3846) Edit bars and actions are missing in IE11 on Windows 10.1

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3846  
 
 
  Edit bars and actions are missing in IE11 on Windows 10.1   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Affects Version/s: 
 5.5.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] (MGNLUI-3846) Edit bars and actions are missing in IE11 on Windows 10.1

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm seeing this issue on the demo instance with the new Win10 laptop we have in the office.  
 

  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3846  
 
 
  Edit bars and actions are missing in IE11 on Windows 10.1   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Resolution: 
 Cannot Reproduce  
 
 
Status: 
 Closed 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, 

[magnolia-dev] [JIRA] (MGNLUI-4126) Magnolia AdminCentral not compatible with IE11 over https

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4126  
 
 
  Magnolia AdminCentral not compatible with IE11 over https   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 At the moment Magnolia AdminCentral is not compatible with IE11 over httpsHow to reproduce with IE11 on https://demo.magnolia-cms.com:- Log in- Open Pages App- Edit a page (f.e. sportstation)- reload the page- watch the fonts and icons (which are part of MagnoliaIcons.woff) disappearThe trigger for this issue was a change in styles.css (for all fonts, not just MagnoliaIcons) Before:@font  done in MGNLUI - face { font-family: "MagnoliaIcons"; src: url( 3983 . ./magnolia/fonts/MagnoliaIcons.eot?roba9k);   src: url(../magnolia/fonts/MagnoliaIcons.eot?roba9k#iefix) format("embedded-opentype"), url(../magnolia/fonts/MagnoliaIcons.ttf?roba9k) format("truetype"), url(../magnolia/fonts/MagnoliaIcons.woff?roba9k) format("woff"), url(../magnolia/fonts/MagnoliaIcons.svg?roba9k#MagnoliaIcons) format("svg");   font-weight: normal; font-style: normal;}Now:@font-face { font-family: "MagnoliaIcons"; src: url(../magnolia/fonts/MagnoliaIcons.woff?roba9k) format("woff"); font-weight: normal; font-style: normal;} The reason for the issue is an IE bug with fonts over https, which apparently won't be fixed:https://connect.microsoft.com/IE/feedbackdetail/view/992569/font-face-not-working-with-internet-explorer-and-http-header-pragma-no-cacheThe only workaround at the moment is to remove the "pragma=no-cache" header from the response when loading WOFF files.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[magnolia-dev] [JIRA] (MGNLUI-4126) AdminCentral font disappears with IE11 over HTTPS if Pragma header present

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4126  
 
 
  AdminCentral font disappears with IE11 over HTTPS if Pragma header present   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Summary: 
 Magnolia  AdminCentral  not compatible  font disappears  with IE11 over  https  HTTPS if Pragma header present  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-165) Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reopened as this is what I got when I tried to download cached content in the browser: 

 

2017-02-28 13:25:10,435 INFO  he.browser.rest.endpoint.WhitelistAwareClassLoader: Serialisation is blocked due to the given class: 'java.util.LinkedHashMap' is not whitelisted and currently whitelisted classes are: '[info.magnolia.module.cache.cachekey.DefaultCacheKey]'
 

  
 

  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

[magnolia-dev] [JIRA] (MGNLUI-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Attachment: 
 thumbnail.jpeg  
 

  
 
 
 
 

 
 
 

 
 
 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-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 While testing ARTEDIT-17, I realized that the lightbox / magnifying glass offers a poor UX. This has nothing to do with the Article Editor, as it behaves the same in Assets.Problems encountered:- No max sizes. If an image is big, the lightbox will display it 100%, regardless of the fact that the user's display might only see the top 20%. (see big.png , thumbnail.jpeg for the full picture )- Slow reaction. It takes ~0.1 second to open the lightbox, vs. ~0.2 seconds to close it. This is regardless of image size.- Poor UX. If an image is small enough that a grey background is shown around it, you'd expect that by clicking on the gray background, the lightbox would close itself. It doesn't, you have to click on the image itself.- Animation glitch. If you close an image small enough to show a grey background around it, the grey background will disappear quicker than the image. (see before.png, during,png, after.png)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
   

[magnolia-dev] [JIRA] (MGNLUI-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 While testing ARTEDIT-17, I realized that the lightbox / magnifying glass offers a poor UX. This has nothing to do with the Article Editor, as it behaves the same in Assets.Problems encountered:- No max sizes. If an image is big, the lightbox will display it 100%, regardless of the fact that the user's display might only see the top 20%.  (see big.png) - Slow reaction. It takes ~0.1 second to open the lightbox, vs. ~0.2 seconds to close it. This is regardless of image size.- Poor UX. If an image is small enough that a grey background is shown around it, you'd expect that by clicking on the gray background, the lightbox would close itself. It doesn't, you have to click on the image itself.- Animation glitch. If you close an image small enough to show a grey background around it, the grey background will disappear quicker than the image.  (see before.png, during,png, after.png)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  

[magnolia-dev] [JIRA] (MGNLUI-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Attachment: 
 after.png  
 
 
Attachment: 
 before.png  
 
 
Attachment: 
 big.png  
 
 
Attachment: 
 during.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-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 While testing ARTEDIT-17, I realized that the lightbox / magnifying glass  button  offers a poor UX. This has nothing to do with the Article Editor, as it behaves the same in Assets.Problems encountered:- No max sizes. If an image is big, the lightbox will display it 100%, regardless of the fact that the user's display might only see the top 20%. (see big.png, thumbnail.jpeg for the full picture)- Slow reaction. It takes ~0.1 second to open the lightbox, vs. ~0.2 seconds to close it. This is regardless of image size.- Poor UX. If an image is small enough that a grey background is shown around it, you'd expect that by clicking on the gray background, the lightbox would close itself. It doesn't, you have to click on the image itself.- Animation glitch. If you close an image small enough to show a grey background around it, the grey background will disappear quicker than the image. (see before.png, during,png, after.png)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
  

[magnolia-dev] [JIRA] (MGNLUI-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Attachment: 
 after.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-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Summary: 
 Lightbox UX is  lacking  deficient  
 

  
 
 
 
 

 
 
 

 
 
 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-4154) Lightbox UX is lacking

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is lacking   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Feb/17 11:19 AM  
 
 
Environment: 
 Firefox 51.0.1, OS X 10.11.6  
 
 
Labels: 
 ux  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 While testing ARTEDIT-17, I realized that the lightbox / magnifying glass offers a poor UX. This has nothing to do with the Article Editor, as it behaves the same in Assets. Problems encountered: 
 
No max sizes. If an image is big, the lightbox will display it 100%, regardless of the fact that the user's display might only see the top 20%. 
Slow reaction. It takes ~0.1 second to open the lightbox, vs. ~0.2 seconds to close it. This is regardless of image size. 
Poor UX. If an image is small enough that a grey background is shown around it, you'd expect that by clicking on the gray background, the lightbox would close itself. It doesn't, you have to click on the image itself. 
Animation glitch. If you close an image small enough to show a grey background around it, the grey background will disappear quicker than the image. 
  
 

  

[magnolia-dev] [JIRA] (MGNLUI-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Attachment: 
 after.png  
 
 
Attachment: 
 before.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-4154) Lightbox UX is deficient

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4154  
 
 
  Lightbox UX is deficient   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Attachment: 
 before.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] (MCTP-1) Load content-types and register workspace and node-types

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Types Project /  MCTP-1  
 
 
  Load content-types and register workspace and node-types   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLFORUM-295) 3.6+ status is unclear

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-295  
 
 
  3.6+ status is unclear   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 It is not clear to customers what the situation is with this module in current bundles, see SUPPORT-7226. The goal of this ticket is to try to remove as much config leftovers as possible. Ideally, only the JAR needed by commenting should be visible. Pointers from grooming:* do we only use code from forum, or also config, in commenting?* if we make it a JAR and remove the MD => how can commenting check that it's here or not?* should we release a new commenting major version with the code forum needs included?  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLFORUM-295) 3.6+ status is unclear

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Forum Module /  MGNLFORUM-295  
 
 
  3.6+ status is unclear   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 3.6.1, 3.6  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 09/Feb/17 11:18 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 It is not clear to customers what the situation is with this module in current bundles, see SUPPORT-7226. The goal of this ticket is to try to remove as much config leftovers as possible. Ideally, only the JAR needed by commenting should be visible.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLDEMO-196) Missing i18n key in rename dialog

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-196  
 
 
  Missing i18n key in rename dialog   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-196) Missing i18n key in rename dialog

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-196  
 
 
  Missing i18n key in rename dialog   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (LOGTOOLS-22) Adapt to current Grid style

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Log Tools /  LOGTOOLS-22  
 
 
  Adapt to current Grid style   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 1.0.3  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 files.png, levels.png  
 
 
Created: 
 03/Feb/17 2:05 PM  
 
 
Fix Versions: 
 1.0.4  
 
 
Labels: 
 ux  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 The following commit altered the defaults that the Log Tools stylesheet is built from: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/commits/42b492bdb9a71896337b36795d5b2e4c60abf083 Resulting in a layout that looks untidy/broken, as seen in the screenshots. What is done in the Log Tools stylesheet should therefore be adapted.  
 

  
 
 
 
 

 
 
 

 
 
  

[magnolia-dev] [JIRA] (NPMCLI-78) Small screensize leads to broken progress bar

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-78  
 
 
  Small screensize leads to broken progress bar   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Comment: 
 A new version of the lib we're using for that is apparently coming in the next few days: https://github.com/visionmedia/node-progress/issues/134#issuecomment-275526565Edit: Just tried it. Our problem seems to come from the long Nexus URL. I'd vote for displaying 'Downloading Magnolia' instead of showing the URL. This fixes it.  
 

  
 
 
 
 

 
 
 

 
 
 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-78) Small screensize leads to broken progress bar

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-78  
 
 
  Small screensize leads to broken progress bar   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-207) Secure travel-demo custom cookie

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-207  
 
 
  Secure travel-demo custom cookie   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Project: 
 Magnolia  Personalization  Demo Projects  
 
 
Key: 
 MGNLPN MGNLDEMO - 360 207  
 

  
 
 
 
 

 
 
 

 
 
 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-115) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-115  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Fix Version/s: 
 5.5.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] (MGNLACTIVATION-141) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-141  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Fix Version/s: 
 5.5.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-100) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-100  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Fix 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] (MGNLACTIVATION-141) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-141  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Sprint: 
 Basel 78  
 

  
 
 
 
 

 
 
 

 
 
 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-115) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-115  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Sprint: 
 Basel 78  
 

  
 
 
 
 

 
 
 

 
 
 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-141) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-141  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-115) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-115  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-100) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-100  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Sprint: 
 Basel 77  
 

  
 
 
 
 

 
 
 

 
 
 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-100) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-100  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-100) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-100  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 05/Jan/17 1:24 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-141) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-141  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 05/Jan/17 1:21 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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-115) Upgrade to javax.servlets-api 3.0.1 & sort out issues

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-115  
 
 
  Upgrade to javax.servlets-api 3.0.1 & sort out issues   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 05/Jan/17 1:22 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLTPLSMPL-28) Legacy properties still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Samples /  MGNLTPLSMPL-28  
 
 
  Legacy properties still bootstrapped   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Fix Version/s: 
 5.3.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] (MGNLTPLSMPL-28) Legacy properties still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Samples /  MGNLTPLSMPL-28  
 
 
  Legacy properties still bootstrapped   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLTPLSMPL-28) Legacy properties still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Samples /  MGNLTPLSMPL-28  
 
 
  Legacy properties still bootstrapped   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 {code}dialog: samples:samplesFieldShowRoomfrom jcrat   /modules/samples/dialogs/samplesFieldShowRoomSource data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/numberDoubleSource data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/numberLongSource data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/text2Source data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/text3Source data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLinks/fields/linkSource data processing problem: Property [cols] not found in class [info.magnolia.ui.form.field.definition.OptionGroupFieldDefinition], property is not assigned: /form/tabs/tabSelections/fields/radioSource data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabSwitch/fields/simpleComposite/fields/link{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 

[magnolia-dev] [JIRA] (MGNLTPLSMPL-28) Legacy properties still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Samples /  MGNLTPLSMPL-28  
 
 
  Legacy properties still bootstrapped   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Summary: 
 Remove legacy Legacy  properties  from bootstraps  still bootstrapped  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLTPLSMPL-28) Remove legacy properties from bootstraps

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Samples /  MGNLTPLSMPL-28  
 
 
  Remove legacy properties from bootstraps   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.3.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 21/Dec/16 2:53 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 {dialog: samples:samplesFieldShowRoom from jcr at /modules/samples/dialogs/samplesFieldShowRoom Source data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/numberDouble Source data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/numberLong Source data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/text2 Source data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/text3 Source data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLinks/fields/link Source data processing problem: Property [cols] not found in class [info.magnolia.ui.form.field.definition.OptionGroupFieldDefinition], property is not assigned: /form/tabs/tabSelections/fields/radio Source data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabSwitch/fields/simpleComposite/fields/link}  
 

  
 
 
 
  

[magnolia-dev] [JIRA] (MGNLTPLSMPL-28) Legacy properties still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Samples /  MGNLTPLSMPL-28  
 
 
  Legacy properties still bootstrapped   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 

  
 
 
 
 

 
 { code} dialog: samples:samplesFieldShowRoomfrom jcrat /modules/samples/dialogs/samplesFieldShowRoomSource data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/numberDoubleSource data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/numberLongSource data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/text2Source data processing problem: Property [width] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabEdits/fields/text3Source data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLinks/fields/linkSource data processing problem: Property [cols] not found in class [info.magnolia.ui.form.field.definition.OptionGroupFieldDefinition], property is not assigned: /form/tabs/tabSelections/fields/radioSource data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabSwitch/fields/simpleComposite/fields/link {code }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
  

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

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCE-38) Add more Log Tools UI tests

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-38  
 
 
  Add more Log Tools UI tests   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCE-67) Add an UI test checking that there are no Definitions app problems

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-67  
 
 
  Add an UI test checking that there are no Definitions app problems   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCE-67) Add an UI test checking that there are no Definitions app problems

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-67  
 
 
  Add an UI test checking that there are no Definitions app problems   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 19/Dec/16 8:49 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 While we clear up current problems with BL-381, it would make sense to also to make sure we don't end up in a similar situation years down the line. Once the epic is done, any new addition to the codebase, or any deprecation of class or function, should result in a clear Problems subapp state. An UI test should therefore be written, assessing that there are no problems, so that builds fail otherwise.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

[magnolia-dev] [JIRA] (MGNLUI-4098) 'preview' property from ui-admincentral's import dialog field 'name' causes node2bean problem

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4098 
 
 
 
  'preview' property from ui-admincentral's import dialog field 'name' causes node2bean problem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLPUR-173) Deprecated properties in dialogs/fields still around in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Public User Registration /  MGNLPUR-173 
 
 
 
  Deprecated properties in dialogs/fields still around in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 The  {{extension}}  property was last seen in 2012: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-form/src/main/java/info/magnolia/ui/form/field/definition/LinkFieldDefinition.java?until=ca47b787c284914dad1b550404669d183f698d38=magnolia-ui-model%2Fsrc%2Fmain%2Fjava%2Finfo%2Fmagnolia%2Fui%2Fmodel%2Ffield%2Fdefinition%2FLinkFieldDefinition.javaIt can therefore be removed, in order to fix the following problems:{code}dialog: public-user-registration:loginfrom jcrat /modules/public-user-registration/dialogs/loginSource data processing problem: Property [extension] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/forgottenPasswordPageSource data processing problem: Property [extension] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/registrationPageSource data processing problem: Property [extension] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/targetPage{code}Also, the following old property can go:{code}dialog: public-user-registration:loginfrom jcrat /modules/public-user-registration/dialogs/loginSource data processing problem: Property [height] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/text{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLPUR-173) Deprecated properties in dialogs/fields still around in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Public User Registration /  MGNLPUR-173 
 
 
 
  Deprecated properties in dialogs/fields still around in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (JCRTOOLS-39) Unnecessary subApp action nodes clutter the configuration and cause node2bean problems

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-39 
 
 
 
  Unnecessary subApp action nodes clutter the configuration and cause node2bean problems  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGS-128) Export action extends export from admincentral for no reason

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Sitemap Module /  MGNLGS-128 
 
 
 
  Export action extends export from admincentral for no reason  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGS-128) Export action extends export from admincentral for no reason

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Sitemap Module /  MGNLGS-128 
 
 
 
  Export action extends export from admincentral for no reason  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-200) Old properties still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-200 
 
 
 
  Old properties still bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Fix missing Old  properties  problems  still bootstrapped 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-200) Fix missing properties problems

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-200 
 
 
 
  Fix missing properties problems  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 {code} app: tourCategoriesfrom jcrat /modules/tours/apps/tourCategoriesSource data processing problem: Property [identifier] not found in class [info.magnolia.ui.form.field.definition.MultiValueFieldDefinition], property is not assigned: /subApps/detail/editor/form/tabs/category/fields/relatedUUIDapp: toursfrom jcrat /modules/tours/apps/toursSource data processing problem: Property [rows] not found in class [info.magnolia.ui.form.field.definition.RichTextFieldDefinition], property is not assigned: /subApps/detail/editor/form/tabs/tour/fields/body {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGS-128) Export action extends export from admincentral for no reason

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Sitemap Module /  MGNLGS-128 
 
 
 
  Export action extends export from admincentral for no reason  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 /subApps/browser/actions/export extends /modules/ui-admincentral/apps/configuration/subApps/browser/actions/export. However, as the screenshots show, we probably don't need to do this if, out of three properties, we override one and don't need another (command).{code}app: siteMapsfrom jcrat /modules/google-sitemap/apps/siteMapsSource data processing problem: Property [command] not found in class [info.magnolia.module.googlesitemap.app.actions.ExportSiteMapToXMLActionDefinition], property is not assigned: /subApps/browser/actions/export{code}Also  this  these  old  property  properties  can go:{code}dialog: google-sitemap:components/content/siteComponentTabfrom jcrat /modules/google-sitemap/dialogs/components/content/siteComponentTabSource data processing problem: Property [chooseOnClick] not found in class [info.magnolia.ui.form.field.definition.MultiValueFieldDefinition], property is not assigned: /form/tabs/tabSites/fields/mgnl:googleSiteMapPages app: siteMapsfrom jcrat /modules/google-sitemap/apps/siteMapsSource data processing problem: Property [nodeType] not found in class [info.magnolia.ui.framework.action.OpenEditDialogActionDefinition], property is not assigned: /subApps/browser/actions/editSiteMap {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (MGNLFORM-291) Old properties are still being bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  Old properties are still being bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 The property was last seen in 2012: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-form/src/main/java/info/magnolia/ui/form/field/definition/LinkFieldDefinition.java?until=ca47b787c284914dad1b550404669d183f698d38=magnolia-ui-model%2Fsrc%2Fmain%2Fjava%2Finfo%2Fmagnolia%2Fui%2Fmodel%2Ffield%2Fdefinition%2FLinkFieldDefinition.javaIt can therefore safely be removed from the bootstrap file, in order to fix the following problem:{code}dialog: form:formfrom jcrat /modules/form/dialogs/formSource data processing problem: Property [buttonLabel] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabSubmit/fields/redirect{code}The selected attribute from CheckboxFieldDefinition was removed a long time ago (MGNLUI-1636). However, the property is still around in many bootstrap files. It should be removed.{code}dialog: form:formEditfrom jcrat /modules/form/dialogs/formEditSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/mandatorydialog: form:formSummaryfrom jcrat /modules/form/dialogs/formSummarySource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/onlyLastdialog: form:formNumberfrom jcrat /modules/form/dialogs/formNumberSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /modules/form/dialogs/formEdit/form/tabs/tabMain/fields/mandatorydialog: form:formSelectionfrom jcrat /modules/form/dialogs/formSelectionSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/horizontalSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/mandatorySource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/multipledialog: form:formfrom jcrat /modules/form/dialogs/formSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabConfirmEmail/fields/sendConfirmationSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/displayStepNavigationSource data processing problem: Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabSubmit/fields/trackMaildialog: form:formGroupEditItemfrom jcrat /modules/form/dialogs/formGroupEditItemSource 

[magnolia-dev] [JIRA] (MGNLMAIL-81) Old property still bootstrap

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Mail Module /  MGNLMAIL-81 
 
 
 
  Old property still bootstrap  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Fix missing Old  property  problem  still bootstrap 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORM-291) Old properties are still being bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  Old properties are still being bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 buttonLabel property for LinkFieldDefinition is Old properties are  still  being  bootstrapped 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLMAIL-81) Old property still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Mail Module /  MGNLMAIL-81 
 
 
 
  Old property still bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 Leading to a Definitions app  minor problem. It can be removed : {code}app:  mailfrom jcrat /modules/mail/apps/mailSource data processing problem: Property [selectionType] not found in class [info.magnolia.ui.form.field.definition.OptionGroupFieldDefinition], property is not assigned: /subApps/main/formDefinitions/main/tabs/main/fields/smtpSecurity {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLPUR-173) Deprecated 'extension' property still around in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Public User Registration /  MGNLPUR-173 
 
 
 
  Deprecated 'extension' property still around in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 The property was last seen in 2012: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-form/src/main/java/info/magnolia/ui/form/field/definition/LinkFieldDefinition.java?until=ca47b787c284914dad1b550404669d183f698d38=magnolia-ui-model%2Fsrc%2Fmain%2Fjava%2Finfo%2Fmagnolia%2Fui%2Fmodel%2Ffield%2Fdefinition%2FLinkFieldDefinition.javaIt can therefore be removed, in order to fix the following problems:{code}dialog: public-user-registration:loginfrom jcrat /modules/public-user-registration/dialogs/loginSource data processing problem: Property [extension] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/forgottenPasswordPageSource data processing problem: Property [extension] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/registrationPageSource data processing problem: Property [extension] not found in class [info.magnolia.ui.form.field.definition.LinkFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/targetPage{code} Also, the following old property can go:{code}dialog: public-user-registration:loginfrom jcrat /modules/public-user-registration/dialogs/loginSource data processing problem: Property [height] not found in class [info.magnolia.ui.form.field.definition.TextFieldDefinition], property is not assigned: /form/tabs/tabLogin/fields/text{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLMAIL-81) Old property still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Mail Module /  MGNLMAIL-81 
 
 
 
  Old property still bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Old property still  bootstrap  bootstrapped 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORUM-294) Old and unnecessary properties are present in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Forum Module /  MGNLFORUM-294 
 
 
 
  Old and unnecessary properties are present in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 Leading to Definitions app problems.* 'allowedParameters' was commited in 2007 and can safely be removed.* 'nodeType', 'subAppId' and 'appName' were probably commited by mistake{code}app: forumfrom jcrat /modules/forum/apps/forumSource data processing problem: Property [nodeType] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editForumSource data processing problem: Property [appName] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editForumSource data processing problem: Property [subAppId] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editMessageSource data processing problem: Property [nodeType] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editMessageSource data processing problem: Property [appName] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editMessageSource data processing problem: Property [nodeType] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editThreadSource data processing problem: Property [appName] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/browser/actions/editThreadSource data processing problem: Property [appName] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/moderation/actions/editMessageSource data processing problem: Property [nodeType] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/moderation/actions/editMessageSource data processing problem: Property [subAppId] not found in class [info.magnolia.module.forum.app.action.OpenEditForumItemDialogDefinition], property is not assigned: /subApps/moderation/actions/editMessagetemplate: forum:components/threadViewfrom jcrat /modules/forum/templates/components/threadViewSource data processing problem: Property [allowedParameters] not found in class [info.magnolia.rendering.template.configured.ConfiguredTemplateDefinition], property is not assigned: /template: forum:components/threadReplyfrom jcrat /modules/forum/templates/components/threadReplySource data processing problem: Property [allowedParameters] not found in class [info.magnolia.rendering.template.configured.ConfiguredTemplateDefinition], property is not assigned: /template: forum:components/threadListfrom jcrat /modules/forum/templates/components/threadListSource data processing problem: Property [allowedParameters] not found in class [info.magnolia.rendering.template.configured.ConfiguredTemplateDefinition], property is not 

[magnolia-dev] [JIRA] (MGNLGS-128) Export action extends export from admincentral for no reason

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Sitemap Module /  MGNLGS-128 
 
 
 
  Export action extends export from admincentral for no reason  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 /subApps/browser/actions/export extends /modules/ui-admincentral/apps/configuration/subApps/browser/actions/export. However, as the screenshots show, we probably don't need to do this if, out of three properties, we override one and don't need another (command).{code}app: siteMapsfrom jcrat /modules/google-sitemap/apps/siteMapsSource data processing problem: Property [command] not found in class [info.magnolia.module.googlesitemap.app.actions.ExportSiteMapToXMLActionDefinition], property is not assigned: /subApps/browser/actions/export{code} Also this old property can go:{code}dialog: google-sitemap:components/content/siteComponentTabfrom jcrat /modules/google-sitemap/dialogs/components/content/siteComponentTabSource data processing problem: Property [chooseOnClick] not found in class [info.magnolia.ui.form.field.definition.MultiValueFieldDefinition], property is not assigned: /form/tabs/tabSites/fields/mgnl:googleSiteMapPages{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4100) Name property for ConfiguredFormDialogDefinition is still in bootstraped nodes

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4100 
 
 
 
  Name property for ConfiguredFormDialogDefinition is still in bootstraped nodes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 {code}app: jcr-browserfrom jcrat /modules/jcr-browser-app/apps/jcr-browserSource data processing problem: Property [nodeType] not found in class [info.magnolia.jcrbrowser.app.action.AddContentNodeActionDefinition], property is not assigned: /subApps/browser/actions/addNodeapp: securityfrom jcrat /modules/security-app/apps/securitySource data processing problem: Property [availability] not found in class [info.magnolia.ui.api.availability.ConfiguredAvailabilityDefinition], property is not assigned: /subApps/groups/actions/addFolder/availabilitySource data processing problem: Property [availability] not found in class [info.magnolia.ui.api.availability.ConfiguredAvailabilityDefinition], property is not assigned: /subApps/roles/actions/addFolder/availabilitySource data processing problem: Property [availability] not found in class [info.magnolia.ui.api.availability.ConfiguredAvailabilityDefinition], property is not assigned: /subApps/users/actions/addFolder/availabilityapp: securityfrom jcrat /modules/security-app/apps/securitySource data processing problem: Property [sortable] not found in class [info.magnolia.ui.workbench.list.ListPresenterDefinition], property is not assigned: /subApps/users/workbench/contentViews/list app: securityfrom jcrat /modules/security-app/apps/securitySource data processing problem: Property [sortable] not found in class [info.magnolia.ui.workbench.search.SearchPresenterDefinition], property is not assigned: /subApps/users/workbench/contentViews/search {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-4100) Old properties are still present in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4100 
 
 
 
  Old properties are still present in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Name property for ConfiguredFormDialogDefinition is Old properties are  still  present  in  bootstraped nodes  bootstrap files 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4100) Name property for ConfiguredFormDialogDefinition is still in bootstraped nodes

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4100 
 
 
 
  Name property for ConfiguredFormDialogDefinition is still in bootstraped nodes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 {code}  app: jcr-browserfrom jcrat /modules/jcr-browser-app/apps/jcr-browserSource data processing problem: Property [nodeType] not found in class [info.magnolia.jcrbrowser.app.action.AddContentNodeActionDefinition], property is not assigned: /subApps/browser/actions/addNodeapp: securityfrom jcrat /modules/security-app/apps/securitySource data processing problem: Property [availability] not found in class [info.magnolia.ui.api.availability.ConfiguredAvailabilityDefinition], property is not assigned: /subApps/groups/actions/addFolder/availabilitySource data processing problem: Property [availability] not found in class [info.magnolia.ui.api.availability.ConfiguredAvailabilityDefinition], property is not assigned: /subApps/roles/actions/addFolder/availabilitySource data processing problem: Property [availability] not found in class [info.magnolia.ui.api.availability.ConfiguredAvailabilityDefinition], property is not assigned: /subApps/users/actions/addFolder/availabilityapp: securityfrom jcrat /modules/security-app/apps/securitySource data processing problem: Property [sortable] not found in class [info.magnolia.ui.workbench.list.ListPresenterDefinition], property is not assigned: /subApps/users/workbench/contentViews/list{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (MGNLRSSAGG-211) Old properties are still present in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-211 
 
 
 
  Old properties are still present in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 Leading to the following Definitions app problems: {code}app: rssAggregatorfrom jcrat /modules/rssaggregator/apps/rssAggregatorSource data processing problem: Property [workspace] not found in class [info.magnolia.dam.app.assets.field.translator.AssetCompositeIdKeyTranslator], property is not assigned: /subApps/detail/editor/form/tabs/mainTab/fields/feeds/field/fields/img/identifierToPathConverterapp: rssAggregatorfrom jcrat /modules/rssaggregator/apps/rssAggregatorSource data processing problem: Property [workspace] not found in class [info.magnolia.dam.app.assets.field.translator.AssetCompositeIdKeyTranslator], property is not assigned: /subApps/detail/editor/form/tabs/mainTab/fields/feeds/field/fields/img/identifierToPathConverter{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-211) Old properties are still present in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-211 
 
 
 
  Old properties are still present in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Fix missing property problem Old properties are still present in bootstrap files 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-211) Fix missing property problem

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-211 
 
 
 
  Fix missing property problem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 {code} app: rssAggregatorfrom jcrat  {{ /modules/rssaggregator/apps/rssAggregator }} Source data processing problem: Property  {{ [workspace] }}  not found in class  {{ [info.magnolia.dam.app.assets.field.translator.AssetCompositeIdKeyTranslator] }} , property is not assigned:  {{ /subApps/detail/editor/form/tabs/mainTab/fields/feeds/field/fields/img/identifierToPathConverter app: rssAggregatorfrom jcrat /modules/rssaggregator/apps/rssAggregatorSource data processing problem: Property [workspace] not found in class [info.magnolia.dam.app.assets.field.translator.AssetCompositeIdKeyTranslator], property is not assigned: /subApps/detail/editor/form/tabs/mainTab/fields/feeds/field/fields/img/identifierToPathConverter{code } } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORUM-294) Old and unnecessary properties are present in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Forum Module /  MGNLFORUM-294 
 
 
 
  Old and unnecessary properties are present in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 template Leading to Definitions app problems.* 'allowedParameters' was commited in 2007 and can safely be removed.* 'nodeType', 'subAppId' and 'appName' were probably commited by mistake{code}app : forum :components/threadView from jcrat /modules/forum/ templates apps / components/threadView forum Source data processing problem: Property [ allowedParameters nodeType ] not found in class [info.magnolia. rendering module . template forum . configured app . ConfiguredTemplateDefinition action.OpenEditForumItemDialogDefinition ], property is not assigned: / subApps/browser/actions/editForum  template Source data processing problem :  Property [appName] not found in class [info.magnolia.module.  forum .app.action.OpenEditForumItemDialogDefinition], property is not assigned : components / threadReplyfrom jcrat subApps  / modules browser / actions/editForumSource data processing problem: Property [subAppId] not found in class [info.magnolia.module. forum .app.action.OpenEditForumItemDialogDefinition], property is not assigned: / templates subApps / components browser / threadReply actions/editMessage Source data processing problem: Property [ allowedParameters nodeType ] not found in class [info.magnolia. rendering module . template forum . configured app . ConfiguredTemplateDefinition action.OpenEditForumItemDialogDefinition ], property is not assigned: / subApps/browser/actions/editMessage  template Source data processing problem :  Property [appName] not found in class [info.magnolia.module.  forum .app.action.OpenEditForumItemDialogDefinition], property is not assigned : components / threadListfrom jcrat subApps  / modules browser / actions/editMessageSource data processing problem: Property [nodeType] not found in class [info.magnolia.module. forum .app.action.OpenEditForumItemDialogDefinition], property is not assigned: / templates subApps / components browser / threadList actions/editThread Source data processing problem: Property [ allowedParameters appName ] not found in class [info.magnolia. rendering module . template forum . configured app . ConfiguredTemplateDefinition action.OpenEditForumItemDialogDefinition ], property is not assigned: / subApps/browser/actions/editThread  template Source data processing problem :  Property [appName] not found in class [info.magnolia.module.  forum .app.action.OpenEditForumItemDialogDefinition], property is not assigned : components / threadNewfrom jcrat subApps  / modules moderation / actions/editMessageSource data processing problem: Property [nodeType] not found in class [info.magnolia.module. forum .app.action.OpenEditForumItemDialogDefinition], property is not assigned: / templates subApps / components moderation / threadNew actions/editMessage Source data processing problem: Property [ allowedParameters subAppId ] not found in class [info.magnolia. rendering module . template forum . configured app . ConfiguredTemplateDefinition action.OpenEditForumItemDialogDefinition ], property is not assigned: / subApps/moderation/actions/editMessage  dialog template : forum: forumAdd components/threadView from jcrat /modules/forum/ dialogs 

[magnolia-dev] [JIRA] (MGNLFORUM-294) Old and unnecessary properties are present in bootstrap files

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Forum Module /  MGNLFORUM-294 
 
 
 
  Old and unnecessary properties are present in bootstrap files  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Fix missing Old and unnecessary  properties  problems  are present in bootstrap files 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORM-291) buttonLabel property for LinkFieldDefinition is still in bootstraped nodes

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  buttonLabel property for LinkFieldDefinition is still in bootstraped nodes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 dialog The property was last seen in 2012 :  form  https : formSummaryfrom jcrat  / modules / form/dialogs/formSummarySource data processing problem: Property [selected] not found in class [info git .magnolia -cms . ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: com  / form projects / tabs PLATFORM / tabMain repos / fields ui / onlyLastdialog: form:formHiddenfrom jcrat browse  / modules/form/dialogs/formHiddenSource data processing problem: Property [description] not found in class [info. magnolia . - ui . - form .definition.ConfiguredTabDefinition], property is not assigned:  / form src / tabs main / tabMaindialog: form:formConditionfrom jcrat java  / modules/form/dialogs/formConditionSource data processing problem: Property [saveHandler] not found in class [ info . / magnolia . / ui .dialog.definition.ConfiguredFormDialogDefinition], property is not assigned:  / dialog:  form :formNumberfrom jcrat  / modules field / form definition / dialogs/formNumberSource data processing problem: Property [selected] not found in class [info LinkFieldDefinition . java?until=ca47b787c284914dad1b550404669d183f698d38= magnolia . - ui -model%2Fsrc%2Fmain%2Fjava%2Finfo%2Fmagnolia%2Fui%2Fmodel%2Ffield%2Fdefinition%2FLinkFieldDefinition . form.field.definition.CheckboxFieldDefinition], property is not assigned: /modules/form/dialogs/formEdit/form/tabs/tabMain/fields/mandatory java  dialog: form:formSelection It can therefore safely be removed from  jcrat /modules/form/dialogs/formSelectionSource data processing  the bootstrap file, in order to fix the following  problem:  Property [selected] not found in class [info.magnolia.ui.form.field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/horizontal  dialog: form:formfrom jcrat /modules/form/dialogs/formSource data processing problem: Property [boxType] not found in class [info.magnolia.ui.form.field.definition.CodeFieldDefinition], property is not assigned: /form/tabs/tabConfirmEmail/fields/confirmContentType/fields/ { code }   dialog: form: formGroupEditItem form from jcrat /modules/form/dialogs/ formGroupEditItemSource data processing problem: Property [selected] not found in class [info.magnolia.ui. form .field.definition.CheckboxFieldDefinition], property is not assigned: /form/tabs/tabMain/fields/mandatory  dialog: form:formEditfrom jcrat /modules/form/dialogs/formEdit Source data processing problem: Property [ selected buttonLabel ] not found in class [info.magnolia.ui.form.field.definition. CheckboxFieldDefinition LinkFieldDefinition ], property is not assigned: /form/tabs/ tabMain tabSubmit /fields/ mandatory redirect{code} 
 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLFORM-291) buttonLabel property for LinkFieldDefinition is still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  buttonLabel property for LinkFieldDefinition is still bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Visible to:
 
 Maxime Michel 
 
 
 

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] (MGNLFORM-291) buttonLabel property for LinkFieldDefinition is still in bootstraped nodes

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  buttonLabel property for LinkFieldDefinition is still in bootstraped nodes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 Fix missing properties problems buttonLabel property for LinkFieldDefinition is still in bootstraped nodes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORM-291) buttonLabel property for LinkFieldDefinition is still bootstrapped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  buttonLabel property for LinkFieldDefinition is still bootstrapped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 buttonLabel property for LinkFieldDefinition is still  bootstraped  bootstrapped 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORM-291) buttonLabel property for LinkFieldDefinition is still bootstraped

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-291 
 
 
 
  buttonLabel property for LinkFieldDefinition is still bootstraped  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Summary:
 
 buttonLabel property for LinkFieldDefinition is still  in  bootstraped  nodes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: