[magnolia-dev] [JIRA] (MGNLUI-4220) LinkFieldFactory used in a SwitchableField leads to NullPointer

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4220  
 
 
  LinkFieldFactory used in a SwitchableField leads to NullPointer   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Project: 
 Magnolia  UI  
 
 
Key: 
 MAGNOLIA MGNLUI - 7048 4220  
 
 
Affects Version/s: 
 5.5.3  
 
 
Affects Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3213) SwitchableField containing MultiValueField throws IllegalArgumentException on commit

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3213  
 
 
  SwitchableField containing MultiValueField throws IllegalArgumentException on commit   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 SwitchableField containing MultiValueField throws IllegalArgumentException  on commit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3213) SwitchableField containing MultiValueField throws IllegalArgumentException

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3213  
 
 
  SwitchableField containing MultiValueField throws IllegalArgumentException   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 SwitchableField containing MultiValueField throws  Exception  IllegalArgumentException  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (BLOSSOM-242) Make it possible to configure dialog presenter class

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Blossom Module /  BLOSSOM-242  
 
 
  Make it possible to configure dialog presenter class   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 # BlossomFormDialogPresenter class is hardcoded in BlossomDialogDefinitionProvider and in DefaultDialogCreator. Since we need them to be able to override some of the functionality, we need to make class configurable.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4217) Regex- and digitsOnly-Validator throw NullPointer (Blossom)

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4217  
 
 
  Regex- and digitsOnly-Validator throw NullPointer (Blossom)   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Project: 
 Magnolia  UI  
 
 
Key: 
 MAGNOLIA MGNLUI - 7051 4217  
 
 
Affects Version/s: 
 5.5.3  
 
 
Affects Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (SUGGEST-85) After upgrade completes there should be a confirmation in the log

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-85  
 
 
  After upgrade completes there should be a confirmation in the log   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 Currently when new modules need to be installed you see:{noformat}** ** Magnolia needs module updates or installs, point your browser to your Magnolia instance and confirm ! ** **{noformat}But there is never any confirmation that upgrade completed. Not such a big deal a lot of the time but when there are issues with upgrade it would be nice to have a confirmation.  Some examples SUPPORT-7577 and SUPPORT-7489. Here there is a very long running renaming task. It can cause the server to be in a locked state after the upgrade.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   

[magnolia-dev] [JIRA] (SUGGEST-85) After upgrade completes there should be a confirmation in the log

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-85  
 
 
  After upgrade completes there should be a confirmation in the log   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 Currently when new modules need to be installed you see:{noformat}** ** Magnolia needs module updates or installs, point your browser to your Magnolia instance and confirm ! ** **{noformat}But there is never any confirmation that upgrade completed. Not such a big deal a lot of the time but when there are issues with upgrade it would be nice to have a confirmation.     Some examples SUPPORT-7577 and SUPPORT-7489. Here there is a very long running renaming task. It can cause the server to be in a locked state after the upgrade.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   

[magnolia-dev] [JIRA] (SUGGEST-85) After upgrade completes there should be a confirmation in the log

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-85  
 
 
  After upgrade completes there should be a confirmation in the log   
 

  
 
 
 
 

 
Issue Type: 
  Support Request  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/May/17 9:04 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 Currently when new modules need to be installed you see: 

 
*
*   *
* Magnolia needs module updates or installs, point your browser to your Magnolia instance and confirm ! *
*   *
*
 

 But there is never any confirmation that upgrade completed. Not such a big deal a lot of the time but when there are issues with upgrade it would be nice to have a confirmation.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

[magnolia-dev] [JIRA] (MGNLUI-4211) Vaadin HEARTBEAT causes null pointer exception on WildFly 8

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4211  
 
 
  Vaadin HEARTBEAT causes null pointer exception on WildFly 8   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Labels: 
 WildFly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4211) Vaadin HEARTBEAT causes null pointer exception on WildFly 8

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4211  
 
 
  Vaadin HEARTBEAT causes null pointer exception on WildFly 8   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5, 5.4  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 18/May/17 3:06 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For 

[magnolia-dev] [JIRA] (MGNLUI-4211) Vaadin HEARTBEAT causes null pointer exception on WildFly 8

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4211  
 
 
  Vaadin HEARTBEAT causes null pointer exception on WildFly 8   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Assignee: 
 Richard Gange  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4211) Vaadin HEARTBEAT causes null pointer exception on WildFly 8

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4211  
 
 
  Vaadin HEARTBEAT causes null pointer exception on WildFly 8   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 Symptom:{noformat}15:04:23,830 ERROR [io.undertow.request] (default task-12) UT005023: Exception handling request to /enterprise-55/.magnolia/admincentral/HEARTBEAT/: java.lang.NullPointerException at io.undertow.servlet.spec.HttpServletResponseImpl.setContentType(HttpServletResponseImpl.java:366) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at javax.servlet.ServletResponseWrapper.setContentType(ServletResponseWrapper.java:179) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at info.magnolia.debug.LoggingResponse.setContentType(LoggingResponse.java:99) [magnolia-core-5.5.4.jar:] at javax.servlet.ServletResponseWrapper.setContentType(ServletResponseWrapper.java:179) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at info.magnolia.module.cache.filter.CacheResponseWrapper.replayHeadersAndStatus(CacheResponseWrapper.java:377) [magnolia-cache-core-5.5.4.jar:] at info.magnolia.module.cache.filter.GZipFilter.doFilter(GZipFilter.java:85) [magnolia-cache-core-5.5.4.jar:] at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:59) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:81) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.security.auth.login.LoginFilter.doFilter(LoginFilter.java:127) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) [magnolia-core-5.5.4.jar:] at info.magnolia.enterprise.registration.RegistrationFilter.doFilter(RegistrationFilter.java:64) [magnolia-module-enterprise-5.5.4.jar:] at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:85) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:81) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:81) [magnolia-core-5.5.4.jar:] at info.magnolia.personalization.preview.filter.PreviewFilter.doFilter(PreviewFilter.java:92) [magnolia-personalization-preview-app-1.4.4.jar:] at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:59) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:79) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:81) [magnolia-core-5.5.4.jar:] at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:81) [magnolia-core-5.5.4.jar:] at 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-305) A user should be able to unassign a task

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-305  
 
 
  A user should be able to unassign a task   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 As a publisher I A user  should be able to  take control of an "InProgress" workitem  unassign a task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-305) A user should be able to unassign a task

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-305  
 
 
  A user should be able to unassign a task   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 It If a user takes control of a task they  should be  possible for some users (appropriate role)  able  to  reassign an "InProgress" workitem  release the task without taking any action of approve/reject/abort .   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-305) A user should be able to unassign a task

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-305  
 
 
  A user should be able to unassign a task   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Comment: 
 The preferred way to handle this is:* Superuser aborts the in-progress workflow.* A user recreates a similar request.* A user takes control of the new item.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-305) A user should be able to unassign a task

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-305  
 
 
  A user should be able to unassign a task   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Resolution: 
 Won't Do  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-695) Update page "JBoss AS configuration" with latest comments

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-695  
 
 
  Update page "JBoss AS configuration" with latest comments   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Assignee: 
 Richard Gange  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-2652) Serialisation issue with AdmincentralVaadinServlet causes error exceptions in JBoss WildFly

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-2652  
 
 
  Serialisation issue with AdmincentralVaadinServlet causes error exceptions in JBoss WildFly   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Assignee: 
 Richard Gange  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-1017) Update JBoss deployment instructions

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1017  
 
 
  Update JBoss deployment instructions   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Comment: 
 Wfly 11.0 Alpha1 - RESTEasy 3.0.21.Final  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLREST-86) RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-86  
 
 
  RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Component/s: 
 integration  
 
 
Component/s: 
 services  
 
 
Component/s: 
 tools  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLREST-86) RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-86  
 
 
  RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Affects Version/s: 
 1.2.1  
 
 
Affects Version/s: 
 1.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-1017) Update JBoss deployment instructions

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1017  
 
 
  Update JBoss deployment instructions   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 Update JBoss deployment instructions  to cover all certified versions  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-1017) Update JBoss deployment instructions to cover all certified versions

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1017  
 
 
  Update JBoss deployment instructions to cover all certified versions   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Richard Gange  
 
 
Created: 
 10/May/17 7:38 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 Currently in the certified stack we list: Wildfly 8 and later JBoss EAP 6.3.3 and later The documentation only talks about Wildfly 10.  Recently we had an inquiry about our JBoss support. 
 
This is the actual stack: 
 
Linux RedHat 
JBoss EAP 6.4 
Magnolia 5.4.10 
 
Magnolia certify the JBoss but in the configuration page there is a step for override the native version of RestEasy. 
We don’t want to make the override of RestEasy because if they make the override they lose the support from RedHat/JBoss. 
If we make the upgrade to JBoss EAP 7.0 does the override of RestEasy is necessary? Does Magnolia in future could certificate JBoss without the override the native libraries? 
The position is: Magnolia certify JBoss then Magnolia must work without any override of libraries on JBoss.
 The goal here is to create a chart for a few popular versions of JBoss.   
 

  
 
 
 
 

[magnolia-dev] [JIRA] (SUGGEST-82) Create an easier way to reset the superuser

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-82  
 
 
  Create an easier way to reset the superuser   
 

  
 
 
 
 

 
Issue Type: 
  Support Request  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 03/May/17 2:19 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 It would be nice if there was a property or switch that can be set at startup to reset the superuser. Perhaps with a parameter.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

[magnolia-dev] [JIRA] (CNTCTSAPP-101) ContactPreviewComponent throws null pointer

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Contacts Module /  CNTCTSAPP-101  
 
 
  ContactPreviewComponent throws null pointer
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Apr/17 3:31 PM  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 Configure the class on a field: 

 

name: contact
class: info.magnolia.ui.form.field.definition.LinkFieldDefinition
targetWorkspace: contacts
appName: contacts
label: Select a contact
contentPreviewDefinition:
  contentPreviewClass: info.magnolia.contacts.app.field.component.ContactPreviewComponent
 

 Try to create a new node. Observe the error: 

 
com.vaadin.event.ListenerMethod$MethodException: Invocation of method valueChange in info.magnolia.ui.form.field.factory.LinkFieldFactory$$Lambda$57/1011703373 failed.
	at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:531)
	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.AbstractField.fireValueChange(AbstractField.java:1163)
	at com.vaadin.ui.AbstractField.setPropertyDataSource(AbstractField.java:690)
	at info.magnolia.ui.form.field.LinkField.setPropertyDataSource(LinkField.java:157)
	at info.magnolia.ui.form.field.factory.AbstractFieldFactory.setPropertyDataSourceAndDefaultValue(AbstractFieldFactory.java:198)
	at info.magnolia.ui.form.field.factory.AbstractFieldFactory.createField(AbstractFieldFactory.java:161)
	at info.magnolia.ui.dialog.formdialog.FormBuilder.createField(FormBuilder.java:231)
	at info.magnolia.ui.dialog.formdialog.FormPresenterImpl.createField(FormPresenterImpl.java:267)
	at 

[magnolia-dev] [JIRA] (MGNLUI-4195) File Upload cannot set as mandatory

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4195  
 
 
  File Upload cannot set as mandatory   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Fix Version/s: 
 5.5.4  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4195) File Upload cannot set as mandatory

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4195  
 
 
  File Upload cannot set as mandatory   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Project: 
 Magnolia  Form Module  UI  
 
 
Key: 
 MGNLFORM MGNLUI - 265 4195  
 
 
Issue Type: 
 Improvement Bug  
 
 
Component/s: 
 forms  
 
 
Component/s: 
 field  
 
 
Component/s: 
 validation  
 
 
Affects Version/s: 
 5.5.3  
 
 
Affects Version/s: 
 2.2.13  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[magnolia-dev] [JIRA] (DOCU-952) Update "REST API"

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-952  
 
 
  Update "REST API"   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Attachment: 
 create-page-test-5.5.3.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-426) Update webdav documentation to reflect current workspaces

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-426  
 
 
  Update webdav documentation to reflect current workspaces   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 Update webdav documentation to  meet new module features  reflect current workspaces  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-426) Update webdav documentation to reflect current workspaces

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-426  
 
 
  Update webdav documentation to reflect current workspaces   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 For instance we mention just mapping to templates, while the module already exposes also  dms  dam  workspaces.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-426) Update webdav documentation to meet new module features

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-426  
 
 
  Update webdav documentation to meet new module features   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Assignee: 
 Richard Gange  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-978) Provide better explication about how cache works, especially which values to expect in memcached

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-978  
 
 
  Provide better explication about how cache works, especially which values to expect in memcached   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Assignee: 
 Roman Kovařík  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-170) The TTL for uncacheable entries should be 0 and not -1

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-170  
 
 
  The TTL for uncacheable entries should be 0 and not -1
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 using '-1' to cache forever even for binary is not correct and inline with memcached specs, you have to use 60*60*24*30 instead  (this is the only thing which brakes compatibility with 'TEXT' protocol at the moment)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-170) The TTL for uncacheable entries should be 0 and not -1

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-170  
 
 
  The TTL for uncacheable entries should be 0 and not -1
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-171) TEXT protocol support broken

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-171  
 
 
  TEXT protocol support broken   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 Caused by MGNLCACHE-170  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-171) TEXT protocol support broken

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-171  
 
 
  TEXT protocol support broken   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Affects Version/s: 
 5.5.2  
 
 
Affects Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-171) TEXT protocol support broken

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-171  
 
 
  TEXT protocol support broken   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Support Score: 
  
 
 
Affects Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-171) Add TEXT protocol support

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-171  
 
 
  Add TEXT protocol support   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLCACHE-171) TEXT protocol support broken

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-171  
 
 
  TEXT protocol support broken   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 Add  TEXT protocol support  broken  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-973) "Storing and serving localized content" needs updating

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-973  
 
 
  "Storing and serving localized content" needs updating   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 20/Mar/17 9:40 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 For the page Language+configuration: The section "Storing and serving localized content" refers to a deprecated class info.magnolia.multisite.i18n.MultiSiteI18nContentSupport  

 

/**
 * Delegates to the i18n support configured in the current site definition.
 *
 * @deprecated since 1.2.1 - use {@link info.magnolia.module.site.i18n.SiteI18nContentSupport} instead.
 */
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[magnolia-dev] [JIRA] (MGNLRESTCL-24) Cannot install Rest Client app and Rest Tools app togther

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 REST Client /  MGNLRESTCL-24  
 
 
  Cannot install Rest Client app and Rest Tools app togther
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 1.1.1  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 library-issue.png  
 
 
Components: 
 app  
 
 
Created: 
 06/Mar/17 5:07 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 The message received is: 

 
500 : Could not initialize class com.fasterxml.jackson.databind.SerializationConfig http://localhost:8080/enterprise-pro-webapp/.rest/swagger.json
 

 See also http://stackoverflow.com/questions/39419160/jackson-databind-classpath-issue  
 

  
 
 
 
 

 
 
 

 
 
 

[magnolia-dev] [JIRA] (MGNLRESTCL-24) Cannot install Rest Client app and Rest Tools app together

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 REST Client /  MGNLRESTCL-24  
 
 
  Cannot install Rest Client app and Rest Tools app together
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 Cannot install Rest Client app and Rest Tools app  togther  together
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3877) CKeditor image plugin: "Browse Server" for the link property of an image opens assets chooser instead of pages chooser

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3877  
 
 
  CKeditor image plugin: "Browse Server" for the link property of an image opens assets chooser instead of pages chooser   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3877) CKeditor image plugin: "Browse Server" for the link property of an image opens assets chooser instead of pages chooser

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3877  
 
 
  CKeditor image plugin: "Browse Server" for the link property of an image opens assets chooser instead of pages chooser   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Environment: 
 Windows 7, should not matter  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3877) CKeditor image plugin: "Browse Server" for the link property of an image opens assets chooser instead of pages chooser

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3877  
 
 
  CKeditor image plugin: "Browse Server" for the link property of an image opens assets chooser instead of pages chooser   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Affects Version/s: 
 5.5.2  
 
 
Affects Version/s: 
 5.4.6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4153) {{DateColumnFormatter}} cannot handle DST correctly

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4153  
 
 
  {{DateColumnFormatter}} cannot handle DST correctly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workbench  
 
 
Created: 
 22/Feb/17 4:33 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 DateColumnFormatter does not han  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[magnolia-dev] [JIRA] (MGNLUI-4153) DateColumnFormatter cannot handle DST correctly

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4153  
 
 
  DateColumnFormatter cannot handle DST correctly   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Summary: 
 {{ DateColumnFormatter }}  cannot handle DST correctly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4153) DateColumnFormatter cannot handle DST correctly

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4153  
 
 
  DateColumnFormatter cannot handle DST correctly   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 {{ The DateFieldFactory, which is used to create the datepicker, defaults correctly against the SERVER-timezone, if no timezone is specified: (TimeZone is null in my case.)The DateColumnFormatter }}  on the other hand, defaults against the BROWSER timezone, when there is no TimeZone specified. ==> It's just an offset, and  does not  han  bring DST in count.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLAPPSW-3) App Switcher gets stuck in Windows

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia App Switcher /  MGNLAPPSW-3  
 
 
  App Switcher gets stuck in Windows   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Affects Version/s: 
 1.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLAPPSW-3) App Switcher gets stuck in Windows

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia App Switcher /  MGNLAPPSW-3  
 
 
  App Switcher gets stuck in Windows   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 If you pull up the app switcher with Alt+Shift, you are unable to select an app  and/  or remove the switcher from the screen. It's stuck on the screen. You can only toggle between the apps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLAPPSW-3) App Switcher gets stuck in Windows

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia App Switcher /  MGNLAPPSW-3  
 
 
  App Switcher gets stuck in Windows   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Labels: 
 windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLAPPSW-3) App Switcher gets stuck in Windows

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia App Switcher /  MGNLAPPSW-3  
 
 
  App Switcher gets stuck in Windows   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLAPPSW-3) App Switcher gets stuck in Windows

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia App Switcher /  MGNLAPPSW-3  
 
 
  App Switcher gets stuck in Windows   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 
 
Created: 
 13/Feb/17 3:55 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 If you pull up the app switcher with Alt+Shift, you are unable to select an app or remove the switcher from the screen. It's stuck on the screen. You can only toggle between the apps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
  

[magnolia-dev] [JIRA] (SUGGEST-68) Deprecate the property "type" for area configuration

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-68  
 
 
  Deprecate the property "type" for area configuration   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 The area "type" has become useless information. All areas can be assumed to hold components. If a template script is configured then it will either render components or it will not. This is will determine if the area is pure script or not. The single type of area can be done using maxComponents set to one.noComponent: if (available components configured) truelist: always assume this typesingle: if (max components == 1) true  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (SUGGEST-68) Deprecate the property "type" for area configuration

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-68  
 
 
  Deprecate the property "type" for area configuration   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 

  
 
 
 
 

 
 The area "type" has become useless information. All areas can be assumed to hold components. If a template script is configured then it will either render components or it will not. This is will determine if the area is pure script or not. The single type of area can be done using maxComponents set to one. noComponent: if (available components  not  configured) truelist: always assume this typesingle: if (max components == 1) true  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4116) View scrolls back to the beginning upon browsing with Chrome

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4116  
 
 
  View scrolls back to the beginning upon browsing with Chrome   
 

  
 
 
 
 

 
Change By: 
 Richard Gange  
 
 
Affects Version/s: 
 5.3.17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (SUGGEST-68) Deprecate the property "type" for area configuration

[JIRA (on behalf of Richard Gange)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-68  
 
 
  Deprecate the property "type" for area configuration   
 

  
 
 
 
 

 
Issue Type: 
  Support Request  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 07/Jan/17 12:31 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Richard Gange  
 

  
 
 
 
 

 
 The area "type" has become useless information. All areas can be assumed to hold components. If a template script is configured then it will either render components or it will not. This is will determine if the area is pure script or not. The single type of area can be done using maxComponents set to one.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCACHE-151) Requests initiated with ERROR dispatcher do not work with CacheFilter

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-151 
 
 
 
  Requests initiated with ERROR dispatcher do not work with CacheFilter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.5.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] (MGNLCACHE-151) Requests initiated with ERROR dispatcher do not work with CacheFilter

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-151 
 
 
 
  Requests initiated with ERROR dispatcher do not work with CacheFilter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

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] (MTE-96) searchfn fails when configuring / as the startPath

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-96 
 
 
 
  searchfn fails when configuring / as the startPath  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 11/Nov/16 9:52 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 
See comment on https://documentation.magnolia-cms.com/display/DOCS/searchfn 
 
We had some issues getting page results to be returned from the Search Pages method in 5.4.4 using the example "Absolute path in the website workspace such as "/" or "/travel"." We tried "/" but the code seems to interpret this as the query "//%" which returns no results. We ended up having to configure it to use "%" which then gets interpreted as searching the path "/%"
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4029) Provide way of automatically opening subapps

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4029 
 
 
 
  Provide way of automatically opening subapps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Component/s:
 
 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] (MGNLREST-78) PUT request fails to create properties

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-78 
 
 
 
  PUT request fails to create properties  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 PUT request  works only if adding a single node. If such node contains any subnode(s) the request  fails  with 400 code.  to create properties  Tested on REST tools and via curl. Sample data:{code}{  "name": "test",  "type": "mgnl:page",  "path": "/test",  "properties": [ ] {  "name": "title" ,  " type": "String",  "multiple": false},  " nodes": [{  "name": "test",  "type": "mgnl:page",  "path": "/test/test",  "properties": []}  ]}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLREST-78) PUT request fails to create properties

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-78 
 
 
 
  PUT request fails to create properties  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 29/Sep/16 7:30 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

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] (PAGES-94) move page action doesn't check for possible 'same name' siblings

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-94 
 
 
 
  move page action doesn't check for possible 'same name' siblings   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Summary:
 
 It is move page action doesn't check for  possible  to create  'same name' siblings  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-94) It is possible to create 'same name' siblings

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-94 
 
 
 
  It is possible to create 'same name' siblings   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Project:
 
 Magnolia  UI  pages module 
 
 
 

Key:
 
 MGNLUI PAGES - 4024 94 
 
 
 

Security:
 
 Public 
 
 
 

Affects Version/s:
 
 5.4.9 
 
 
 

Affects Version/s:
 
 5.4.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (PAGES-94) move page action doesn't check for possible 'same name' siblings

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-94 
 
 
 
  move page action doesn't check for possible 'same name' siblings   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

[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] (MGNLUI-4014) Investigate into corner cases: Wrong timezone calculation in DateFieldFactory

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4014 
 
 
 
  Investigate into corner cases: Wrong timezone calculation in DateFieldFactory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

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] (MGNLUI-4014) Investigate into corner cases: Wrong timezone calculation in DateFieldFactory

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4014 
 
 
 
  Investigate into corner cases: Wrong timezone calculation in DateFieldFactory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Affects Version/s:
 
 5.4.7 
 
 
 

Affects Version/s:
 
 5.4.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4014) Investigate into corner cases: Wrong timezone calculation in DateFieldFactory

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4014 
 
 
 
  Investigate into corner cases: Wrong timezone calculation in DateFieldFactory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.4.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4005) users timezone permission delta task starts at root

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4005 
 
 
 
  users timezone permission delta task starts at root  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Priority:
 
 Neutral Minor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4005) users timezone permission delta task starts at root

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4005 
 
 
 
  users timezone permission delta task starts at root  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 From the {{CoreModuleVersionHandler}}:{code}register((DeltaBuilder.update("5.4.7", "")).addTask(new AddUsersPermissionTask("Allow users to edit their timezone setting", "/", RepositoryConstants.USERS, AddUsersPermissionTask.USER_PATH_REPLACEMENT + "/timezone", Permission.ALL).exclude(MgnlUserManager.SYSTEM_USER, MgnlUserManager.ANONYMOUS_USER)){code}Setting it to start at root causes it to crawl over {{jcr:system}} nodes.  This can take a while for some customers.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4005) users timezone permission delta task starts at root

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4005 
 
 
 
  users timezone permission delta task starts at root  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4005) users timezone permission delta task starts at root

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4005 
 
 
 
  users timezone permission delta task starts at root  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 02/Sep/16 6:22 PM 
 
 
 

Fix Versions:
 

 5.4.x 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-4005) users timezone permission delta task starts at root

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4005 
 
 
 
  users timezone permission delta task starts at root  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 From the {{CoreModuleVersionHandler}}:{code}register((DeltaBuilder.update("5.4.7", "")).addTask(new AddUsersPermissionTask("Allow users to edit their timezone setting", "/", RepositoryConstants.USERS, AddUsersPermissionTask.USER_PATH_REPLACEMENT + "/timezone", Permission.ALL).exclude(MgnlUserManager.SYSTEM_USER, MgnlUserManager.ANONYMOUS_USER)){code}Setting it to start at root causes it to crawl over {{jcr:system}} nodes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4004) Asynchronous actions can consume a lot of memory

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4004 
 
 
 
  Asynchronous actions can consume a lot of memory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.3.16 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4004) Asynchronous actions can consume a lot of memory

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4004 
 
 
 
  Asynchronous actions can consume a lot of memory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Affects Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4004) Asynchronous actions can consume a lot of memory

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4004 
 
 
 
  Asynchronous actions can consume a lot of memory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

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-801) Fix "Cleaning activation errors"

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-801 
 
 
 
  Fix "Cleaning activation errors"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Summary:
 
 Fix "Cleaning activation errors"  documentation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-801) Fix "Cleaning activation errors" documentation

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-801 
 
 
 
  Fix "Cleaning activation errors" documentation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Richard Gange 
 
 
 

Created:
 

 25/Aug/16 4:16 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
This documentation states that the "clean mgnlsystem workspace" button can clean "corrupted" data. See https://documentation.magnolia-cms.com/display/DOCS/Cleaning+activation+errors. It cannot do that. It can only clean "garbage" data that may have been left behind.  
If a workspace is "corrupt" then you must use repository inconsistency methods for that. See https://documentation.magnolia-cms.com/display/DOCS/Repository+inconsistency.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (SUGGEST-48) searchfn in jsp

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-48 
 
 
 
  searchfn in jsp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 how to build an searchPage in jsp with searchfn ? OR how to translate following to jsp ? {code} [#assign searchResults = searchfn.searchPages('hello', '/home') /]  [#if searchResults?has_content][#list searchResults as item]${item.title!}${item.excerpt!}[/#list][/#if] {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3996) multiple instances of same dialog opening

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3996 
 
 
 
  multiple instances of same dialog opening   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Summary:
 
 Multiple Dialog box opens up when an edit component tried  multiple  time  instances of same dialog opening  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-794) add "scheduled" tasks

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-794 
 
 
 
  add "scheduled" tasks  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 19/Aug/16 5:14 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The current documentation for Tasks (https://documentation.magnolia-cms.com/display/DOCS/Tasks) makes no mention of the scheduled task.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by 

[magnolia-dev] [JIRA] (MGNLUI-3986) allow for disabling of up/down buttons in the MultiValueField

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3986 
 
 
 
  allow for disabling of up/down buttons in the MultiValueField  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

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-3986) allow for disabling of up/down buttons in the MultiValueField

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3986 
 
 
 
  allow for disabling of up/down buttons in the MultiValueField  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Attachment:
 
 DelegatingMultiValueExample.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] (MGNLUI-3986) allow for disabling of up/down buttons in the MultiValueField

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3986 
 
 
 
  allow for disabling of up/down buttons in the MultiValueField  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 16/Aug/16 4:44 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
There are some cases where the up/down buttons to reorder values become useless. One such example: https://documentation.magnolia-cms.com/display/DOCS/Transforming+field+values#Transformingfieldvalues-Combiningdelegatingtransformers 
It would be a nice improvement if you could disable the buttons through configuration.  
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3962) multiple publishing leaves page in "modified" state

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3962 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 To reproduce this issue:# Create a new test page in the travel demo using the basic template.# Add an image component to the page and select an image from the dam.# Start publication on the page so a task makes it into the pulse.# Change the image on the test page and publish it again so that 2 tasks appear in the pulse.# Approve the test page for publication in the same order. First version first, second version second. # Go back to the pages app and observe the page remains in a modified (yellow) instead of the  green ( published  (green ), even though the page is in the same state on both author and public.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3962) multiple publishing leaves page in "modified" state

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3962 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3962) multiple publishing leaves page in "modified" state

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3962 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 To reproduce this issue:# Create a new test page in the travel demo using the basic template.# Add an image component to the page and select an image from the dam.# Start publication on the page so a task makes it into the pulse.# Change the image on the test page and publish it again so that 2 tasks appear in the pulse.# Approve the test page for publication in the same order. First  page  version  first, second  page  version  second. # Go back to the pages app and observe the page remains in a modified (yellow) instead of the green (published), even though the page is in the same state on both author and public.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3962) multiple publishing leaves page in "modified" state

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3962 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 pages app 
 
 
 

Created:
 

 25/Jul/16 4:09 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
To reproduce this issue: 
 

Create a new test page in the travel demo using the basic template.
 

Add an image component to the page and select an image from the dam.
 

Start publication on the page so a task makes it into the pulse.
  

[magnolia-dev] [JIRA] (MGNLUI-3954) Sliding "Warning" Bar

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3954 
 
 
 
  Sliding "Warning" Bar  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Project:
 
 Magnolia  UI 
 
 
 

Key:
 
 MAGNOLIA MGNLUI - 6578 3954 
 
 
 

Component/s:
 
 user interaction 
 
 
 

Component/s:
 
 admininterface 
 
 
 

Affects Version/s:
 
 5.4.5 
 
 
 

Affects Version/s:
 
 5.4.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

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-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 Currently messages are organized in the messages workspace by username. So each username has an entry in the workspace. Under the username node there can be several message nodes all organized at the same level (see messages.png attached). This creates a problem when a user accumulates  to  too  many messages. This issue is similar to one we had with tasks (see TASKMGMT-22). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 Currently messages are organized in the messages workspace by username. So each username has an entry in the workspace. Under the username node there can be several message nodes all organized at the same level (see messages.png attached). This creates a  performance  problem when a user accumulates too many messages  under a single username node .     This issue is similar to one we had with tasks (see TASKMGMT-22). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

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] (MGNLUI-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 Currently messages are organized in the messages workspace by username. So each username has an entry in the workspace. Under the username node there can be several message nodes all organized at the same level (see messages.png attached). This creates a problem when a user accumulates to many messages.    This issue is similar to one we had with tasks (see TASKMGMT-22). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 

Attachment:
 
 messages.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] (MGNLUI-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 messages app 
 
 
 

Created:
 

 05/Jul/16 4:21 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Richard Gange 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Currently messages are organized in the messages workspace by username. So each username has an entry in the workspace. Under the username node there can be several message nodes all organized at the same level. This creates a problem when a user accumulates to many messages.  
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3936) Newly created messages are not be stored in proper date folder

[JIRA (on behalf of Richard Gange)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Gange updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3936 
 
 
 
  Newly created messages are not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Richard Gange 
 
 
 
 
 
 
 
 
 
 Currently messages are organized in the messages workspace by username. So each username has an entry in the workspace. Under the username node there can be several message nodes all organized at the same level  (see messages . png attached).  This creates a problem when a user accumulates to many messages.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: