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

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


 
 
 
 

 
 
 

 
   
 Milan Divilek 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: 
 Milan Divilek  
 
 
Fix Version/s: 
 1.0.1  
 
 
Fix Version/s: 
 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] (MGNLUI-4157) Action bar disappears or displays incorrectly when importing a strange XML file

2017-03-02 Thread JIRA (on behalf of Hieu Nguyen Duc)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hieu Nguyen Duc created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4157  
 
 
  Action bar disappears or displays incorrectly when importing a strange XML file   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 03/Mar/17 8:14 AM  
 
 
Labels: 
 ux usability  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Hieu Nguyen Duc  
 

  
 
 
 
 

 
 This issue occurs in every subapps such as Pages, Contacts, Tours, Personas. Steps to reproduce: 
 
Export a contact in Contacts app 
Import it in Pages app or Tours app or Personas app => Action bar disappears or shows incorrect menu item 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLACTIVATION-149) Publication failing due to "(resource) locked by unfinished transaction..." errors

2017-03-02 Thread JIRA (on behalf of Mark Nottage)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Nottage created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-149  
 
 
  Publication failing due to "(resource) locked by unfinished transaction..." errors   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.2.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 03/Mar/17 4:44 AM  
 
 
Environment: 
 Magnolia Enterprise 5.2.2  Host OS: Linux 2.6.32-358.el6.x86_64 (amd64) (CentOS 6.4)  Java Version: 1.7.0_25 (build 1.7.0_25-b15)  Application server: Apache Tomcat/7.0.42  Repository: Jackrabbit 2.6.4  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Mark Nottage  
 

  
 
 
 
 

 
 We've gotten reports of publication failures from our Digital Marketing end-users for various Pages. Upon investigating the failures, typically cache purges plus Magnolia restarts seem to re-enable successful publishing, at least for a short while. But within a day or sometimes hours we get repeated reports of failing publish workflows. Typical errors reported within the Magnolia GUI are: Publication request failed for item /test04 
 
sender: workflow 
error: info.magnolia.cms.exchange.ExchangeException: info.magnolia.cms.exchange.ExchangeException: 1 error detected: Message received from subscriber: Operation not permitted, /test04 is locked by unfinished transaction. on public01 
 and Publication request failed for item /test03 
 
sender: workflow 
error: info.magnolia.cms.exchange.ExchangeException: info.magnolia.cms.exchange.ExchangeException: 2 

[magnolia-dev] [JIRA] (MGNLUI-4155) Cannot add new an asset in DAM application

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


 
 
 
 

 
 
 

 
   
 Oanh Thai Hoang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4155  
 
 
  Cannot add new an asset in DAM application   
 

  
 
 
 
 

 
Change By: 
 Oanh Thai Hoang  
 
 
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] (MTE-71) Simple MTK template demo

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-71  
 
 
  Simple MTK template demo
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Labels: 
 devwl  to-specify  
 

  
 
 
 
 

 
 
 

 
 
 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-110) Fail gracefully if custom config is missing file

2017-03-02 Thread JIRA (on behalf of Federico Grilli)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-110  
 
 
  Fail gracefully if custom config is missing file   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Story Points: 
 2 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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





[magnolia-dev] [JIRA] (MGNLUI-3769) CK editor image not updated after editing it in Assets app

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3769  
 
 
  CK editor image not updated after editing it in Assets app   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Kromeriz 86  
 

  
 
 
 
 

 
 
 

 
 
 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-144) Implement activation according to the concept

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-144  
 
 
  Implement activation according to the concept   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Kromeriz 86  
 

  
 
 
 
 

 
 
 

 
 
 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-4126) Magnolia AdminCentral not compatible with IE11 over https

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4126  
 
 
  Magnolia AdminCentral not compatible with IE11 over https   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 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] (MGNLWORKFLOW-307) Concurrent modification when persisting processes

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-307  
 
 
  Concurrent modification when persisting processes   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 86  
 

  
 
 
 
 

 
 
 

 
 
 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-4126) Magnolia AdminCentral not compatible with IE11 over https

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4126  
 
 
  Magnolia AdminCentral not compatible with IE11 over https   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Assignee: 
 Maxime Michel  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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





[magnolia-dev] [JIRA] (MGNLWORKFLOW-349) Deletion workflow message should not be identical to publishing changes

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-349  
 
 
  Deletion workflow message should not be identical to publishing changes   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 86  
 

  
 
 
 
 

 
 
 

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

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

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Kromeriz 86  
 

  
 
 
 
 

 
 
 

 
 
 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-83) JSON output suddenly changed without changing API version number

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-83  
 
 
  JSON output suddenly changed without changing API version number   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 86  
 

  
 
 
 
 

 
 
 

 
 
 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-83) JSON output suddenly changed without changing API version number

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-83  
 
 
  JSON output suddenly changed without changing API version number   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Story Points: 
 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-73) When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-73  
 
 
  When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 86  
 

  
 
 
 
 

 
 
 

 
 
 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-62) Add possibility to put context attributes to the rest response in command endpoint

2017-03-02 Thread JIRA (on behalf of Antti Hietala)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antti Hietala updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-62  
 
 
  Add possibility to put context attributes to the rest response in command endpoint   
 

  
 
 
 
 

 
 Requires a documentation update. Commands endpoint v2 allows you to configure context parameters which are then sent back in the response if the command is executed successfully. This feature is not documented in the REST API docs and it is difficult to discover on your own because the example commands that ship with the REST Service module (/modules/rest-services/rest-endpoints/commands) don't have any context attributes. Please document and provide an example.  
 

  
 
 
 
 

 
Change By: 
 Antti Hietala  
 
 
Documentation update required: 
 Yes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




[magnolia-dev] [JIRA] (MGNLUI-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

2017-03-02 Thread JIRA (on behalf of Andreas Weder)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Weder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
 Raised this to major as this is a bug the article editor depends upon.  
 

  
 
 
 
 

 
Change By: 
 Andreas Weder  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-27) Create german language property files for the MTE components

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-27  
 
 
  Create german language property files for the MTE components   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-91) Move CLI "texts" into a common resource bundle file (i18n)

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-91  
 
 
  Move CLI "texts" into a common resource bundle file (i18n)   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLMAIL-66) Using Gmail as a mail client requires enabling a less secure option on your account

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Mail Module /  MGNLMAIL-66  
 
 
  Using Gmail as a mail client requires enabling a less secure option on your account   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 8  
 
 
Labels: 
 support  to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-3242) Warn on deletion of page with modified children

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3242  
 
 
  Warn on deletion of page with modified children   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-322) Location fragment should be escaped

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-322  
 
 
  Location fragment should be escaped   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 framework tech-debt  to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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





[magnolia-dev] [JIRA] (MGNLWORKFLOW-349) Deletion workflow message should not be identical to publishing changes

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-349  
 
 
  Deletion workflow message should not be identical to publishing changes   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 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] (DOCU-948) Update Option Group and Twin Column field pages

2017-03-02 Thread JIRA (on behalf of Ruth Stocks)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ruth Stocks updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-948  
 
 
  Update Option Group and Twin Column field pages   
 

  
 
 
 
 

 
Change By: 
 Ruth Stocks  
 
 
Sprint: 
 Docu Sprint 19  
 

  
 
 
 
 

 
 
 

 
 
 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-91) Move CLI "texts" into a common resource bundle file (i18n)

2017-03-02 Thread JIRA (on behalf of Ilgun Ilgun)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-91  
 
 
  Move CLI "texts" into a common resource bundle file (i18n)   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 h4. IssueAt the moment, all texts addressed to CLI users are widespread among command-js-files.I propose to move these texts into one resource bundle file (most probably a json file).h4. Motivationh5. docs maintenancetbh - my first motivation was rather selfish and documentation centric. With such a  commmon  common  resource bundle file - i could read it and use with a Confluence macro. This would in the long run reduce the amount of work of maintenance of the (CLI) documentation.h5. 18nI do not expect that we will create translations for other languages in the near future - however - it doesn't hurt to make it 18n ready now - but it may hurt in future.h5. Ease of linguistic reviewDuring the NOW development we have seen that it is impossible for a linguist to make a UI text review, if the texts are hardcoded and widespread among code files. But to have the texts in one single (json) file makes it very easy for a non developer to review the text and to polish them. (Guys as Martin or Julie could do such a text review.)h4. etc.I already had a quick SKYPE call with [~robertkowalski] whether this is feasible and common practice in the CLI / NPM world too - which he confirmed.Robert also has mentioned, that at the moment many files are touched anyway. So - i18n-ization could be done additionally while fixing / improving other things. (Just make sure to have separate commits.)h4. KeysIf the ticket will be tackled - we would have to find a suitable naming convention for good keys.I could propose here some ideas - if desired - since i already was thinking about a bit.However - other guys have a lot of experience in this topic too.Basically i would expect something like$commandName.$topic, e.g. {{create-page.sucess-next-step-tip}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

[magnolia-dev] [JIRA] (DOCU-948) Update Option Group and Twin Column field pages

2017-03-02 Thread JIRA (on behalf of Ruth Stocks)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ruth Stocks created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-948  
 
 
  Update Option Group and Twin Column field pages   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Ruth Stocks  
 
 
Created: 
 02/Mar/17 10:46 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Ruth Stocks  
 

  
 
 
 
 

 
 See Antti's comment on https://documentation.magnolia-cms.com/display/DOCS/Option+group+field  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

[magnolia-dev] [JIRA] (MGNLWORKFLOW-349) Deletion workflow message should not be identical to publishing changes

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-349  
 
 
  Deletion workflow message should not be identical to publishing changes   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Story Points: 
 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-83) JSON output suddenly changed without changing API version number

2017-03-02 Thread JIRA (on behalf of Antti Hietala)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antti Hietala updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-83  
 
 
  JSON output suddenly changed without changing API version number   
 

  
 
 
 
 

 
Change By: 
 Antti Hietala  
 
 
Assignee: 
 Philip Mundt  
 

  
 
 
 
 

 
 
 

 
 
 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-83) JSON output suddenly changed without changing API version number

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


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-83  
 
 
  JSON output suddenly changed without changing API version number   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-17) Allow to use YAML as bootstrap format

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


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-17  
 
 
  Allow to use YAML as bootstrap format   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Labels: 
 selected-for-backlog  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-17) Allow to use YAML as bootstrap format

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


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-17  
 
 
  Allow to use YAML as bootstrap format   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Labels: 
 selected-for-backlog  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-17) Allow to use YAML as bootstrap format

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


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-17  
 
 
  Allow to use YAML as bootstrap format   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Labels: 
 selected-for-backlog  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-17) Allow to use YAML as bootstrap format

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


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-17  
 
 
  Allow to use YAML as bootstrap format   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Sprint: 
 Kromeriz 85  
 
 
Labels: 
 selected-for-backlog  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-17) Allow to use YAML as bootstrap format

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


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-17  
 
 
  Allow to use YAML as bootstrap format   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 
 
Labels: 
 selected-for-backlog  
 

  
 
 
 
 

 
 
 

 
 
 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: