[magnolia-dev] [JIRA] (MCTP-4) Register non-existing namespaces

2017-02-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Espen Jervidalo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Types Project /  MCTP-4  
 
 
  Register non-existing namespaces
 

  
 
 
 
 

 
Change By: 
 Espen Jervidalo  
 

  
 
 
 
 

 
 See https://git.magnolia-cms.com/projects/MODULES/repos/magnolia-content-types/pull-requests/3/overviewJackrabbit throws exception if you try to register nodetypes with yet unknown namespace. Namespaces need to be register with an URI. What URI should be used?Besides the exception that is thrown is swallowed. That should definitely not be the case. I'll create a follow up, as we need this commit for the others to apply.{code}info.magnolia.repository.DefaultRepositoryManager#registerNameSpacesAndNodeTypesinfo.magnolia.jackrabbit.ProviderImpl#registerNamespacejavax.jcr.NamespaceRegistry#registerNamespace{code}  
 

  
 
 
 
 

 
 
 

 
 
 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] (MCTP-4) Register non-existing namespaces

2017-02-23 Thread JIRA (on behalf of Espen Jervidalo) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Espen Jervidalo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Types Project /  MCTP-4  
 
 
  Register non-existing namespaces
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 23/Feb/17 5:08 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Espen Jervidalo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4151) Adjust tests to changes done in MAGNOLIA-5209

2017-02-23 Thread JIRA (on behalf of Milan Divilek) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Milan Divilek updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4151  
 
 
  Adjust tests to changes done in MAGNOLIA-5209   
 

  
 
 
 
 

 
Change By: 
 Milan Divilek  
 
 
Story Points: 
 0 2  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-107) tab-completion should give success message stating where it has been installed.

2017-02-23 Thread JIRA (on behalf of Robert Kowalski) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Kowalski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-107  
 
 
  tab-completion should give success message stating where it has been installed.   
 

  
 
 
 
 

 
Change By: 
 Robert Kowalski  
 
 
Story Points: 
 1  
 
 
Assignee: 
 Robert Kowalski  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-108) Improve README prototype to make modules easier to understand

2017-02-23 Thread JIRA (on behalf of Robert Kowalski) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Kowalski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-108  
 
 
  Improve README prototype to make modules easier to understand   
 

  
 
 
 
 

 
Change By: 
 Robert Kowalski  
 
 
Story Points: 
 1  
 
 
Assignee: 
 Robert Kowalski  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4133) Warn user if using drag & drop in sorted tree

2017-02-23 Thread JIRA (on behalf of Milan Divilek) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Milan Divilek updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4133  
 
 
  Warn user if using drag & drop in sorted tree   
 

  
 
 
 
 

 
Change By: 
 Milan Divilek  
 
 
Fix Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

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

2017-02-23 Thread JIRA (on behalf of Oanh Thai Hoang) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oanh Thai Hoang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 1.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 23/Feb/17 1:01 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Oanh Thai Hoang  
 

  
 
 
 
 

 
 Since 5.5.2, Magnolia is using all Resteasy v 3.0.19.Final but library resteasy-multipart-provider that our project is currently using has one bug (https://issues.jboss.org/browse/RESTEASY-1201). This bug is fixed at Resteasy v 3.0.20.Final.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLACTIVATION-148) Root site content is locked, can not publish and use 100% CPU resource in Production servr

2017-02-23 Thread JIRA (on behalf of Bao Quach) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bao Quach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-148  
 
 
  Root site content is locked, can not publish and use 100% CPU resource in Production servr   
 

  
 
 
 
 

 
Change By: 
 Bao Quach  
 

  
 
 
 
 

 
 Hi MagnoliaMy name is Bao Quach, I am senior Technical Lead Pepper.I have user account of "bquach" and email of bqu...@pepper.com.au, but I  can not login or reset password. So Iogin using my personal account.Pepper have Enterprise support with Magnolia version 5.4.7.I have major issue in 2 Production web public instance servers.The web public instance servers magnolia-activation.log.* showsINFO   info.magnolia.module.activation.ReceiveFilter 23.02.2017 13:43:54 -- Content /pepper-au is locked. Will retry 10 more times.When we try to public a campaign page.The root /pepper-au is locked and can not be publish.The web public instance servers use 100 % CPU and which can not be access to public.We try to restart but did not fixed the problem. The Pepper website had outage around after lunch today, We need your help to resolve this asap . I have CIO and Pepper IT are not happy with the issue.I have disable publishing from authoring server to production web public instance servers for now.Please contact me on 61-415456565.I have attached the logs for your to investigate the issue.Regards, Bao  
 

  
 
 
 
 

 
 
 

 
 
 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

2017-02-23 Thread 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

2017-02-23 Thread 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

2017-02-23 Thread 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] (NPMCLI-108) Improve README prototype to make modules easier to understand

2017-02-23 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-108  
 
 
  Improve README prototype to make modules easier to understand   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 23/Feb/17 12:00 PM  
 
 
Fix Versions: 
 2.0  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 The readme should include some comments and more suggestions in order to guide devs to make more useful and consistant readme files. In particular this will encourage better reuse and sharing of modules.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4102) Wrongly replacing of html links in i18n messages

2017-02-23 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4102  
 
 
  Wrongly replacing of html links in i18n messages   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Created according to SUPPORT-6926, please reference to linked ticket for detail description and discussion.If you want to render a i18n message which contains a html link, the link will be replaced by __.It is reproducible on demoauthor instance. Open the groovy console and execute the following statement.{noformat}info.magnolia.objectfactory.Components.getComponent(info.magnolia.i18nsystem.TranslationService.class).translate(new info.magnolia.i18nsystem.FixedLocaleProvider(Locale.ENGLISH), ["pages.noAvailableTemplatesAlert.createTemplateLink"] as String[]) {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 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, 

[magnolia-dev] [JIRA] (MGNLACTIVATION-140) Problem with order when nodetypes are not the same

2017-02-23 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-140  
 
 
  Problem with order when nodetypes are not the same   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLACTIVATION-148) Root site content is locked, can not publish and use 100% CPU resource in Production servr

2017-02-23 Thread JIRA (on behalf of Bao Quach) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bao Quach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-148  
 
 
  Root site content is locked, can not publish and use 100% CPU resource in Production servr   
 

  
 
 
 
 

 
Change By: 
 Bao Quach  
 
 
Attachment: 
 p_aut.zip  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-210) Change component variants parent node type to mgnl:componentVariants

2017-02-23 Thread on behalf of Roman Kovařík 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-210  
 
 
  Change component variants parent node type to mgnl:componentVariants   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Sprint: 
 Kromeriz 85  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3741) Admin Central unaccessible after unhandled exception

2017-02-23 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3741  
 
 
  Admin Central unaccessible after unhandled exception   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Kromeriz 85  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-148) Root site content is locked, can not publish and use 100% CPU resource in Production servr

2017-02-23 Thread JIRA (on behalf of Bao Quach) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bao Quach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-148  
 
 
  Root site content is locked, can not publish and use 100% CPU resource in Production servr   
 

  
 
 
 
 

 
Change By: 
 Bao Quach  
 
 
Attachment: 
 p2.zip  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-148) Root site content is locked, can not publish and use 100% CPU resource in Production servr

2017-02-23 Thread JIRA (on behalf of Bao Quach) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bao Quach created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-148  
 
 
  Root site content is locked, can not publish and use 100% CPU resource in Production servr   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.4.5  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 p1.zip  
 
 
Created: 
 23/Feb/17 10:54 AM  
 
 
Environment: 
 Linux  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Bao Quach  
 

  
 
 
 
 

 
 Hi Magnolia My name is Bao Quach, I am senior Technical Lead Pepper. I have user account of "bquach" and email of bqu...@pepper.com.au, but I can not login or reset password. So Iogin using my personal account. Pepper have Enterprise support with Magnolia version 5.4.7. I have major issue in 2 Production web public instance servers. The web public instance servers magnolia-activation.log.* shows INFO info.magnolia.module.activation.ReceiveFilter 23.02.2017 13:43:54 – Content /pepper-au is locked. Will retry 10 more times. When we try to public a campaign page. The root /pepper-au is locked and can not be publish. The web public instance servers use 100 % CPU and which can not be access to public. We try to restart but did not fixed the problem. We need your help to resolve this asap. I have CIO and Pepper IT are not happy with the issue. I have disable publishing from authoring server to production web public instance servers for now. Please contact me on 61-415456565. I have attached the logs for your to investigate the issue. Regards, Bao

[magnolia-dev] [JIRA] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

2017-02-23 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Kromeriz 85  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

2017-02-23 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Assignee: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

2017-02-23 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Fix Version/s: 
 5.4.12  
 
 
Fix Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-3571) More subtle appearance of language switcher in dialogs

2017-02-23 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evzen Fochr updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Evzen Fochr  
 
 
Assignee: 
 Evzen Fochr  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4131) Prevent triggering actionbar actions twice by doubleclick

2017-02-23 Thread JIRA (on behalf of Jaroslav Simak) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jaroslav Simak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4131  
 
 
  Prevent triggering actionbar actions twice by doubleclick   
 

  
 
 
 
 

 
Change By: 
 Jaroslav Simak  
 
 
Story Points: 
 8 5  
 

  
 
 
 
 

 
 
 

 
 
 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: