[magnolia-dev] [JIRA] (MGNLUI-4023) SelectField options don't allow to set the same value into two different select options.

2016-09-22 Thread JIRA (on behalf of Richard Gange) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Labels:
 
 support 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLREST-74) PUT request fails if a new node has any subnodes

2016-09-22 Thread JIRA (on behalf of Ondrej Chytil) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ondrej Chytil created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-74 
 
 
 
  PUT request fails if a new node has any subnodes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 9:28 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Ondrej Chytil 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
PUT request works only if adding a single node. If such node contains any subnode(s) the request fails with 400 code. Tested on REST tools and via curl. Sample data: 

 

{
  "name": "test",
  "type": "mgnl:page",
  "path": "/test",
  "properties": [],
  "nodes": [
{
  "name": "test",
  "type": "mgnl:page",
  "path": "/test/test",
  "properties": []
}
  ]
}

[magnolia-dev] [JIRA] (MGNLUI-4023) SelectField options don't allow to set the same value into two different select options.

2016-09-22 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4023) SelectField options don't allow to set the same value into two different select options.

2016-09-22 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SelectFieldFactory.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4023) SelectField options don't allow to set the same value into two different select options.

2016-09-22 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 SelectFieldFactory.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4023) SelectField options don't allow to set the same value into two different select options.

2016-09-22 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4023 
 
 
 
  SelectField options don't allow to set the same value into two different select options.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 SelectFieldFactory.patch 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 22/Sep/16 4:57 PM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

2016-09-22 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 4:34 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Federico Grilli 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
magnolia-travel-demo-component-personalization uses the _javascript_ cookie library https://github.com/js-cookie/js-cookie to set/remove tour type preferences.  Antti would like this mechanism to be documented. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (CFGUI-43) Make use of new querying capabilities of registry

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 

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] (CFGUI-43) Make use of new querying capabilities of registry

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

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] (MGNLCE-57) Update web.xml to Servlet 3.0.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-57 
 
 
 
  Update web.xml to Servlet 3.0.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Saigon 63 
 
 
 

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] (MGNLCE-57) Update web.xml to Servlet 3.0.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-57 
 
 
 
  Update web.xml to Servlet 3.0.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 3:29 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Michael Mühlebach 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-27) Verify row/column/grouping styles

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-27 
 
 
 
  Verify row/column/grouping styles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 63 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLREST-60) RESTEasy dependency should be upgraded to latest.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-60 
 
 
 
  RESTEasy dependency should be upgraded to latest.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Summary:
 
 RESTEasy dependency should be upgraded to  3  latest . 0.18.Final  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-43) Make use of new querying capabilities of registry

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 3:17 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLREST-60) RESTEasy dependency should be upgraded to latest.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-60 
 
 
 
  RESTEasy dependency should be upgraded to latest.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.2 
 
 
 

Fix Version/s:
 
 1.1.x 
 
 
 

Sprint:
 
 Basel 63 
 
 
 

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] (CFGUI-11) Improve display of warnings and errors

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-11 
 
 
 
  Improve display of warnings and errors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 63 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLREST-60) RESTEasy dependency should be upgraded to 3.0.18.Final

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-60 
 
 
 
  RESTEasy dependency should be upgraded to 3.0.18.Final   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Summary:
 
 RESTEasy dependency should be upgraded to 3.0. 10 18 .Final  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLRESTCL-5) RESTEasy client dependency should be upgraded to latest.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 REST Client /  MGNLRESTCL-5 
 
 
 
  RESTEasy client dependency should be upgraded to latest.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Summary:
 
 RESTEasy client dependency should be upgraded to  3  latest . 0.10.Final 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLRESTCL-5) RESTEasy client dependency should be upgraded to latest.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 REST Client /  MGNLRESTCL-5 
 
 
 
  RESTEasy client dependency should be upgraded to latest.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 1.1 
 
 
 

Sprint:
 
 Basel 63 
 
 
 

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] (MGNLADMLEG-69) Add remove tasks.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Admininterface Legacy Module (4.x compatibility) /  MGNLADMLEG-69 
 
 
 
  Add remove tasks.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 
 
 
 
 
 
 
 tbd. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLADMLEG-69) Add remove tasks.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Admininterface Legacy Module (4.x compatibility) /  MGNLADMLEG-69 
 
 
 
  Add remove tasks.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 3:23 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Michael Mühlebach 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLADMLEG-69) Add remove tasks for admin-legacy module.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Admininterface Legacy Module (4.x compatibility) /  MGNLADMLEG-69 
 
 
 
  Add remove tasks for admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Summary:
 
 Add remove tasks  for admin-legacy module . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLADMLEG-69) Add remove tasks.

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Admininterface Legacy Module (4.x compatibility) /  MGNLADMLEG-69 
 
 
 
  Add remove tasks.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 63 
 
 
 

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] (CFGUI-43) Make use of new querying capabilities of registry

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 MAGNOLIA-6084  and related issues added better querying capabilities to the registries. We should make use of them, especially the partial name search (from the name search input field of the definitions app). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-43) Make use of new querying capabilities of registry

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Sprint:
 
 Basel 63 
 
 
 

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] (CFGUI-27) Verify row/column/grouping styles

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-27 
 
 
 
  Verify row/column/grouping styles  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 63 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-186) remove Clicky icon from demo

2016-09-22 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-186 
 
 
 
  remove Clicky icon from demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 63 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-186) remove Clicky icon from demo

2016-09-22 Thread on behalf of Tomáš Gregovský 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-186 
 
 
 
  remove Clicky icon from demo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 demo_clicky.png 
 
 
 

Created:
 

 22/Sep/16 1:31 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
https://demopublic.magnolia-cms.com/ same as travel demo on 5.5-snapshot has entry in Tools > marketing tags which adds clicky snipet in to pages, but first line of this code is no need becasue its only displaying clicky logo on page (see screenshot).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (MGNLCE-55) Integrate app switcher into community edition

2016-09-22 Thread JIRA (on behalf of Ngoc Nguyenthanh) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-55 
 
 
 
  Integrate app switcher into community edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 h6. Forge App Switcher Info- [Git Repository|https://git.magnolia-cms.com/projects/FORGE/repos/appswitcher/browse]- [Jira Project|https://jira.magnolia-cms.com/projects/APPSWITCH]- [Documentation|https://wiki.magnolia-cms.com/display/WIKI/AdminCentral+App+Switcher]h6. Moving App Switcher from Forge to CE- Keep the old version at Forge as it is.- Clone the repository as a new module of {{Modules}} categoryh6. Actions* Request to create Jira, git repository, hudson build for App Switcher module in Modules Git Project Category** Suggested name: {{MGNLAPPSWITCH}}* Integrate the module into CE** Modify the pom file of the module: change parent pom, issuesManagement, scm links, etc. The version should be: 1. 0 3 -SNAPSHOT** Add the dependency of the new module into CE.* Create a follow up ticket to create UI tests if needed.* After new Jira has been created. Create tickets:** Port App Switcher to Java 8** Create Unit testing** Bug fixings, etch6. CONCERNS* Should we keep the old JIRA? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-831) Add a procedure for configuring a cookie trait

2016-09-22 Thread JIRA (on behalf of Antti Hietala) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-831 
 
 
 
  Add a procedure for configuring a cookie trait  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 
 
 
 
 
 
 
 Add a procedure for configuring a cookie trait for personalization. Magnolia provides a trait called {{cookies}} out of the box. We also provide two example cookies: weatherLocality and tourType. Write a procedure for configuring your own cookie name and values.Contents:* *Use case*: Start with an example to orient the reader. What can you use the cookie trait for? A classic case is to store a user preference and use it to personalize content like we do with the tourType cookie. We ask the visitor "Which tour type are you?", store the answer in a cookie, and show featured tours of the visitor's preferred type on the travel home page.* *Benefit*: You don't need to write a new trait class in Java. Configuring new options for the existing cookies trait is enough. * *Location*: Where can you configure a cookie trait? In [Registering a module|https://documentation.magnolia-cms.com/display/DOCS/Creating+custom+traits#Creatingcustomtraits-Registeringatrait] we say that any module can register a trait. But can you configure new options for the cookie trait in any module or do they have to be in {{/modules/personalization-traits/traits/cookies}}? Can you configure options only in JCR or also in YAML? (I don't know the answers to these questions, please test.)* *Example tree*: Configuring the ruleField and valueField are already documented in [Registering a module|https://documentation.magnolia-cms.com/display/DOCS/Creating+custom+traits#Creatingcustomtraits-Registeringatrait]. But the configuration tree does not show what happens under those nodes. Provide an example.* *Any match*: The cookie trait supports the special string {{any}} which matches any cookie value.* *No match*: You can also check for "no match" if you check against a value that would never occur in the cookie. This is a workaround.* *Limitations*: The converterClass {{info.magnolia.personalization.cookie.CookieParameterConverter}} has a bug MGNLPN-333 that prevents you from using more than one cookie in the same  component  variant . Mention this restriction and link to the issue until it is resolved. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

2016-09-22 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

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] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

2016-09-22 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 11:21 AM 
 
 
 

Labels:
 

 support 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Currently the authoring local chosen over the language drop-down is not a part of the location fragment. This has as a consequence, that one can not send the URL of editing the page in a certain non-default language to other editors or via a location call by code. Also the Favorites store and won't react to it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (DOCU-831) Add a procedure for configuring a cookie trait

2016-09-22 Thread JIRA (on behalf of Antti Hietala) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-831 
 
 
 
  Add a procedure for configuring a cookie trait  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 content 
 
 
 

Created:
 

 22/Sep/16 11:19 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antti Hietala 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Add a procedure for configuring a cookie trait for personalization. Magnolia provides a trait called cookies out of the box. We also provide two example cookies: weatherLocality and tourType. Write a procedure for configuring your own cookie name and values. 
Contents: 
 

Use case: Start with an example to orient the reader. What can you use the cookie trait for? A classic case is to store a user preference and use it to personalize content like we do with the tourType cookie. We ask the visitor "Which tour type are you?", store the answer in a cookie, and show featured tours of the visitor's preferred type on the travel home page.
 

Benefit: You don't need to write a new trait class in Java. Configuring new options for the existing

[magnolia-dev] [JIRA] (PROCRES-6) Resource without template causes NPE when trying to edit it

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Resource without template causes NPE when trying to edit it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 When editing a resource that doesn't have a template set an NPE is thrown causing the opening of the app to fail. Additionally the template is not displayed nicely in the processed resources app's column as the formatter of the app doesn't handle them.h4.  To reproduce  Error  # Created a new resource in JCR from resources app (e.g. by hotfixing)# Switch to processed resources app# Try to edit this resource {code}2016-09-22 10:52:38,654 ERROR fo.magnolia.ui.contentapp.browser.BrowserPresenter: An error occurred while executing action [editResource]info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editResource at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeAction(BrowserPresenter.java:347) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeDefaultAction(BrowserPresenter.java:324) at info.magnolia.ui.contentapp.browser.BrowserPresenter.access$300(BrowserPresenter.java:94) at info.magnolia.ui.contentapp.browser.BrowserPresenter$4.onItemDoubleClicked(BrowserPresenter.java:214) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:65) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:43) at info.magnolia.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) at info.magnolia.ui.workbench.AbstractContentPresenterBase.onDoubleClick(AbstractContentPresenterBase.java:152) at info.magnolia.ui.workbench.list.ListViewImpl$3.itemClick(ListViewImpl.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161) at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008) at com.vaadin.ui.Table.handleClickEvent(Table.java:3163) at com.vaadin.ui.Table.changeVariables(Table.java:2952) at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:431) at info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:86) at com.vaadin.server.communication.ServerRpcHandler.changeVariables(ServerRpcHandler.java:637) at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:463) at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:412) at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273) at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:90) at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41) at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414) at 

[magnolia-dev] [JIRA] (MGNLDEMO-185) Update contact page contents

2016-09-22 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-185 
 
 
 
  Update contact page contents  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Assignee:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-42) Make use of Registry and RegistryFacade API

2016-09-22 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-42 
 
 
 
  Make use of Registry and RegistryFacade API   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 22/Sep/16 11:00 AM 
 
 
 

Fix Versions:
 

 1.0 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (PROCRES-6) Resource without template causes NPE when trying to edit it

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Resource without template causes NPE when trying to edit it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 When editing a resource that doesn't have a template set an NPE is thrown causing the opening of the app to fail. Additionally the template is not displayed nicely in the processed resources app's column as the formatter of the app doesn't handle them.h4. To reproduce# Created a new resource in JCR from resources app (e.g. by hotfixing)# Switch to processed resources app# Try to edit this resource{code}2016-09-22 10:52:38,654 ERROR fo.magnolia.ui.contentapp.browser.BrowserPresenter: An error occurred while executing action [editResource]info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editResource at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeAction(BrowserPresenter.java:347) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeDefaultAction(BrowserPresenter.java:324) at info.magnolia.ui.contentapp.browser.BrowserPresenter.access$300(BrowserPresenter.java:94) at info.magnolia.ui.contentapp.browser.BrowserPresenter$4.onItemDoubleClicked(BrowserPresenter.java:214) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:65) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:43) at info.magnolia.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) at info.magnolia.ui.workbench.AbstractContentPresenterBase.onDoubleClick(AbstractContentPresenterBase.java:152) at info.magnolia.ui.workbench.list.ListViewImpl$3.itemClick(ListViewImpl.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161) at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008) at com.vaadin.ui.Table.handleClickEvent(Table.java:3163) at com.vaadin.ui.Table.changeVariables(Table.java:2952) at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:431) at info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:86) at com.vaadin.server.communication.ServerRpcHandler.changeVariables(ServerRpcHandler.java:637) at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:463) at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:412) at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273) at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:90) at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41) at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414) at 

[magnolia-dev] [JIRA] (MGNLDEMO-185) Update contact page contents

2016-09-22 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-185 
 
 
 
  Update contact page contents  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Sprint:
 
 Basel 62 
 
 
 

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] (CFGUI-42) Make use of Registry and RegistryFacade API

2016-09-22 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-42 
 
 
 
  Make use of Registry and RegistryFacade API   
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 https://wiki.magnolia-cms.com/display/DEV/Prepare+Registry+and+RegistryFacade+API%27s+for+the+new+Definitions+app 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-6) Resource without template causes NPE when trying to edit it

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Resource without template causes NPE when trying to edit it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 When editing a resource that doesn't have a template set an NPE is thrown causing the opening of the app to fail. Additionally the template is not displayed nicely in the processed resources app's column as the formatter of the app doesn't handle them.h4. To reproduce# Created a new resource in JCR from resources app (e.g. by hotfixing)# Switch to processed resources app# Try to edit this resource{code}2016-09-22 10:52:38,654 ERROR fo.magnolia.ui.contentapp.browser.BrowserPresenter: An error occurred while executing action [editResource]info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editResource at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeAction(BrowserPresenter.java:347) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeDefaultAction(BrowserPresenter.java:324) at info.magnolia.ui.contentapp.browser.BrowserPresenter.access$300(BrowserPresenter.java:94) at info.magnolia.ui.contentapp.browser.BrowserPresenter$4.onItemDoubleClicked(BrowserPresenter.java:214) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:65) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:43) at info.magnolia.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) at info.magnolia.ui.workbench.AbstractContentPresenterBase.onDoubleClick(AbstractContentPresenterBase.java:152) at info.magnolia.ui.workbench.list.ListViewImpl$3.itemClick(ListViewImpl.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161) at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008) at com.vaadin.ui.Table.handleClickEvent(Table.java:3163) at com.vaadin.ui.Table.changeVariables(Table.java:2952) at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:431) at info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:86) at com.vaadin.server.communication.ServerRpcHandler.changeVariables(ServerRpcHandler.java:637) at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:463) at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:412) at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273) at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:90) at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41) at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414) at 

[magnolia-dev] [JIRA] (PROCRES-6) Resource without template causes NPE when trying to edit it

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Resource without template causes NPE when trying to edit it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Summary:
 
 Disable actions when Resource without  template  is not set  causes NPE when trying to edit it 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-6) Resource without template causes NPE when trying to edit it

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Resource without template causes NPE when trying to edit it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 One may have created When editing  a resource  from resources app and switch to processed resources app, this would  that doesn't  have  all the actions available which is not ideal and only ChangeTemplate action should be available in  a  situation as such  template set an NPE is thrown causing the opening of the app to fail .  Also null  Additionally the  template is not displayed nicely in the processed resources app , 's  column  as the  formatter of the app  should  doesn't  handle  those situations nicer  them . h4. To reproduce# Created a new resource in JCR from resources app (e.g. by hotfixing)# Switch to processed resources app# Try to edit this resource {code}2016-09-22 10:52:38,654 ERROR fo.magnolia.ui.contentapp.browser.BrowserPresenter: An error occurred while executing action [editResource]info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editResource at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeAction(BrowserPresenter.java:347) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeDefaultAction(BrowserPresenter.java:324) at info.magnolia.ui.contentapp.browser.BrowserPresenter.access$300(BrowserPresenter.java:94) at info.magnolia.ui.contentapp.browser.BrowserPresenter$4.onItemDoubleClicked(BrowserPresenter.java:214) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:65) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:43) at info.magnolia.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) at info.magnolia.ui.workbench.AbstractContentPresenterBase.onDoubleClick(AbstractContentPresenterBase.java:152) at info.magnolia.ui.workbench.list.ListViewImpl$3.itemClick(ListViewImpl.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161) at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008) at com.vaadin.ui.Table.handleClickEvent(Table.java:3163) at com.vaadin.ui.Table.changeVariables(Table.java:2952) at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:431) at info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:86) at com.vaadin.server.communication.ServerRpcHandler.changeVariables(ServerRpcHandler.java:637) at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:463) at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:412) at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273) at 

[magnolia-dev] [JIRA] (PROCRES-6) Disable actions when template is not set

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Disable actions when template is not set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 One may have created a resource from resources app and switch to processed resources app, this would have all the actions available which is not ideal and only ChangeTemplate action should be available in a situation as such. Also null template is not displayed nicely in the processed resources app, column formatter of the app should handle those situations nicer. {code}2016-09-22 10:52:38,654 ERROR fo.magnolia.ui.contentapp.browser.BrowserPresenter: An error occurred while executing action [editResource]info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editResource at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeAction(BrowserPresenter.java:347) at info.magnolia.ui.contentapp.browser.BrowserPresenter.executeDefaultAction(BrowserPresenter.java:324) at info.magnolia.ui.contentapp.browser.BrowserPresenter.access$300(BrowserPresenter.java:94) at info.magnolia.ui.contentapp.browser.BrowserPresenter$4.onItemDoubleClicked(BrowserPresenter.java:214) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:65) at info.magnolia.ui.workbench.event.ItemDoubleClickedEvent.dispatch(ItemDoubleClickedEvent.java:43) at info.magnolia.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) at info.magnolia.ui.workbench.AbstractContentPresenterBase.onDoubleClick(AbstractContentPresenterBase.java:152) at info.magnolia.ui.workbench.list.ListViewImpl$3.itemClick(ListViewImpl.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198) at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161) at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008) at com.vaadin.ui.Table.handleClickEvent(Table.java:3163) at com.vaadin.ui.Table.changeVariables(Table.java:2952) at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:431) at info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:86) at com.vaadin.server.communication.ServerRpcHandler.changeVariables(ServerRpcHandler.java:637) at com.vaadin.server.communication.ServerRpcHandler.handleInvocation(ServerRpcHandler.java:463) at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:412) at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273) at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:90) at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41) at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414) at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:365) at 

[magnolia-dev] [JIRA] (PROCRES-6) Disable actions when template is not set

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Disable actions when template is not set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Attachment:
 
 processed-resources-error.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-793) 'Maintain your site' tutorial(s)

2016-09-22 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-793 
 
 
 
  'Maintain your site' tutorial(s)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-826) Magnolia Now GUI text

2016-09-22 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-826 
 
 
 
  Magnolia Now GUI text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Fix Version/s:
 
 5.5. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-830) Explain Activity Logs mnow page

2016-09-22 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julie Legendre updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-830 
 
 
 
  Explain Activity Logs mnow page   
 
 
 
 
 
 
 
 
 

Change By:
 
 Julie Legendre 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-787) Developing with Magnolia Now

2016-09-22 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julie Legendre updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-787 
 
 
 
  Developing with Magnolia Now  
 
 
 
 
 
 
 
 
 

Change By:
 
 Julie Legendre 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PROCRES-4) ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-4 
 
 
 
  ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Previously – before MGNLRES-287 – {{info.magnolia.module.resources.app.ResourceTemplateColumnFormatter}} would not determine the title of templates correctly.It should instead use {{info.magnolia.rendering.template.registry.TemplateDefinitionRegistry}} as in {{info.magnolia.pages.app.column.TemplateColumnFormatter}} and determine the title from the template definition itself  (i18nized title of RenderableDefinition, see {{info . magnolia.rendering.template.RenderableDefinition#getTitle()}}). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-4) ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-4 
 
 
 
  ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Previously – before MGNLRES-287 – {{info.magnolia.module.resources.app.ResourceTemplateColumnFormatter}} would not determine the title of templates correctly. It should  instead  use  templateDefinitonRegistry  TemplateDefinitonRegistry  as in  {{  info.magnolia.pages.app.column.TemplateColumnFormatter }} and determine the title from the template definition itself. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-4) ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-4 
 
 
 
  ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Summary:
 
 ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry  doesn't support yaml templates  to determine title of template 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-4) ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-4 
 
 
 
  ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry to determine title of template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Previously – before MGNLRES-287 – {{info.magnolia.module.resources.app.ResourceTemplateColumnFormatter}} would not determine the title of templates correctly.It should instead use  TemplateDefinitonRegistry  {{info.magnolia.rendering.template.registry.TemplateDefinitionRegistry}}  as in {{info.magnolia.pages.app.column.TemplateColumnFormatter}} and determine the title from the template definition itself. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-7) Publication actions do not use same catalog – versions only created on unpublish

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-7 
 
 
 
  Publication actions do not use same catalog – versions only created on unpublish  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev Philip Mundt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-7) Publication actions do not use same catalog – versions only created on unpublish

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-7 
 
 
 
  Publication actions do not use same catalog – versions only created on unpublish  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Current configuration of the publication actions is flawed:* publish ( not no  catalog defined)* publishRecursively ( not no  catalog defined)* unpublish (versioned catalog)This results in only unpublications creating versions.h5. Proposed solutionUse versioned catalog throughout all publications actions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-7) Publication actions do not use same catalog – versions only created on unpublish

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-7 
 
 
 
  Publication actions do not use same catalog – versions only created on unpublish  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-7) Publication actions do not use same catalog – versions only created on unpublish

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-7 
 
 
 
  Publication actions do not use same catalog – versions only created on unpublish  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 Current configuration of the  publication  actions is flawed:* publish (not catalog defined)* publishRecursively (not catalog defined)* unpublish (versioned catalog)This results in only unpublications creating versions.h5. Proposed solutionUse versioned catalog throughout all publications actions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-7) Publication actions do not use same catalog – versions only created on unpublish

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-7 
 
 
 
  Publication actions do not use same catalog – versions only created on unpublish  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 

Created:
 

 22/Sep/16 9:15 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 
Current configuration of the actions is flawed: 
 

publish (not catalog defined)
 

publishRecursively (not catalog defined)
 

unpublish (versioned catalog)
 
 
This results in only unpublications creating versions. 
Proposed solution 
Use versioned catalog throughout all publications actions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (PROCRES-4) ResourceTemplateColumnFormatter doesn't support yaml templates

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-4 
 
 
 
  ResourceTemplateColumnFormatter doesn't support yaml templates  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Resolution:
 
 Outdated 
 
 
 

Status:
 
 Closed Reopened 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PROCRES-4) ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry doesn't support yaml templates

2016-09-22 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-4 
 
 
 
  ResourceTemplateColumnFormatter should use TemplateDefinitionRegistry doesn't support yaml templates  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Summary:
 
 ResourceTemplateColumnFormatter  should use TemplateDefinitionRegistry  doesn't support yaml templates 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: