[magnolia-dev] [JIRA] (FORMDB-15) Flat and unclear persistence structur

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-15  
 
 
  Flat and unclear persistence structur   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 
 
Attachment: 
 screenshot-2.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] (FORMDB-16) Excel export should contains only creation date and form data in alphabetically order

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-16  
 
 
  Excel export should contains only creation date and form data in alphabetically order   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 
 
Environment: 
 M5.4.10, Forn2DB 1.1.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (FORMDB-16) Excel export should contains only creation date and form data in alphabetically order

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-16  
 
 
  Excel export should contains only creation date and form data in alphabetically order   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Marvin Kerkhoff  
 
 
Created: 
 23/Feb/17 12:30 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Frank Sommer  
 

  
 
 
 
 

 
 The ordering of the exported fields is not clear and differs on form export and form entry export. Further the mgnl:xyz fields are not useless.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 

[magnolia-dev] [JIRA] (FORMDB-16) Excel export should contains only creation date and form data in alphabetically order

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-16  
 
 
  Excel export should contains only creation date and form data in alphabetically order   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 

  
 
 
 
 

 
 The ordering of the exported fields is not clear and differs on form export and form entry export. Further the _mgnl:xyz_ fields are  not  useless.  
 

  
 
 
 
 

 
 
 

 
 
 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] (FORMDB-15) Flat and unclear persistence structur

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-15  
 
 
  Flat and unclear persistence structur   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 
 
Attachment: 
 screenshot-1.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] (FORMDB-15) Flat and unclear persistence structur

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-15  
 
 
  Flat and unclear persistence structur   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 

  
 
 
 
 

 
 If you have only one website with less forms the persistence structure of the form data is okay. But with more the one site and many languages, you will lost the overview about the stored form data.It should be better if the form data is stored in the same structure like the page structure. So you can maintain the access to the stored form data. E.g. the editor for site-A and language de (in website below /site-a/de) has access to the form data in the same structure.Furthermore the single form entries should be stored in date based notation and not only with a numeric name. See attached screenshot.  !screenshot-1.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: 

[magnolia-dev] [JIRA] (FORMDB-15) Flat and unclear persistence structur

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-15  
 
 
  Flat and unclear persistence structur   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Marvin Kerkhoff  
 
 
Created: 
 16/Feb/17 11:12 AM  
 
 
Environment: 
 M5.4.10, Forn2DB 1.1.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Frank Sommer  
 

  
 
 
 
 

 
 If you have only one website with less forms the persistence structure of the form data is okay. But with more the one site and many languages, you will lost the overview about the stored form data. It should be better if the form data is stored in the same structure like the page structure. So you can maintain the access to the stored form data. E.g. the editor for site-A and language de (in website below /site-a/de) has access to the form data in the same structure. Furthermore the single form entries should be stored in date based notation and not only with a numeric name. See attached screenshot.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[magnolia-dev] [JIRA] (FORMDB-13) Storing form data should be configurable in form component dialog

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-13  
 
 
  Storing form data should be configurable in form component dialog   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Marvin Kerkhoff  
 
 
Created: 
 16/Feb/17 11:02 AM  
 
 
Environment: 
 M5.4.10, Form2DB 1.1.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Frank Sommer  
 

  
 
 
 
 

 
 If you have many forms in your website, you don't want to store every form data to the JCR. It makes no sense to store every contact form in the JCR.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[magnolia-dev] [JIRA] (FORMDB-14) Save form data should be executed in system context

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-14  
 
 
  Save form data should be executed in system context   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Marvin Kerkhoff  
 
 
Created: 
 16/Feb/17 11:04 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Frank Sommer  
 

  
 
 
 
 

 
 Writing in the form2db workspace should be done in system context. In my opinion the anonymous user shouldn't have write access to any workspace.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

[magnolia-dev] [JIRA] (PROCRES-8) Module does not work anymore with 5.4.10

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Processed resources /  PROCRES-8  
 
 
  Module does not work anymore with 5.4.10   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 

  
 
 
 
 

 
 After upgrade to Magnolia 5.4.10 the processed resources module doesn't work, because the resource mapping couldn't be instantiate.{noformat}17-01-19 14:25:26 WARN  AUTHOR[localhost-startStop-1]info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl: Can't instantiate bean for /server/URI2RepositoryMapping/mappings/resources info.magnolia.jcr.node2bean.Node2BeanException: com.google.inject.ProvisionException: Guice provision errors:1) Module instance for module [resources] not available, most likely because the module has not yet been started. Inject a Provider<> instead to get access to the module instance when it's available.  at info.magnolia.objectfactory.guice.GuiceComponentConfigurationModule.bindProvider(GuiceComponentConfigurationModule.java:190)  while locating info.magnolia.module.resources.ResourcesModule1 errorat info.magnolia.jcr.node2bean.impl.Node2BeanTransformerImpl.newBeanInstance(Node2BeanTransformerImpl.java:248)at info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl.toBean(Node2BeanProcessorImpl.java:135)at info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl.toMap(Node2BeanProcessorImpl.java:227)at info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl.toBean(Node2BeanProcessorImpl.java:132){noformat} I think the problem occures only, if you start Magnolia in *not* auto update mode.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was 

[magnolia-dev] [JIRA] (PROCRES-8) Module does not work anymore with 5.4.10

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Processed resources /  PROCRES-8  
 
 
  Module does not work anymore with 5.4.10   
 

  
 
 
 
 

 
Change By: 
 Frank Sommer  
 
 
Attachment: 
 patch.diff  
 

  
 
 
 
 

 
 
 

 
 
 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] (PROCRES-8) Module does not work anymore with 5.4.10

[JIRA (on behalf of Frank Sommer)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Sommer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Processed resources /  PROCRES-8  
 
 
  Module does not work anymore with 5.4.10   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 1.0.2  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 
 
Created: 
 19/Jan/17 3:06 PM  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Frank Sommer  
 

  
 
 
 
 

 
 After upgrade to Magnolia 5.4.10 the processed resources module doesn't work, because the resource mapping couldn't be instantiate. 

 
17-01-19 14:25:26 WARN  AUTHOR[localhost-startStop-1]info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl: Can't instantiate bean for /server/URI2RepositoryMapping/mappings/resources info.magnolia.jcr.node2bean.Node2BeanException: com.google.inject.ProvisionException: Guice provision errors:

1) Module instance for module [resources] not available, most likely because the module has not yet been started. Inject a Provider<> instead to get access to the module instance when it's available.
  at info.magnolia.objectfactory.guice.GuiceComponentConfigurationModule.bindProvider(GuiceComponentConfigurationModule.java:190)
  while locating info.magnolia.module.resources.ResourcesModule

1 error
at info.magnolia.jcr.node2bean.impl.Node2BeanTransformerImpl.newBeanInstance(Node2BeanTransformerImpl.java:248)
at info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl.toBean(Node2BeanProcessorImpl.java:135)
at info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl.toMap(Node2BeanProcessorImpl.java:227)
at info.magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl.toBean(Node2BeanProcessorImpl.java:132)
 

  
 

  
 

[magnolia-dev] [JIRA] (JCRTOOLS-38) Exporter should support filtering of sub nodes and properties

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-38 
 
 
 
  Exporter should support filtering of sub nodes and properties  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Nov/16 10:13 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
It would be very helpful if the exporter support the two following functionalities. 
 

Export only one node of this type 
 

E.g. Export content of a single page. So it is possible to export just the home page without all the child article pages.
 
 
 

Exclude some properties for exported content 
 

E.g. exclude the activation state properties. So the editors are not confused by wrong activation states of imported content.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-343) Scheduled publications of deleted pages have positive Pulse result

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-343 
 
 
 
  Scheduled publications of deleted pages have positive Pulse result  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Attachment:
 
 scheduled-activation-of-removed-page-result.png 
 
 
 

Attachment:
 
 scheduled-activation-of-removed-page.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] (MGNLWORKFLOW-343) Scheduled publications of deleted pages have positive Pulse result

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-343 
 
 
 
  Scheduled publications of deleted pages have positive Pulse result  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Nov/16 9:55 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
If you schedule a page publication and you remove the page before the schedule date, the scheduled work item will be shown as resolved. See attached screenshots. 
But the following exception will be thrown. 

 
ERROR  info.magnolia.personalization.command.PersonalizationActivationCommand 18.11.2016 09:40:00 -- Cannot execute activation command for the node 'website:/sportstation/about':
javax.jcr.ItemNotFoundException: 64cc52a3-326f-40b9-b021-c980f2959447
	at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384)
	at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:328)
	at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:622)
	at org.apache.jackrabbit.core.SessionImpl.getNodeById(SessionImpl.java:536)
 

 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-343) Scheduled publications of deleted pages have positive Pulse result

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-343 
 
 
 
  Scheduled publications of deleted pages have positive Pulse result  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 If you schedule a page publication and you remove the page before the schedule date, the scheduled work item will be shown as resolved. See attached screenshots.But the following exception will be thrown.{noformat}ERROR  info.magnolia.personalization.command.PersonalizationActivationCommand 18.11.2016 09:40:00 -- Cannot execute activation command for the node 'website:/sportstation/about':javax.jcr.ItemNotFoundException: 64cc52a3-326f-40b9-b021-c980f2959447 at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384) at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:328) at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:622) at org.apache.jackrabbit.core.SessionImpl.getNodeById(SessionImpl.java:536){noformat}I think it makes more sense, if the work item would be shown as failed and  is  should  not  be restartable. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-343) Scheduled publications of deleted pages have positive Pulse result

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-343 
 
 
 
  Scheduled publications of deleted pages have positive Pulse result  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 If you schedule a page publication and you remove the page before the schedule date, the scheduled work item will be shown as resolved. See attached screenshots.But the following exception will be thrown.{noformat}ERROR  info.magnolia.personalization.command.PersonalizationActivationCommand 18.11.2016 09:40:00 -- Cannot execute activation command for the node 'website:/sportstation/about':javax.jcr.ItemNotFoundException: 64cc52a3-326f-40b9-b021-c980f2959447 at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:384) at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:328) at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:622) at org.apache.jackrabbit.core.SessionImpl.getNodeById(SessionImpl.java:536){noformat} I think it makes more sense, if the work item would be shown as failed and is not 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (VANITY-18) Maven Build doesn't work out of the box

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-18 
 
 
 
  Maven Build doesn't work out of the box  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-17) Internal forwarding

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-17 
 
 
 
  Internal forwarding  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-17) Internal forwarding

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-17 
 
 
 
  Internal forwarding  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.4.1 
 
 
 

Affects Version/s:
 
 1.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (BLOSSOM-238) Tab definitions without a field create NPE in FormPresenter

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-238 
 
 
 
  Tab definitions without a field create NPE in FormPresenter  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 3.1.3 
 
 
 

Assignee:
 
 Tobias Mattsson 
 
 
 

Created:
 

 22/Jul/16 11:38 AM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
Since upgrade to Magnolia 5.4.7 and corresponding Blossom 3.1.3 it is not possible to have empty dialog tabs. With Magnolia 5.3.14 empty tabs are hidden in dialogs. Now the following NPE is logged and the dialog could not be opened. 

 
Caused by: java.lang.NullPointerException: null value in entry: info.magnolia.ui.form.definition.ConfiguredTabDefinition@6ae197c=null
at vom.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:33)
at com.google.common.collect.RegularImmutableMap.(RegularImmutableMap.java:88)
at com.google.common.collect.ImmutableMap.copyOf(ImmutableMap.java:294)
at com.google.common.collect.Maps.toMap(Maps.java:1121)
at com.google.common.collect.Maps.toMap(Maps.java:1097)
at info.magnolia.ui.dialog.formdialog.FormPresenterImpl.presentView(FormPresenterImpl.java:117)
at info.magnolia.ui.dialog.formdialog.FormDialogPresenterImpl.buildView(FormDialogPresenterImpl.java:167)
at info.magnolia.ui.dialog.formdialog.FormDialogPresenterImpl.start(FormDialogPresenterImpl.java:152)
at info.magnolia.module.blossom.dialog.BlossomFormDialogPresenter.start(BlossomFormDialogPresenter.java:91)
 

  

[magnolia-dev] [JIRA] (PROCRES-5) UUID conflict on upgrade Magnolia with processed resources module

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-5 
 
 
 
  UUID conflict on upgrade Magnolia with processed resources module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 On upgrade Magnolia to 5.4.7  with resources 2.4.5  I get following exception.{noformat}Caused by: javax.jcr.ItemExistsException: a node with uuid a53f308a-0d6a-4bb9-a5f8-6f11ff68504d already exists!at org.apache.jackrabbit.core.xml.SessionImporter.resolveUUIDConflict(SessionImporter.java:230)at org.apache.jackrabbit.core.xml.SessionImporter.startNode(SessionImporter.java:408)at org.apache.jackrabbit.core.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:93){noformat}It is an uuid conflict on bootstrapping the resources form dialog, which already exists in the _resources_ module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PROCRES-5) UUID conflict on upgrade Magnolia with processed resources module

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-5 
 
 
 
  UUID conflict on upgrade Magnolia with processed resources module  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 

Created:
 

 18/Jul/16 9:44 AM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
On upgrade Magnolia to 5.4.7 I get following exception. 

 
 

 
Caused by: javax.jcr.ItemExistsException: a node with uuid a53f308a-0d6a-4bb9-a5f8-6f11ff68504d already exists! at org.apache.jackrabbit.core.xml.SessionImporter.resolveUUIDConflict(SessionImporter.java:230) at org.apache.jackrabbit.core.xml.SessionImporter.startNode(SessionImporter.java:408) at org.apache.jackrabbit.core.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:93) {noforamt} 
It is an uuid conflict on bootstrapping the resources form dialog, which already exists in the resources module. 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (PROCRES-5) UUID conflict on upgrade Magnolia with processed resources module

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-5 
 
 
 
  UUID conflict on upgrade Magnolia with processed resources module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 On upgrade Magnolia to 5.4.7 I get following exception.{noformat}Caused by: javax.jcr.ItemExistsException: a node with uuid a53f308a-0d6a-4bb9-a5f8-6f11ff68504d already exists!at org.apache.jackrabbit.core.xml.SessionImporter.resolveUUIDConflict(SessionImporter.java:230)at org.apache.jackrabbit.core.xml.SessionImporter.startNode(SessionImporter.java:408)at org.apache.jackrabbit.core.xml.SysViewImportHandler.processNode(SysViewImportHandler.java:93){ noforamt noformat }It is an uuid conflict on bootstrapping the resources form dialog, which already exists in the _resources_ module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3944) Resource delete confirmation message is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3944 
 
 
 
  Resource delete confirmation message is not correct processed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 If a German user deletes a resource from resources app, a not processed confirmation message will be shown. Following error message is logged. {noformat}16-07-12 10:17:08 WARN  AUTHOR[http-bio-8001-exec-9]info.magnolia.i18nsystem.util.MessageFormatterUtils: Inserting arguments into message 'Zum L÷schen markierte Ressource {0,Wahl,1# Datei|1< Dateien} erfolgreich gel÷scht.' failed: 'unknown format type: Wahl'.{noformat} Seems to be the same reason like MGNLUI-3922 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3944) Resource delete confirmation message is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3944 
 
 
 
  Resource delete confirmation message is not correct processed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 admincentral, dialogs 
 
 
 

Created:
 

 12/Jul/16 10:12 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
If a German user deletes a resource from resources app, a not processed confirmation message will be shown. 
Seems to be the same reason like MGNLUI-3922 
 
 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-3922) Page delete confirmation message in dialog is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3922 
 
 
 
  Page delete confirmation message in dialog is not correct processed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Attachment:
 
 remove-resource.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-3922) Page delete confirmation message in dialog is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3922 
 
 
 
  Page delete confirmation message in dialog is not correct processed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 The message in page delete confirmation dialog is not processed. The bug occures  at least  for French and Italian users. German and English is fine. It is reproducable on Demoauthor instance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3922) Page delete confirmation message in dialog is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3922 
 
 
 
  Page delete confirmation message in dialog is not correct processed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.6, 5.3.14 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 remove-dialog-french.png, remove-dialog-italian.png 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 21/Jun/16 1:40 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The message in page delete confirmation dialog is not processed. The bug occures for French and Italian users. German and English is fine. It is reproducable on Demoauthor instance. 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 An in JCR configured select field does not work with filtering. I attach my select field configuration as bootstrap file  [^config . modules.pages.dialogs.editPage.form.tabs.tabPage.fields.select.xml]. It is reproducible on Demoauthor. # Go to https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/modules/pages/dialogs/editPage/form/tabs/tabPage/fields:treeview:# Add a select field with filtering, described here https://documentation.magnolia-cms.com/display/DOCS/Select+field# Then opens https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:pages:;/sportstation:treeview: and click 'Rename page'## in the select field you can type, but nothings happens, no filtering (see [^screenshot-1.png]) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Attachment:
 
 config.modules.pages.dialogs.editPage.form.tabs.tabPage.fields.select.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 An in JCR configured select field does not work with filtering.  I attach my select field configuration as bootstrap file. It is reproducible on Demoauthor. # Go to https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/modules/pages/dialogs/editPage/form/tabs/tabPage/fields:treeview:# Add a select field with filtering, described here https://documentation.magnolia-cms.com/display/DOCS/Select+field# Then opens https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:pages:;/sportstation:treeview: and click 'Rename page'## in the select field you can type, but nothings happens, no filtering (see [^screenshot-1.png]) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 An in JCR configured select field does not work with filtering.It is reproducible on Demoauthor. # Go to https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/modules/pages/dialogs/editPage/form/tabs/tabPage/fields:treeview:# Add a select field with filtering, described here https://documentation.magnolia-cms.com/display/DOCS/Select+field# Then opens https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:pages:;/sportstation:treeview: and click 'Rename page'## in the select field you can type, but nothings happens, no filtering  (see [^screenshot-1.png]) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 An in JCR configured select field does not work with filtering. It is reproducible on Demoauthor. # Go to https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/modules/pages/dialogs/editPage/form/tabs/tabPage/fields:treeview:# Add a select field with filtering, described here https://documentation.magnolia-cms.com/display/DOCS/Select+field# Then opens https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:pages:;/sportstation:treeview: and click 'Rename page'## in the select field you can type, but nothings happens, no filtering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3893) Filtering mode in select fields dows not work

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3893 
 
 
 
  Filtering mode in select fields dows not work  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.6, 5.3.14 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 26/May/16 10:47 AM 
 
 
 

Environment:
 

 Firefox 43 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
An in JCR configured select field does not work with filtering. 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-331) Scheduled publication won't executed after Tomcat restart

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-331 
 
 
 
  Scheduled publication won't executed after Tomcat restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 If you schedule a publication and restart the server before the publication date is reached, the activation won't be executed. The workflow process is still active, but won't be triggered to be executed. In Magnolia 5.4.x with workflow 5.5.1 it seems to work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-331) Scheduled publication won't executed after Tomcat restart

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-331 
 
 
 
  Scheduled publication won't executed after Tomcat restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 5.5.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-331) Scheduled publication won't executed after Tomcat restart

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-331 
 
 
 
  Scheduled publication won't executed after Tomcat restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 5.5.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-331) Scheduled publication won't executed after Tomcat restart

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-331 
 
 
 
  Scheduled publication won't executed after Tomcat restart  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 jBPM 
 
 
 

Created:
 

 20/Apr/16 10:58 AM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
If you schedule a publication and restart the server before the publication date is reached, the activation won't be executed. The workflow process is still active, but won't be triggered to be executed. 
 
 
 
 
 
 
 
 
 
 
 
 

  

[magnolia-dev] [JIRA] (MGNLUI-3174) Default value setting doesn't work for page properties dialog

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3174 
 
 
 
  Default value setting doesn't work for page properties dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3174) Default value setting doesn't work for page properties dialog

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3174 
 
 
 
  Default value setting doesn't work for page properties dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 5.3.11 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3768) NPE in About Magnolia app after parsing failure

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3768 
 
 
 
  NPE in About Magnolia app after parsing failure  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.11 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 about app 
 
 
 

Created:
 

 12/Feb/16 11:12 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The about app crashes with an NullPointerException like: 

 
16-02-12 10:55:50 ERROR author[ajp-bio-127.0.0.1-8009-exec-11]info.magnolia.ui.framework.app.AppInstanceControllerImpl:
Sub-app main failed to start: java.lang.reflect.InvocationTargetException
info.magnolia.objectfactory.MgnlInstantiationException: java.lang.reflect.InvocationTargetException
at info.magnolia.objectfactory.ObjectManufacturer.newInstance(ObjectManufacturer.java:124)
at info.magnolia.objectfactory.ObjectManufacturer.newInstance(ObjectManufacturer.java:88)
at 

[magnolia-dev] [JIRA] (VANITY-13) Ability to specify HTTP response code per URL

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-13 
 
 
 
  Ability to specify HTTP response code per URL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-16) Task 'Check cache flush' failed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-16 
 
 
 
  Task 'Check cache flush' failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.4.0 
 
 
 

Affects Version/s:
 
 1.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-16) Task 'Check cache flush' failed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-16 
 
 
 
  Task 'Check cache flush' failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Environment:
 
 Magnolia 5.4.3 (new project)   com.aperto.magkitmagnolia-vanity-url  with 1.4.1-SNAPSHOT    
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-16) Task 'Check cache flush' failed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-16 
 
 
 
  Task 'Check cache flush' failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-12) Get rid of the STK dependency for Magnolia 5.4

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-12 
 
 
 
  Get rid of the STK dependency for Magnolia 5.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-12) Get rid of the STK dependency for Magnolia 5.4

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-12 
 
 
 
  Get rid of the STK dependency for Magnolia 5.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.4.1 
 
 
 

Fix Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-12) Get rid of the STK dependency for Magnolia 5.4

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-12 
 
 
 
  Get rid of the STK dependency for Magnolia 5.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-13) Ability to specify HTTP response code per URL

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-13 
 
 
 
  Ability to specify HTTP response code per URL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.3.3 
 
 
 

Fix Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-13) Ability to specify HTTP response code per URL

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-13 
 
 
 
  Ability to specify HTTP response code per URL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (VANITY-12) Get rid of the STK dependency for Magnolia 5.4

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-12 
 
 
 
  Get rid of the STK dependency for Magnolia 5.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCACHE-125) Cache header negotiation does not work for first request after cache flush

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-125 
 
 
 
  Cache header negotiation does not work for first request after cache flush  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Summary:
 
 Cache header negotiation does not work for first  Request  request  after cache flush 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCACHE-125) Cache header negotiation does not work for first Request after cache flush

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-125 
 
 
 
  Cache header negotiation does not work for first Request after cache flush  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 cache core 
 
 
 

Created:
 

 23/Oct/15 10:06 AM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
We've got trouble with different cache headers for the same page request. Sometimes we saw the correct no-cache headers and sometimes the default cache configuration headers. 
The pattern is that every first request after a cache flush will use the configured browser cache policies and overwrite the cache headers set by code. See Cache header negotiation 
The reason seems to be that missing cache entries will be stored as uncacheable cache entries in the cache. And then the cache will bypass such cache entry requests. But for the first request the browser cache policies will overwrite the existing cache headers.  
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (VANITY-15) Caching is not flushed for vanity urls

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-15 
 
 
 
  Caching is not flushed for vanity urls  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.3.3 
 
 
 

Fix Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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

[magnolia-dev] [JIRA] (VANITY-14) Use folders to structure vanity URLs

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-14 
 
 
 
  Use folders to structure vanity URLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Fix Version/s:
 
 1.3.3 
 
 
 

Fix Version/s:
 
 1.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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

[magnolia-dev] [JIRA] (VANITY-14) Use folders to structure vanity URLs

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Vanity URL app /  VANITY-14 
 
 
 
  Use folders to structure vanity URLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Affects Version/s:
 
 1.3.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.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-216) Avoid using deprecated DamConfig for tab creation

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-216 
 
 
 
  Avoid using deprecated DamConfig for tab creation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 3.0.6 
 
 
 

Assignee:
 
 Tobias Mattsson 
 
 
 

Created:
 

 06/Jul/15 10:25 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
With DAM 2.0.8 DamConfig is deprecated. Now all my TabFactory annotated methods have a deprecated parameter.  

 

@TabFactory(Content)
public void contentTab(UiConfig cfg, DamConfig dam, TabBuilder tab)
 

 
How can I avoid this? Is there an alternative way to go? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-300) Overview with scheduled workflow items

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-300 
 
 
 
  Overview with scheduled workflow items  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 29/Apr/15 3:22 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 
It is not transparent which page is already scheduled for un-/publication. A possible solution could be to provide an overview app with all scheduled workflow items. Additional the editor could cancel the workflow process or edit the schedule date. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 
 
 
 
 
 

[magnolia-dev] [JIRA] (DEAD-9) Null pointer exception when loading Deadlink

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Deadlink /  DEAD-9 
 
 
 
  Null pointer exception when loading Deadlink  
 
 
 
 
 
 
 
 
 
 
I attached fixed deadlink app configuration. The app will be shown now, but there is still a problem with the scan action. The error message points to a bug caused by a API change. 

 
RpcInvocationException: Unable to invoke method onActionTriggered in info.magnolia.ui.vaadin.gwt.client.actionbar.rpc.ActionbarServerRpc 
  caused by InvocationTargetException caused by MethodException: 
Invocation of method actionTrigger in info.magnolia.ui.actionbar.ActionbarViewImpl$1 failed. 
caused by NoSuchMethodError: info.magnolia.ui.vaadin.integration.jcr.JcrItemAdapter.getItemId()Ljava/lang/String;
 

 
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 

Attachment:
 
 config.modules.deadlink-app.apps.deadlink.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Alternatively,useourforums:http://forum.magnolia-cms.com/

[magnolia-dev] [JIRA] (BLOSSOM-202) Tab order does not work

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  BLOSSOM-202


Tab order does not work















Issue Type:


Bug



Affects Versions:


3.0.5, 3.0.4



Assignee:


Tobias Mattsson



Created:


17/Feb/15 10:12 AM



Description:


The ordering of dialog tabs with the TabOrder annotation does not work properly. Reason is that the sortTabs method uses for comparing the internationalized tab labels instead of the static tab names.

@see info.magnolia.module.blossom.dialog.DefaultDialogCreator#sortTabs




Project:


Magnolia Blossom Module



Priority:


Critical




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLGS-98) Missing i18n messages on sitemap publication in pulse

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLGS-98


Missing i18n messages on sitemap publication in pulse
















Change By:


Frank Sommer
(20/Jan/15 9:54 AM)




Attachment:


bug-publication-module-google-sitemap.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLGS-98) Missing i18n messages on sitemap publication in pulse

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLGS-98


Missing i18n messages on sitemap publication in pulse















Issue Type:


Bug



Affects Versions:


2.2.2



Assignee:


Unassigned


Attachments:


bug-publication-module-google-sitemap.png



Created:


20/Jan/15 9:54 AM



Description:


The publication message view for sitemap entries contains some property keys. The appropriate message values are not set. See screenshot

You can reproduce this on demoauthor. It doesn't work for superuser in English or German.




Project:


Magnolia Google Sitemap Module



Labels:


i18n




Priority:


Neutral




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLGS-98) Missing i18n messages on sitemap publication in pulse

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLGS-98


Missing i18n messages on sitemap publication in pulse
















Change By:


Frank Sommer
(20/Jan/15 9:57 AM)




Description:


Thepublicationmessageviewforsitemapentriescontainssomepropertykeys.Theappropriatemessagevaluesarenotset.SeescreenshotYoucanreproducethisondemoauthor.ItdoesntworkforsuperuserinEnglishorGerman.
FurtermoreinGermananencondingoccure.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3319) Url with subapp location does not work in security app

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-3319


Url with subapp location does not work in security app
















Change By:


Frank Sommer
(15/Jan/15 10:51 AM)




Attachment:


roles-subapp.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3319) Url with subapp location does not work in security app

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-3319


Url with subapp location does not work in security app
















Change By:


Frank Sommer
(15/Jan/15 10:52 AM)




Description:


Appswithseveralinitialopenedsubappsdonotsupporturlswithapreselectedsubapp.Forexamplethesecurityapp:http://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:security:roles;/:treeview:Thelinkshouldopentherolessubappdirectly.Butitopensthefirstsubappandordersthewantedsubappatthesecondposition.
Seeroles-subapp.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3319) Url with subapp location does not work in security app

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-3319


Url with subapp location does not work in security app
















Change By:


Frank Sommer
(15/Jan/15 10:52 AM)




Description:


Appswithseveralinitialopenedsubappsdonotsupporturlswithapreselectedsubapp.Forexamplethesecurityapp:http://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:security:roles;/:treeview:Thelinkshouldopentherolessubappdirectly.Butitopensthefirstsubappandordersthewantedsubappatthesecondposition.See
[^
roles-subapp.png
]



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3319) Url with subapp location does not work in security app

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-3319


Url with subapp location does not work in security app















Issue Type:


Bug



Affects Versions:


5.3.6, 5.3.5



Assignee:


Unassigned


Components:


admincentral



Created:


15/Jan/15 10:49 AM



Description:


Apps with several initial opened sub apps do not support urls with a pre selected subapp.

For example the security app: http://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:security:roles;/:treeview:

The link should open the roles subapp directly. But it opens the first subapp and orders the wanted subapp at the second position.




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (TASKMGMT-15) No german support of tasks in Pulse (I18N)

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  TASKMGMT-15


No german support of tasks in Pulse (I18N)















Issue Type:


Bug



Affects Versions:


1.0.1



Assignee:


Unassigned


Attachments:


tasks.png



Created:


11/Nov/14 12:33 PM



Description:


The task handling in Pulse is not translated into german. See screenshot




Project:


Task Management



Priority:


Neutral




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3250) New area isn't full internationalized

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-3250


New area isnt full internationalized















Issue Type:


Bug



Affects Versions:


5.3.4



Assignee:


Unassigned


Attachments:


new-component.png



Components:


page editor



Created:


10/Nov/14 3:59 PM



Description:


The new areas in page editor view are not full internationalized. So a strange mix with translated labels are occure. For example: "New Inhalt component". See Screenshot




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-9) Preview QR code shows binary text output instead of the image

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  VANITY-9


Preview QR code shows binary text output instead of the image















Issue Type:


Bug



Affects Versions:


1.3.0



Assignee:


Frank Sommer



Created:


05/Nov/14 1:57 PM



Description:


The URL for the QR code preview ends with the wrong extension. It should end with image extension.




Fix Versions:


1.3.1



Project:


Vanity URL app



Priority:


Neutral




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-9) Preview QR code shows binary text output instead of the image

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-9


Preview QR code shows binary text output instead of the image
















Change By:


Frank Sommer
(05/Nov/14 2:38 PM)




Fix Version/s:


1.3.2





Fix Version/s:


1.3.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-9) Preview QR code shows binary text output instead of the image

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-9


Preview QR code shows binary text output instead of the image
















Change By:


Frank Sommer
(05/Nov/14 2:38 PM)




Affects Version/s:


1.3.1





Affects Version/s:


1.3.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLWORKFLOW-276) Log message contains place holder

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLWORKFLOW-276


Log message contains place holder















Issue Type:


Bug



Affects Versions:


5.4.1



Assignee:


Unassigned


Created:


03/Nov/14 1:11 PM



Description:


The following log message is buggy and still contains a place holder.


14-11-03 13:05:34 INFO  AUTHOR[Thread-19]info.magnolia.module.workflow.registry.WorkflowDefinitionRegistry: Definitions for workflows will be reloaded on system restart. Currently registered [{0}]





Project:


Magnolia Workflow Module



Priority:


Minor




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLWORKFLOW-276) Log message contains place holder

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLWORKFLOW-276


Log message contains place holder
















Change By:


Frank Sommer
(03/Nov/14 1:59 PM)




Affects Version/s:


5.3.4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3174) Default value setting doesn't work for page properties dialog

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-3174


Default value setting doesnt work for page properties dialog















Issue Type:


Bug



Affects Versions:


5.3.3



Assignee:


Unassigned


Components:


dialogs



Created:


26/Sep/14 1:26 PM



Description:


If you set the defaultValue property on a TextField form field an a page properties dialog, no default value will appear in the displayed dialog. On components it works. In my opinion the default value should be always displayed, if no value for the property is stored.

You can reproduce this on demoauthor.




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-4) External link building

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-4


External link building
















Change By:


Frank Sommer
(19/Sep/14 3:00 PM)




Fix Version/s:


1.2.2





Fix Version/s:


1.2.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-4) External link building

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-4


External link building
















Change By:


Frank Sommer
(19/Sep/14 3:00 PM)




Fix Version/s:


1.3.1





Fix Version/s:


1.3.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (BLOSSOM-191) Area annotation should also support area node creation flag

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  BLOSSOM-191


Area annotation should also support area node creation flag















Issue Type:


Improvement



Affects Versions:


3.0.3



Assignee:


Tobias Mattsson



Created:


12/Sep/14 12:21 PM



Description:


Like configured area definitions the area annotation should support the createAreaNode flag. Otherwise the usage of the area directives in freemarker between Blossom and configured areas is different.

See also MAGNOLIA-4711




Project:


Magnolia Blossom Module



Priority:


Neutral




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3123) Date property change in JCR browser doesn't work

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-3123


Date property change in JCR browser doesnt work















Issue Type:


Bug



Affects Versions:


5.2.7



Assignee:


Unassigned


Components:


content app



Created:


26/Aug/14 3:40 PM



Description:


If you change a date property in website jcr browser, the change won't be saved. Instead the current time will be set.

There is no corresponding error message in the log. It is reproducable on the demoauthor instance.




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-4) External link building

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-4


External link building
















Change By:


Frank Sommer
(13/Aug/14 8:55 AM)




Fix Version/s:


1.3.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-3) URL title + url configuration

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-3


URL title + url configuration
















Change By:


Frank Sommer
(13/Aug/14 8:56 AM)




Fix Version/s:


1.3.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-6) App stopping after starting in 5.3

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-6


App stopping after starting in 5.3
















Change By:


Frank Sommer
(13/Aug/14 8:53 AM)




Fix Version/s:


1.3.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-7) Label for delete confirm dialog not set

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-7


Label for delete confirm dialog not set
















Change By:


Frank Sommer
(13/Aug/14 8:53 AM)




Fix Version/s:


1.3.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-7) Label for delete confirm dialog not set

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  VANITY-7


Label for delete confirm dialog not set















Issue Type:


Bug



Affects Versions:


1.2.0



Assignee:


Frank Sommer



Created:


11/Aug/14 12:33 PM



Description:


The various labels for the delete confirm dialog don't exist.




Fix Versions:


1.2.1



Project:


Vanity URL app



Priority:


Neutral




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3072) Upload a binary with drag and drop in IE9 doesn' work

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-3072


Upload a binary with drag and drop in IE9 doesn work















Issue Type:


Bug



Affects Versions:


5.3.1



Assignee:


Unassigned


Components:


widgets



Created:


18/Jul/14 1:57 PM



Description:


Upload with drag and drop in IE9 doesn't work. After trying that in IE9, I must close the browser window, the admincentral does not react anymore.




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3060) On HTTPS favorites are saved with protocol and domain

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-3060


On HTTPS favorites are saved with protocol and domain















Issue Type:


Bug



Affects Versions:


5.2.5



Assignee:


Unassigned


Components:


favorites



Created:


14/Jul/14 4:52 PM



Description:


If I use the secure https protocol, the favorites will stored with its complete external url. This is reproducable on demoauthor.

Reason is a bug in info.magnolia.ui.admincentral.shellapp.favorites.FavoritesPresenter#getWebAppRootURI. The method uses the information of the request to remove the domain part from the url. But the request knows nothing about https. The method should use the information from vaadin to cleanup the location url.




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLFORM-233) NullPointerException on sending confirmation mail

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLFORM-233


NullPointerException on sending confirmation mail















Issue Type:


Bug



Affects Versions:


2.2.4



Assignee:


Unassigned


Components:


processor



Created:


07/Jul/14 3:07 PM



Description:


If you try to send a confirmation mail and there is no confirmation mail text stored, a NullPointerException will occure. 
The fix could be a simple null check in info.magnolia.module.mail.templates.impl.FreemarkerEmail#processFreemarkerString.


14-07-03 11:03:39 ERROR AUTHOR[ajp-bio-8009-exec-88]info.magnolia.module.form.processors.SendConfirmationEMailProcessor: Confirmation email
java.lang.NullPointerException
  at java.io.StringReader.init(StringReader.java:50)
  at info.magnolia.module.mail.templates.impl.FreemarkerEmail.processFreemarkerString(FreemarkerEmail.java:103)
  at info.magnolia.module.mail.templates.impl.FreemarkerEmail.setBody(FreemarkerEmail.java:84)
  at info.magnolia.module.form.processors.AbstractEMailFormProcessor.sendMail(AbstractEMailFormProcessor.java:62)
  at info.magnolia.module.form.processors.SendConfirmationEMailProcessor.internalProcess(SendConfirmationEMailProcessor.java:89)
  at info.magnolia.module.form.processors.AbstractFormProcessor.process(AbstractFormProcessor.java:68)
  at info.magnolia.module.form.templates.components.AbstractFormEngine.executeProcessors(AbstractFormEngine.java:150)
  at info.magnolia.module.form.engine.FormEngine.processSubmission(FormEngine.java:214)
  at info.magnolia.module.form.engine.FormEngine.handleRequest(FormEngine.java:133)






Project:


Magnolia Form Module



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-4) External link building

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-4


External link building
















Change By:


Frank Sommer
(07/Jul/14 6:47 PM)




Affects Version/s:


1.2.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-4) External link building

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-4


External link building
















Change By:


Frank Sommer
(07/Jul/14 6:47 PM)




Fix Version/s:


1.2.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-3) URL title + url configuration

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-3


URL title + url configuration
















Change By:


Frank Sommer
(07/Jul/14 6:48 PM)




Affects Version/s:


1.2.0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-3) URL title + url configuration

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  VANITY-3


URL title + url configuration
















Change By:


Frank Sommer
(07/Jul/14 6:48 PM)




Fix Version/s:


1.2.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (VANITY-1) QR-Code should contains the vanity url instead the redirect target url

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  VANITY-1


QR-Code should contains the vanity url instead the redirect target url















Issue Type:


Improvement



Assignee:


Frank Sommer



Created:


24/Jun/14 10:47 AM



Description:


This would be benefits for testing the redirect with the rendered QR code and you need not print new qr codes if destination will change.




Fix Versions:


1.2.0



Project:


Vanity URL app



Priority:


Neutral




Reporter:


Frank Sommer




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-2968) Rich text editor (ck editor) ui in wrong language

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-2968


Rich text editor (ck editor) ui in wrong language















Issue Type:


Bug



Affects Versions:


5.2.4



Assignee:


Unassigned


Components:


dialogs



Created:


05/Jun/14 11:59 AM



Description:


The rich text editor should use for it's UI the user language. At the moment it uses the browser language.




Project:


Magnolia UI



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-2968) Rich text editor (ck editor) ui in wrong language

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-2968


Rich text editor (ck editor) ui in wrong language
















Change By:


Frank Sommer
(05/Jun/14 12:01 PM)




Attachment:


screenshot-1.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-2945) Action availability with writePermissionRequired does not work on root level

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 created  MGNLUI-2945


Action availability with writePermissionRequired does not work on root level















Issue Type:


Bug



Affects Versions:


5.2.4



Assignee:


Unassigned


Components:


content app



Created:


28/May/14 8:59 AM



Description:


If you restrict the access to actions with the writePermissionRequired flag, it will work except on root level (no item is selected). The 'Add ...' and 'Import' actions are always clickable.




Project:


Magnolia UI



Priority:


Major




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-2945) Action availability with writePermissionRequired does not work on root level

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-2945


Action availability with writePermissionRequired does not work on root level
















Change By:


Frank Sommer
(28/May/14 9:06 AM)




Attachment:


read-only-actions.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-2933) Configured component descrption is never shown

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-2933


Configured component descrption is never shown
















Change By:


Frank Sommer
(22/May/14 9:37 AM)




Issue Type:


Bug
Improvement



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-2933) Configured component descrption is never shown

[JIRA (on behalf of Frank Sommer)]

Frank Sommer
 updated  MGNLUI-2933


Configured component descrption is never shown
















Change By:


Frank Sommer
(22/May/14 9:38 AM)




Affects Version/s:


5.1.2





Affects Version/s:


5.0.4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com