[magnolia-dev] [JIRA] (MGNLUI-3829) Translation keys for German are missing in google sitemap module

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3829 
 
 
 
  Translation keys for German are missing in google sitemap module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Component/s:
 
 content app 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3829) Translation keys for German are missing in google sitemap module

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3829 
 
 
 
  Translation keys for German are missing in google sitemap module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 
 
 
 
 
 
 
 Hi Mgnls,after installing the Keys for German translation in  sitemap module  the dialog "new sitemap" only shows translation keys  are missing in [lang-de|https://git . See screenshot magnolia-cms . The user is superuser and has language english configured.As our customer is a german company we switched everything to German.I noticed when setting the fallback language in com  / server projects / LANG/repos/de/browse/src/main/resources/mgnl- i18n/ system back to "en" the translations appeared, although there are some translations missing (like Include Virtual URI s, description and others) google-sitemap/app-sitemaps-messages_de . Sigurd properties]. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3829) Translation keys for German are missing in google sitemap module

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3829 
 
 
 
  Translation keys for German are missing in google sitemap module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Affects Version/s:
 
 5.4.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3829) Translation keys for German are missing in google sitemap module

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3829 
 
 
 
  Translation keys for German are missing in google sitemap module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Assignee:
 
 Zdenek Skodik 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3829) Translation keys for German are missing in google sitemap module

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3829 
 
 
 
  Translation keys for German are missing in google sitemap module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Project:
 
 Support -  Magnolia  UI 
 
 
 

Key:
 
 SUPPORT MGNLUI - 5863 3829 
 
 
 

Issue Type:
 
 Magnolia Malfunction Improvement 
 
 
 

Workflow:
 
 Support New Product Dev  Workflow 
 
 
 

Security:
 
 Private Public 
 
 
 

Component/s:
 
 Functional issues 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCACHE-128) EhCacheWrapper does not catch LockTimeOutException properly

2016-03-23 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-128 
 
 
 
  EhCacheWrapper does not catch LockTimeOutException properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Assignee:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-128) EhCacheWrapper does not catch LockTimeOutException properly

2016-03-23 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-128 
 
 
 
  EhCacheWrapper does not catch LockTimeOutException properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Fix Version/s:
 
 5.4.4 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Kromeriz 36 
 
 
 

Account:
 
 
 
 
 

Affects Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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, 

[magnolia-dev] [JIRA] (MTE-78) Integrate light-module-maven-plugin into templating kit

2016-03-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-78 
 
 
 
  Integrate light-module-maven-plugin into templating kit  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The plugin will take care of auto-generating the npm package during 'generate-resource' phase and deploy it to nexus during 'deploy' phase. This has been manually tested with the attached patch.Some open questions:- There's no way to re-deploy SNAPSHOT versions. Once it's deployed to nexus, we have to manually DELETE the whole package (including all versions). No-go for production, but for testing we don't mind. How to solve it is not yet decided. (fixed in LMPLUGIN-2) - We should test it during release (staging). That's the fall-back solution if we can't solve the SNAPSHOT issue.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-133) AbstractListeningFlushPolicy#stop wrongly unregisters eventListeners for different cache

2016-03-23 Thread JIRA (on behalf of Milan Divilek) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milan Divilek updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-133 
 
 
 
  AbstractListeningFlushPolicy#stop wrongly unregisters eventListeners for different cache  
 
 
 
 
 
 
 
 
 

Change By:
 
 Milan Divilek 
 
 
 

Project:
 
 Magnolia  Advanced  Cache  Module 
 
 
 

Key:
 
 MGNLADVCACHE MGNLCACHE - 71 133 
 
 
 

Security:
 
 Public 
 
 
 

Fix Version/s:
 
 5.4.4 
 
 
 

Fix Version/s:
 
 1.7.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, 

[magnolia-dev] [JIRA] (MGNLCACHE-133) AbstractListeningFlushPolicy#stop wrongly unregisters eventListeners for different cache

2016-03-23 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-133 
 
 
 
  AbstractListeningFlushPolicy#stop wrongly unregisters eventListeners for different cache  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-78) Integrate light-module-maven-plugin into templating kit

2016-03-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-78 
 
 
 
  Integrate light-module-maven-plugin into templating kit  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 

Sprint:
 
 Basel 36 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-78) Integrate light-module-maven-plugin into templating kit

2016-03-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-78 
 
 
 
  Integrate light-module-maven-plugin into templating kit  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-327) CommandWorkItemHandler works only with commands inside the default catalog

2016-03-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-327 
 
 
 
  CommandWorkItemHandler works only with commands inside the default catalog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 2:37 PM 
 
 
 

Fix Versions:
 

 5.5.2 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
CommandWorkItemHandler doesn't read the passed commandCatalog.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (PAGES-62) Disable duplicate action in 'single' areas and when 'maxComponents' is reached

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

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-62 
 
 
 
  Disable duplicate action in 'single' areas and when 'maxComponents' is reached  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Assignee:
 
 Federico Grilli Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-62) Disable duplicate action in 'single' areas and when 'maxComponents' is reached

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

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-62 
 
 
 
  Disable duplicate action in 'single' areas and when 'maxComponents' is reached  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Assignee:
 
 Ilgun Ilgun Federico Grilli 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-62) Disable duplicate action in 'single' areas and when 'maxComponents' is reached

2016-03-23 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-62 
 
 
 
  Disable duplicate action in 'single' areas and when 'maxComponents' is reached  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Status:
 
 pre-integration QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3828) Improve resolution of sub-bean/collection names by DefinitionRawViewMapWrapper

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3828 
 
 
 
  Improve resolution of sub-bean/collection names by DefinitionRawViewMapWrapper  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 1:51 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Try to deduce name from sub-properties instead of using null 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was

[magnolia-dev] [JIRA] (MGNLUI-3820) Content Apps should offer a default action per node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3810) Pulse hides new tasks created by current user

2016-03-23 Thread JIRA (on behalf of Oanh Thai Hoang) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3810 
 
 
 
  Pulse hides new tasks created by current user  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Attachment:
 
 message-app-send-demo-project-editors.png 
 
 
 

Attachment:
 
 eric-pulse-case1.png 
 
 
 

Attachment:
 
 eric2-pulse-case1.png 
 
 
 

Attachment:
 
 message-app-send-editors.png 
 
 
 

Attachment:
 
 eric2-pulse-cae2.png 
 
 
 

Attachment:
 
 eric-pulse-case2.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3827) Add user may pre-fill dialog with superuser

2016-03-23 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3827 
 
 
 
  Add user may pre-fill dialog with superuser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Summary:
 
 Add user  may  pre- fills fill  dialog with superuser 
 
 
 

Priority:
 
 Major Neutral 
 
 
 

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-3827) Add user pre-fills dialog with superuser

2016-03-23 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3827 
 
 
 
  Add user pre-fills dialog with superuser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Account:
 
 
 
 
 

Environment:
 
 Firefox 44.0.2 
 
 
 
 
 
 
 
 
 
 In the Security app, hitting the "add user" action opens the dialog, with "superuser" (or current user, I don't know) pre-filled in the user name field, same for the first password field... Cannot reproduce on Chrome, could this be Firefox-only, interfering with saved passwords??! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3827) Add user pre-fills dialog with superuser

2016-03-23 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3827 
 
 
 
  Add user pre-fills dialog with superuser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Attachment:
 
 security-add-user.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] (LMPLUGIN-6) Improve version conversion between Magnolia and SemVer

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

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-6 
 
 
 
  Improve version conversion between Magnolia and SemVer  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 23/Mar/16 11:39 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 
It should be easily possible to use info.magnolia.module.model.Version in our code and make conversion between SemVer (com.github.zafarkhaja.semver.Version) and Magnolia versions easier. 
info.magnolia.module.model.Version → com.github.zafarkhaja.semver.Version and vice-versa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3827) Add user pre-fills dialog with superuser

2016-03-23 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3827 
 
 
 
  Add user pre-fills dialog with superuser  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 security app 
 
 
 

Created:
 

 23/Mar/16 11:36 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Mikaël Geljić 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
In the Security app, hitting the "add user" action opens the dialog, with "superuser" (or current user, I don't know) pre-filled in the user name field, same for the first password field...

[magnolia-dev] [JIRA] (MGNLGROOVY-145) NPE in in ConsoleContext when strategy is not set (when executing console OUT of web context (on a separate thread for example)

2016-03-23 Thread JIRA (on behalf of Milan Divilek) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milan Divilek updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-145 
 
 
 
  NPE in in ConsoleContext when strategy is not set (when executing console OUT of web context (on a separate thread for example)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Milan Divilek 
 
 
 

Priority:
 
 Neutral Critical 
 
 
 

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-3793) Improve notification of validation errors in composite fields

2016-03-23 Thread JIRA (on behalf of Zdenek Skodik) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zdenek Skodik updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3793 
 
 
 
  Improve notification of validation errors in composite fields  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zdenek Skodik 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 When validation of a field placed inside a composite field fails notifications are not working correctly.Use-case 1 - field with validator configured under composite field:- when validation fails dialog is not saved and displays the generic error on top but user is not notified at concrete field with the specific error message.Use-case 2 - required field without validator configured under composite field:- correct message is displayed ("This field is required.") but is tied to the composite field, not the concrete inner field.Use-case 3 - required field with validator configured under composite field:- if the field was blank before and validation failed, error message for required field missing ("This field is required.") is displayed. Same as in use-case 2 it's tied to whole composite field.- if the field was not blank the same behavior as in use-case 1 will occur.Correct behavior - error messages should be displayed under concrete fields and not be covered by required files missing message.Use-case 4 - making changes on the select field (which is part of composite field) caused the below exceptionSee more in video: https://jira.magnolia-cms.com/secure/attachment/32694/SelectFieldValidation.webm{code}2016-03-17 10:59:08,524 ERROR .magnolia.ui.admincentral.AdmincentralErrorHandler: AdmincentralUI has encountered an unhandled exception.com.vaadin.data.Validator$InvalidValueException: Country is requiredat com.vaadin.data.validator.AbstractValidator.validate(AbstractValidator.java:103)at com.vaadin.ui.AbstractField.validate(AbstractField.java:969)at com.vaadin.ui.AbstractField.setValue(AbstractField.java:499)at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:709)at com.vaadin.ui.ComboBox.changeVariables(ComboBox.java:674)at com.vaadin.server.communication.ServerRpcHandler.changeVariables(ServerRpcHandler.java:486)at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:305)at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:184)at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:92)at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1408)at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:350)at info.magnolia.ui.admincentral.AdmincentralVaadinServlet.service(AdmincentralVaadinServlet.java:131)at 

[magnolia-dev] [JIRA] (MGNLCE-32) Add UI tests to cover correct item/row selections using keyboard (MGNLUI-3819)

2016-03-23 Thread JIRA (on behalf of Jaroslav Simak) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jaroslav Simak created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-32 
 
 
 
  Add UI tests to cover correct item/row selections using keyboard (MGNLUI-3819)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Jaroslav Simak 
 
 
 

Created:
 

 23/Mar/16 10:28 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Jaroslav Simak 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3826) Evaluate update to Vaadin 7.6.4+

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3826 
 
 
 
  Evaluate update to Vaadin 7.6.4+  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 10:18 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Philip Mundt 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3826) Evaluate update to Vaadin 7.6.4+

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3826 
 
 
 
  Evaluate update to Vaadin 7.6.4+  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 We should evaluate an update to Vaadin {{7.6.4+}} as we are currently using {{7.4.7}}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-78) Integrate light-module-maven-plugin into templating kit

2016-03-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-78 
 
 
 
  Integrate light-module-maven-plugin into templating kit  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The plugin will take care of auto-generating the npm package during 'generate-resource' phase and deploy it to nexus during 'deploy' phase. This has been manually tested with the attached patch.Some open questions:- There's no way to re-deploy SNAPSHOT versions. Once it's deployed to nexus, we have to manually DELETE the whole package (including all versions). No-go for production, but for testing we don't mind. How to solve it is not yet decided.  (fixed in LMPLUGIN-2) - We should test it during release (staging). That's the fall-back solution if we can't solve the SNAPSHOT issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-53) Changing of filters order after migration from 5.3.5 to 5.4.4

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

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-53 
 
 
 
  Changing of filters order after migration from 5.3.5 to 5.4.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Fix Version/s:
 
 1.0.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-701) Integration options overview

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

 
 
 
 
 
 
 
 Documentation /  DOCU-701 
 
 
 
  Integration options overview  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Ruth Stocks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3823) Adapt UI registries to the new dependency on ModuleRegistry

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3823 
 
 
 
  Adapt UI registries to the new dependency on ModuleRegistry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 Since {{AbstractRegistry}} provides all the necessary functionality, the adaptation would involve adding the new c-tors and deprecating the old ones, and making sure the Registry-related tests are adapted as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3822) Prepare UI definition registries to the introduction of the definition decorators feature

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3822 
 
 
 
  Prepare UI definition registries to the introduction of the definition decorators feature  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 We need to apply several minor tweaks and fixes to makes sure that the new {{DefinitionDecorator}} feature functions properly with the UI-related {{Registries}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3825) Make sure decorators are respected in FieldTypeDefinitionRegistry#getByDefinition(..)

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3825 
 
 
 
  Make sure decorators are respected in FieldTypeDefinitionRegistry#getByDefinition(..)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 A custom legacy search method {{FieldTypeDefinitionRegistry#getByDefinition(..)}} pulls the definition providers directly out of {{RegistryMap}} and by-passes the decoration mechanism.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3824) Use I18NParentable interface duck-type check to determine whether a definition is i18n-ized

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3824 
 
 
 
  Use I18NParentable interface duck-type check to determine whether a definition is i18n-ized  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 In {{BaseDialogPresenter}} class in order to avoid applying i18n magic multiple times we used to check if an incoming definition is a proxy (=> it was i18n-framework who's proxied an object). However, such an assumption is not necessarily valid, especially since 5.4 (introduction of 'injectable' {{NamedDefinition}} interface via proxies) and 5.4.6 - definition decorators use proxies to provide fallbacks.A safer way to determine that an object has been i18n-ized is to do an {{instanceof I18NParentable}} check. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3822) Prepare UI definition registries to the introduction of the definition decorators feature

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3822 
 
 
 
  Prepare UI definition registries to the introduction of the definition decorators feature  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 8:45 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-3824) Use I18NParentable interface duck-type check to determine whether a definition is i18n-ized

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3824 
 
 
 
  Use I18NParentable interface duck-type check to determine whether a definition is i18n-ized  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 8:47 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-3825) Make sure decorators are respected in FieldTypeDefinitionRegistry#getByDefinition(..)

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3825 
 
 
 
  Make sure decorators are respected in FieldTypeDefinitionRegistry#getByDefinition(..)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 8:48 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-3823) Adapt UI registries to the new dependency on ModuleRegistry

2016-03-23 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3823 
 
 
 
  Adapt UI registries to the new dependency on ModuleRegistry  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 8:46 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-3774) Provide action which delegates to another action by node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*. -It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win. -  h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item.Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3774) Provide action which delegates to another action by node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 Our content apps allows us to manage nodes of different types.  The {{defaultAction}} property of an ActionBar definition allows to specify the name of the action executed if a user double-clicks on an item (see [here|https://documentation.magnolia-cms.com/display/DOCS/Action+bar+definition#Actionbardefinition-Actionbardefinitionproperties] in the documentation).However, this *{{defaultAction}} property is type-agnostic - we can only define an action for _all_ node types*. We thus can't map each node type to a different detail app to e.g. edit that node type. It would be *very useful to have a {{defaultAction}} property per node type*.  - It seems that Jan's "Magnolia neat tweaks" module available at https://github.com/rah003/neat-tweaks already seems to offer a Java class implementing this feature - this could actually be a quick win.    -   h4. Default use caseFor *apps with hierarchical data sets supporting folders*, we add the following default actions:* For *folders*: toggle the open state of the folder. So, if closed, we open the folder; if opened, we close the folder.* For *items*: use the current default action, i.e. we open the details sub app (aka the edit dialog) for the item.Examples of such apps are Assets, Contacts, Categorization, Security, Tours, Segments. For all other apps, we don't do anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3820) Content Apps should offer a default action per node type

2016-03-23 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Sprint:
 
 Kromeriz 36 
 
 
 

Labels:
 
 quickwin  support to-specify 
 
 
 

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-3821) Provide API for collapse node

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3821 
 
 
 
  Provide API for collapse node  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Mar/16 8:33 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3820) Content Apps should offer a default action per node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 CLONE -  Content Apps should offer a default action per node type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3820) CLONE - Content Apps should offer a default action per node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3820 
 
 
 
  CLONE - Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 

Components:
 

 content app 
 
 
 

Created:
 

 23/Mar/16 8:20 AM 
 
 
 

Fix Versions:
 

 5.4.6 
 
 
 

Labels:
 

 quickwin support to-specify 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antonín Juran 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Our content apps

[magnolia-dev] [JIRA] (MGNLUI-3774) Provide delegate action by node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide delegate action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Content Apps should offer a default Provide delegate  action  per  by  node type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3774) Provide action which delegates to another action by node type

2016-03-23 Thread on behalf of Antonín Juran 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Provide action which delegates to another action by node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Summary:
 
 Provide  delegate  action  which delegates to another action  by node type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-701) Integration options overview

2016-03-23 Thread JIRA (on behalf of Ruth Stocks) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Stocks updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-701 
 
 
 
  Integration options overview  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ruth Stocks 
 
 
 

Sprint:
 
 Docu Sprint 8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: