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

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Viet Nguyen 
 
 
 

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

2016-10-18 Thread JIRA (on behalf of Michiel Meeuwissen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michiel Meeuwissen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Michiel Meeuwissen 
 
 
 

Affects Version/s:
 
 2.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-10-18 Thread JIRA (on behalf of Michiel Meeuwissen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michiel Meeuwissen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Michiel Meeuwissen 
 
 
 
 
 
 
 
 
 
 It should give a 404, and log nothing.For example the following URL currently cause an error:{code}http://www.vpro.nl/rss/?generatorName=Doesntexist{code}And from our logs:{code}145.58.169.110 - - [18/Oct/2016:15:32:18 +0200] "www.vpro.nl" "GET /rss/?generatorName=Doesntexist HTTP/1.1" 500 4620 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"{code}This does not make sense. The feed simply does not exist and hence should be 404. De stack trace is :{code}java.lang.RuntimeException: javax.servlet.ServletException: Failed to process request at info.magnolia.module.cache.filter.CacheFilter.doFilter(CacheFilter.java:188) at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:59) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at nl.vpro.magnolia.module.vprotemplatingkit.filters.RedirectHttpsFilter.doFilter(RedirectHttpsFilter.java:127) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.cms.i18n.I18nContentSupportFilter.doFilter(I18nContentSupportFilter.java:74) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.cms.filters.RangeSupportFilter.doFilter(RangeSupportFilter.java:84) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.cms.security.BaseSecurityFilter.doFilter(BaseSecurityFilter.java:57) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.multisite.filters.CrossSiteSecurityFilter.doFilter(CrossSiteSecurityFilter.java:104) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:81) at info.magnolia.cms.security.SecurityCallbackFilter.doFilter(SecurityCallbackFilter.java:84) at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:59) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.cms.security.LogoutFilter.doFilter(LogoutFilter.java:94) at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:59) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at info.magnolia.module.site.filters.SiteMergeFilter.doFilter(SiteMergeFilter.java:119) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) at 

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

2016-10-18 Thread JIRA (on behalf of Michiel Meeuwissen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michiel Meeuwissen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Michiel Meeuwissen 
 
 
 
 
 
 
 
 
 
 It should give a 404, and log nothing.For example the following URL currently cause an error:{code}http://www.vpro.nl/rss/?generatorName= Doesnexist Doesntexist {code}And from our logs:{code}145.58.169.110 - - [18/Oct/2016:15:32:18 +0200] "www.vpro.nl" "GET /rss/?generatorName= Doesnexist Doesntexist  HTTP/1.1" 500 4620 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"{code}This does not make sense. The feed simply does not exist and hence should be 404. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-845) Update page JBoss AS configuration

2016-10-18 Thread on behalf of Martin Drápela 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Drápela updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-845 
 
 
 
  Update page JBoss AS configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Drápela 
 
 
 

Assignee:
 
 Martin Drápela 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3845) Richtext disappears from a dialog when focus is lost

2016-10-18 Thread on behalf of Ervín Výstup 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ervín Výstup updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3845 
 
 
 
  Richtext disappears from a dialog when focus is lost  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Support Score:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-47) Use mono-space font for code-related detail messages

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

 
 
 
 
 
 
 
 Definitions app /  CFGUI-47 
 
 
 
  Use mono-space font for code-related detail messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 1.0 
 
 
 
 
 
 
 
 
 
 
 
 

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

2016-10-18 Thread JIRA (on behalf of Michiel Meeuwissen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michiel Meeuwissen created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 3:33 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Michiel Meeuwissen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
It should give a 404, and log nothing. 
For example the following URL currently cause an error: 

 

http://www.vpro.nl/rss/?generatorName=Doesnexist
 

 
And from our logs: 

 

145.58.169.110 - - [18/Oct/2016:15:32:18 +0200] "www.vpro.nl" "GET /rss/?generatorName=Doesnexist HTTP/1.1" 500 4620 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
 

 
This does not make sense. The feed simply does not exist and hence should be 404.

[magnolia-dev] [JIRA] (BUILD-25) Clirr reports should be generated against latest *final* versions

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

 
 
 
 
 
 
 
 Build /  BUILD-25 
 
 
 
  Clirr reports should be generated against latest *final* versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-127) Enable integration tests in other projects

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

 
 
 
 
 
 
 
 Build /  BUILD-127 
 
 
 
  Enable integration tests in other projects  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-27) Provide assembly for modules using appassembler

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

 
 
 
 
 
 
 
 Build /  BUILD-27 
 
 
 
  Provide assembly for modules using appassembler  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-138) Pre-configure dmg/app signing in parent poms

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

 
 
 
 
 
 
 
 Build /  BUILD-138 
 
 
 
  Pre-configure dmg/app signing in parent poms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-63) Use our common header in Javadoc ?

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

 
 
 
 
 
 
 
 Build /  BUILD-63 
 
 
 
  Use our common header in Javadoc ?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-182) Review/remove our Maven plugins

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

 
 
 
 
 
 
 
 Build /  BUILD-182 
 
 
 
  Review/remove our Maven plugins  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-79) Examples in CMS taglib reference unreadable

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

 
 
 
 
 
 
 
 Build /  BUILD-79 
 
 
 
  Examples in CMS taglib reference unreadable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-188) Enforce groupID and certain properties to be set when using parent poms

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

 
 
 
 
 
 
 
 Build /  BUILD-188 
 
 
 
  Enforce groupID and certain properties to be set when using parent poms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-162) Reconsider list of reports generated by Maven

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

 
 
 
 
 
 
 
 Build /  BUILD-162 
 
 
 
  Reconsider list of reports generated by Maven  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-185) Update site plugin to use supplemental models from BUILD-166

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

 
 
 
 
 
 
 
 Build /  BUILD-185 
 
 
 
  Update site plugin to use supplemental models from BUILD-166  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-212) Generate test-jars by default ?

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

 
 
 
 
 
 
 
 Build /  BUILD-212 
 
 
 
  Generate test-jars by default ?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-215) Magnolia Network Agreement (MNA) was renamed Magnolia License Agreement (MLA) "a long time ago"

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

 
 
 
 
 
 
 
 Build /  BUILD-215 
 
 
 
  Magnolia Network Agreement (MNA) was renamed Magnolia License Agreement (MLA) "a long time ago"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-211) When running Clover, compiler still generates code twice, leading to duplicate classes

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

 
 
 
 
 
 
 
 Build /  BUILD-211 
 
 
 
  When running Clover, compiler still generates code twice, leading to duplicate classes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-211) When running Clover, compiler still generates code twice, leading to duplicate classes

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

 
 
 
 
 
 
 
 Build /  BUILD-211 
 
 
 
  When running Clover, compiler still generates code twice, leading to duplicate classes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 Grégory Joseph 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BUILD-215) Magnolia Network Agreement (MNA) was renamed Magnolia License Agreement (MLA) "a long time ago"

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

 
 
 
 
 
 
 
 Build /  BUILD-215 
 
 
 
  Magnolia Network Agreement (MNA) was renamed Magnolia License Agreement (MLA) "a long time ago"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 Build Resources 1.6.3 
 
 
 

Fix Version/s:
 
 POMs 33 
 
 
 

Fix Version/s:
 
 POMs 32 
 
 
 

Fix Version/s:
 
 Build Resources 1.6.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] Re: fileupload into magnolia-tmp-dir

2016-10-18 Thread Christoph Meier (via Magnolia Forums) 
Thanks a lot Benjamin for providing the infos.

We will investigate the issue.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=0c7666f1-0a4b-439b-8efb-dbe287fecd0d



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] Re: fileupload into magnolia-tmp-dir

2016-10-18 Thread Benjamin Brupbacher (via Magnolia Forums) 
i was able to upload files to https://demo.magnolia-cms.com which is 5.4.9… 

here a bit cleaned version of the poc above
[code]
 
[/code]

you can check if the file is in the demo instance with the groovy console:
[code]
myList = Path.getTempDirectory().listFiles()
myList.each{println it}
[/code]

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=0c7666f1-0a4b-439b-8efb-dbe287fecd0d



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-4037) Set range on artifact macros on the DOCS54 space

2016-10-18 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4037 
 
 
 
  Set range on artifact macros on the DOCS54 space  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 1:38 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christoph Meier 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We must make sure the artifact macros on DOCS54 show the highest version on the context of the Magnolia 5.4.x series, but not the really highest version. 
To achieve this - parameter Below version must be set on the artifact macros. 
Note that this concerns the version of ... let's say the Module. These versions must be figured out carefully with the bundle pom files. 
It mainly concerns module pages. 
Example. Module MTK version on the 5.4.x branch must be below 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (MGNLUI-4037) Set range on artifact macros on the DOCS54 space

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4037 
 
 
 
  Set range on artifact macros on the DOCS54 space  
 
 
 
 
 
 
 
 
 

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-853) Set range on artifact macros on the DOCS54 space

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

 
 
 
 
 
 
 
 Documentation /  DOCU-853 
 
 
 
  Set range on artifact macros on the DOCS54 space  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Project:
 
 Magnolia UI Documentation 
 
 
 

Key:
 
 MGNLUI DOCU - 4037 853 
 
 
 

Workflow:
 
 New Product Dev Agile Simplified  Workflow  for Project DOCU 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (CFGUI-46) Fix linking to definitions in overview subapp

2016-10-18 Thread JIRA (on behalf of Cedric Reichenbach) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cedric Reichenbach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-46 
 
 
 
  Fix linking to definitions in overview subapp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cedric Reichenbach 
 
 
 

Assignee:
 
 Cedric Reichenbach 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4033) Double-check that there are no missing i18n keys

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4033 
 
 
 
  Double-check that there are no missing i18n keys  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

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-3883) Dialogs have Cancel and Save Changes actions by default

2016-10-18 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The intention of this ticket is to reduce the required configuration, to make dialogs easier to create and work with. The actions should be supplied by default.  
As implemented one must add the class to the definition, which makes the dialogs more complicated again: 

 
class: info.magnolia.ui.dialog.definition.DefaultActionsDialogDefinition 

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

Change By:
 
 Christopher Zimmermann 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (PAGES-97) Copy & paste action copied node is incorrectly shown as activated

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

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-97 
 
 
 
  Copy & paste action copied node is incorrectly shown as activated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

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-4036) Impossible to set descending ordering within the contentConnector using defaultOrder

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4036 
 
 
 
  Impossible to set descending ordering within the contentConnector using defaultOrder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 According to Tobias Szczepanski in this support ticket we are NOT able to set descending order in our JCR content app list view SUPPORT-6749 due to hard-coded return value of this function:{code}info.magnolia.ui.workbench.container.AbstractJcrContainer.getDefaultOrderBy(String) :: return new OrderBy(property, true);{code} Could it possible to have an easy way for user just to configure content app to apply correct ordering? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4036) Impossible to set descending ordering within the contentConnector using defaultOrder

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4036 
 
 
 
  Impossible to set descending ordering within the contentConnector using defaultOrder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Original Estimate:
 
 1h 
 
 
 

Remaining Estimate:
 
 1h 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Remove adminInterface-legacy module.

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

 
 
 
 
 
 
 
 
This whole configuration from admininterface-legacy has been forgotten: 

 


  FCKEditorSimpleUploadServlet
  info.magnolia.module.fckeditor.servlets.FCKEditorSimpleUploadServlet
  Used for fckeditor inline images and files
  
/.magnolia/fckeditor/upload
  
  

 

 
 
 
 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: 

[magnolia-dev] [JIRA] (MGNLUI-4036) Impossible to set descending ordering within the contentConnector using defaultOrder

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4036 
 
 
 
  Impossible to set descending ordering within the contentConnector using defaultOrder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 11:22 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
According to Tobias Szczepanski in this support ticket we are NOT able to set descending order in our JCR content app list view SUPPORT-6749 due to hard-coded return value of this function: 

 

info.magnolia.ui.workbench.container.AbstractJcrContainer.getDefaultOrderBy(String) :: return new OrderBy(property, true);

[magnolia-dev] [JIRA] (DOCU-849) Downplay STK in 5.5 docs

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

 
 
 
 
 
 
 
 Documentation /  DOCU-849 
 
 
 
  Downplay STK in 5.5 docs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Julie Legendre 
 
 
 
 
 
 
 
 
 
 * Update MTE &  STK  page to become a MTE page * Search and remove mentions of STK throughout doc in most placesNotes from STK meeting 6/6/16 with topher:STK  bundles will still be delivered.Existing customers (pre 5.4) will still have STK based templates and may migrate directly to 5.5  MTE & STK page to become a MTE page that:  - contains a brief paragraph about STK and points people to 5.4 doc for more info- has a sub page re installing stk (since the bundles will still be delivered). Content about installing stk is currently in the "STK changes in 5.4" page. Search and remove mentions of STK throughout doc in most placese.g. :- Remove from DAM+Preview+module- Remove from KonaKart+Connector+module- Filters  - remove stk note, but leave device detection filter paragraphSome modules must be updated before stk mentions can be removed:- leave in IBM+WebSphere+Commerce+Integration+module- leave in Cumulus+DAM+connector 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-851) Postponed from 'Golden leaf' release

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

 
 
 
 
 
 
 
 Documentation /  DOCU-851 
 
 
 
  Postponed from 'Golden leaf' release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Julie Legendre 
 
 
 

Summary:
 
 Postponed from 'Golden  leafs  leaf ' release 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-46) Fix linking to definitions in overview subapp

2016-10-18 Thread JIRA (on behalf of Cedric Reichenbach) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cedric Reichenbach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-46 
 
 
 
  Fix linking to definitions in overview subapp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cedric Reichenbach 
 
 
 
 
 
 
 
 
 
 There's an action  `  {{ OpenDefinitionActionDefinition ` }}  which currently only opens the overview subapp, but doesn't highlight the corresponding definition node.This is related to opening detail locations not working properly in the definitions app in general.Action bar definiton to be re-added afterwards:{noformat}actionbar:  sections:file:  groups:default:  items:- name: showDefinition  availability:rules:  IsFileDefinitionRule:implementationClass: info.magnolia.definitions.app.overview.availability.IsDefinitionRule{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

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] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Comment:
 
 A comment with security level 'Magnolia International' was removed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4035) "Move Before" and "Move After" buttons' states are not handled correctly

2016-10-18 Thread JIRA (on behalf of Hieu Nguyen Duc) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hieu Nguyen Duc updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4035 
 
 
 
  "Move Before" and "Move After" buttons' states are not handled correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hieu Nguyen Duc 
 
 
 
 
 
 
 
 
 
 This issue occurs in Site app and Security app.Steps to reproduce:* Open Site app* Create a folder* Create a content node inside that folder* Select that content node, open Move dialog* Select then deselect on the content node* {{Move Before}} and {{Move After}} will be enabled* Click on any of those buttons=> Expected: The content node is moved to first level.=> Actual: It disappears! We can see it using JCR app.Consider to disable "Move before" and "Move after" in this case like Pages app because this issue doesn't occur in Pages app. *Side note:* The issue doesn't come from "move" dialog epic because it even occurs in 5.4.10 which doesn't have "move" dialog enhancements. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLWORKFLOW-341) Updated JPBM libraries don't work on Weblogic

2016-10-18 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-341 
 
 
 
  Updated JPBM libraries don't work on Weblogic  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sang Ngo Huu 
 
 
 
 
 
 
 
 
 
 After Perhaps after  merging MGNLWORKFLOW-338, the bundle cannot start on Weblogic anymore. There is the log as bellow : . We tried to revert this code, the bundle starts, but it leads to other error. {code}weblogic.management.DeploymentException: CDI deployment failure:org/kie/internal/runtime/manager/RuntimeManagerIdFilter at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:95) at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:43) at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:39) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:754) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45) Truncated. see log file for complete stacktraceCaused By: java.lang.ClassNotFoundException: org.kie.internal.runtime.manager.RuntimeManagerIdFilter at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:1025) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:986) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:83) at weblogic.utils.classloaders.GenericClassLoader.doFindClass(GenericClassLoader.java:607) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:539) Truncated. see log file for complete stacktrace> 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-341) Updated JPBM libraries don't work on Weblogic

2016-10-18 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-341 
 
 
 
  Updated JPBM libraries don't work on Weblogic  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sang Ngo Huu 
 
 
 

Summary:
 
 Updated JPBM libraries  cannot  don't  work on Weblogic 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLWORKFLOW-341) Updated JPBM libraries don't work on Weblogic

2016-10-18 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-341 
 
 
 
  Updated JPBM libraries don't work on Weblogic  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sang Ngo Huu 
 
 
 
 
 
 
 
 
 
 After merging MGNLWORKFLOW-338, the bundle cannot start on Weblogic anymore. There is the log as bellow . We tried to revert the code and it works fine. :   {code}weblogic.management.DeploymentException: CDI deployment failure:org/kie/internal/runtime/manager/RuntimeManagerIdFilter at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:95) at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:43) at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:39) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:754) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45) Truncated. see log file for complete stacktraceCaused By: java.lang.ClassNotFoundException: org.kie.internal.runtime.manager.RuntimeManagerIdFilter at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:1025) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:986) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:83) at weblogic.utils.classloaders.GenericClassLoader.doFindClass(GenericClassLoader.java:607) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:539) Truncated. see log file for complete stacktrace> 

[magnolia-dev] [JIRA] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

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] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 8:29 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Thanks to Nils Breunese for his issue reporting, user would not able to name his Derby workspace name starting with a number as described in SUPPORT-6750. Could you please consider add this information somewhere in our setup or trouble shooting section. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (MGNLWORKFLOW-341) Updated JPBM libraries cannot work on Weblogic

2016-10-18 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-341 
 
 
 
  Updated JPBM libraries cannot work on Weblogic  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5.x 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 8:26 AM 
 
 
 

Environment:
 

 Bundle: magnolia-enterprise-weblogic-webapp-5.5-20161017.072127-321  Weblogic 12.2.1.1.0 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Sang Ngo Huu 
 
 
 
 
 
 
 
 
 
 
After merging 

MGNLWORKFLOW-338
, the bundle cannot start on Weblogic anymore. There is the log as bellow. We tried to revert the code and it works fine. 

 

weblogic.management.DeploymentException: CDI deployment failure:org/kie/internal/runtime/manager/RuntimeManagerIdFilter
	at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:95)
	at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:43)
	at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:39)
	at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:754)
	at