[magnolia-dev] [JIRA] (JSMODELS-8) JavascriptObjectFactory should expose HTMLEscapingAggregationState to templates

2017-06-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-8  
 
 
  _javascript_ObjectFactory should expose HTMLEscapingAggregationState to templates   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jaroslav Simak  
 
 
Created: 
 01/Jun/17 7:18 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Federico Grilli  
 

  
 
 
 
 

 
 
 

 
 
 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] (JSMODELS-8) JavascriptObjectFactory should expose HTMLEscapingAggregationState to templates

2017-06-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-8  
 
 
  _javascript_ObjectFactory should expose HTMLEscapingAggregationState to templates   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 See relate issue MAGNOLIA-6448  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

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

2017-06-01 Thread JIRA (on behalf of Richard Gange) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Gange updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-1034) Hint: Force cache flushing after installation of SNAPSHOT or site release

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1034  
 
 
  Hint: Force cache flushing after installation of SNAPSHOT or site release   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 5:29 PM  
 
 
Labels: 
 mnow  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christoph Meier  
 

  
 
 
 
 

 
 When adding a developer SNAPSHOT or installing a site release - actually the cache on the public contexts should be flushed - but it is not happening. (See SUGGEST-35) The user may be confused. We may should add a hint concerning this "issue" to avoid SUPPORT tickets in the future.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (JSMODELS-4) Provide samples of how to use JS models

2017-06-01 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-4  
 
 
  Provide samples of how to use JS models   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Kromeriz 99  
 

  
 
 
 
 

 
 
 

 
 
 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-83) Bcrypt the password value in the SMTP configuration

2017-06-01 Thread on behalf of Roman Kovařík 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Mail Module /  MGNLMAIL-83  
 
 
  Bcrypt the password value in the SMTP configuration   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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-929) Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-929  
 
 
  Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 The tutorial should replace the current hello magnolia tutorial. [Hello Magnolia|https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia]has become old - it originates from the days of the 5.4 release.Be aware that there is also another, smaller, newer version called[Hello Magnolia for front-end developers|https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia+for+front-end+developers]h4. Things which are clear so far- Use CLI wherever it makes sense- There is no more _"If you use CLI, do it that way. If not using CLI, do it this way"._ Avoid explaining the same thing with 2 approaches.- Keep the existing example(s) whenever possible; there is no reason to figure out new ones.- Example wise the following things are clear:-- Create a new light module-- Create a new page template-- Create a new component template - to be used on the new page template(!) Even if we will use CLI wherever possible - the main focus of this tutorial is - "Getting started with Magnolia"- Understanding some core principles of templating - Using CLI is _*not*_ the main aim - CLI is just a means to an end.   h4. Things which have not yet been decided:- Should we again use a static prototype file as a precursor of the new page template?-- It is still a very valid use case.-- It includes a lot of manual work - which is however helpful to learn magnolia-- It is still possible to do the static prototype first ... then creating a page template via script ... but then adapting the per script generated files by copying parts of the static prototype file- How deep do we go in explaining things which are done via CLI commands, which we have explained "in detail" in the old version  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (DOCU-929) Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-929  
 
 
  Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 The tutorial should replace the current hello magnolia tutorial. [Hello Magnolia|https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia]has become old - it originates from the days of the 5.4 release.Be aware that there is also another, smaller, newer version called[Hello Magnolia for front-end developers|https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia+for+front-end+developers]h4. Things which are clear so far- Use CLI wherever it makes sense- There is no more  _  "If you use CLI, do it that way. If not using CLI, do it this way". _  Avoid explaining the same thing with 2 approaches.- Keep the existing example(s) whenever possible; there is no reason to figure out new ones.- Example wise the following things are clear:-- Create a new light module-- Create a new page template-- Create a new component template - to be used on the new page template (!) Even if we will use CLI wherever possible - the main focus of this tutorial is - "Getting started with Magnolia"- Understanding some core principles of templating h4. Things which have not yet been decided:- Should we again use a static prototype file as a precursor of the new page template?-- It is still a very valid use case.-- It includes a lot of manual work - which is however helpful to learn magnolia-- It is still possible to do the static prototype first ... then creating a page template via script ... but then adapting the per script generated files by copying parts of the static prototype file- How deep do we go in explaining things which are done via CLI commands, which we have explained "in detail" in the old version  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (DOCU-929) Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-929  
 
 
  Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 The tutorial should replace the current hello magnolia tutorial. [Hello Magnolia|https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia]has become old - it originates from the days of the 5.4 release.Be aware that there is also another, smaller, newer version called[Hello Magnolia for front-end developers|https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia+for+front-end+developers] The replacement for the old Hello Magnolia should rely on h4. Things which are clear so far- Use  CLI  wherever it makes sense- There is no more "If you use CLI, do it that way. If not using CLI, do it this way". Avoid explaining the same thing with 2 approaches.- Keep the existing example(s) whenever possible; there is no reason  to  install magnolia and create  figure out new ones.- Example wise the following things are clear:-- Create  a  working  new  light module . The benefits of fast light dev using Magnolia CLI should -- Create a new page template-- Create a new component template - to  be  showcased  used on the new page templateh4 .  Specific CLI [prototypes|https  Things which have not yet been decided : //documentation - Should we again use a static prototype file as a precursor of the new page template?-- It is still a very valid use case . -- It includes a lot of manual work - which is however helpful to learn magnolia  - cms.com/display/DOCS/Magnolia+CLI#MagnoliaCLI - Prototypes] for  It is still possible to do the static prototype first ... then creating a page  template  and dialog definitions could/should be created  via script . .. but then adapting the per script generated files by copying parts of the static prototype file- How deep do we go in explaining things which are done via CLI commands, which we have explained "in detail" in the old version  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (TASKMGMT-28) Avoid creating User throwaway objects in TaskManager API

2017-06-01 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Task Management /  TASKMGMT-28  
 
 
  Avoid creating User throwaway objects in TaskManager API   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 1.2.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 2:33 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Federico Grilli  
 

  
 
 
 
 

 
 Upon logging into AdminCentral, when Pulse initialises, the following method gets called several times getTasksAmountByUserAndStatus:192, DefaultTasksManager (info.magnolia.task) which, in turn, triggers getUser:264, MgnlUserManager (info.magnolia.cms.security).  This results in the same user instance being created like 10 times. Probably not much of a overhead and in any case the instance is local to a method so it will be thrown away immediately, still there could be room for some improvement. Could be probably fixed if the TaskMgmt API would pass around the User object instead of just the user id, but that's quite a change on its own. If we passed the User object to TaskManager - we would be able to re-use User from MgnlContext.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (DOCU-888) Tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 NOW documentation users are sent to CORE doc module pages because we don't want to duplicate content from CORE in NOW.  I suggest adding At least tag the module pages with the label {{mnow}}.Not sure whether we need  a "badge"/ label/ info box   to , cloudy icon, etc. pp on  the CORE  module  pages  that apply . We have  to  NOW to make  wonder how obvious  it  clear  should be  for  the readers of the CORE doc which modules are available on  NOW  users that this content applies to them ( and  that if there is no "badge", the content does  which  not  apply to them) .  Could we add the cloudy icon to CORE pages for example For me  ( see attachment cmeier ) ?   this is rather a technical labelling to be reused on the NOW docs.   Test generating a list of tagged CORE content in NOW docu space. Name the label {{mnow}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (DOCU-888) Tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Summary: 
 Think of a way to tag Tag  CORE module pages that are included in NOW  
 

  
 
 
 
 

 
 
 

 
 
 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-929) Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent

2017-06-01 Thread on behalf of Martin Drápela 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Drápela updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-929  
 
 
  Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent   
 

  
 
 
 
 

 
Change By: 
 Martin Drápela  
 
 
Assignee: 
 Martin Drápela  
 

  
 
 
 
 

 
 
 

 
 
 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-1023) Release notes for 5.4.13

2017-06-01 Thread on behalf of Martin Drápela 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Drápela updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1023  
 
 
  Release notes for 5.4.13   
 

  
 
 
 
 

 
Change By: 
 Martin Drápela  
 
 
Assignee: 
 Martin Drápela  
 

  
 
 
 
 

 
 
 

 
 
 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-929) Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-929  
 
 
  Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Story Points: 
 13  
 

  
 
 
 
 

 
 
 

 
 
 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-1032) Planning the NMP wrap up tutorial

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1032  
 
 
  Planning the NMP wrap up tutorial   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
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] (DOCU-1032) Planning the NMP wrap up tutorial

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1032  
 
 
  Planning the NMP wrap up tutorial   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 Get a clear idea what we will do here.Define subtasks. During planning, at least:- Define the  examples, etc.  example- Define the structure  
 

  
 
 
 
 

 
 
 

 
 
 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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 

  
 
 
 
 

 
 NOW documentation users are sent to CORE doc module pages because we don't want to duplicate content from CORE in NOW. I suggest adding a "badge"/label/info box  to the CORE module pages that apply to NOW to make it clear for NOW users that this content applies to them (and that if there is no "badge", the content does not apply to them). Could we add the cloudy icon to CORE pages for example (see attachment)?Test generating a list of tagged CORE content in NOW docu space.  
 

  
 
 
 
 

 
 
 

 
 
 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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 
 
Labels: 
 mnow  
 

  
 
 
 
 

 
 
 

 
 
 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-1023) Release notes for 5.4.13

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1023  
 
 
  Release notes for 5.4.13   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 NOW documentation users are sent to CORE doc module pages because we don't want to duplicate content from CORE in NOW. I suggest adding a "badge"/label/info box  to the CORE module pages that apply to NOW to make it clear for NOW users that this content applies to them (and that if there is no "badge", the content does not apply to them). Could we add the cloudy icon to CORE pages for example (see attachment)? Test generating a list of tagged CORE content in NOW docu space. Name the label {{mnow}}  
 

  
 
 
 
 

 
 
 

 
 
 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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Labels: 
 mnow  
 

  
 
 
 
 

 
 
 

 
 
 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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 
 
Labels: 
 mnow  
 

  
 
 
 
 

 
 
 

 
 
 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-1032) Planning the tutorial

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1032  
 
 
  Planning the tutorial   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 
 
Sprint: 
 Docu Sprint 26  
 

  
 
 
 
 

 
 
 

 
 
 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-888) Think of a way to tag CORE module pages that are included in NOW

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-888  
 
 
  Think of a way to tag CORE module pages that are included in NOW   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 26  
 

  
 
 
 
 

 
 
 

 
 
 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-1032) Planning the NMP wrap up tutorial

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1032  
 
 
  Planning the NMP wrap up tutorial   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 
 
Summary: 
 Planning the  NMP wrap up  tutorial  
 

  
 
 
 
 

 
 
 

 
 
 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-1033) Planning rewriting "Hello Magnolia"

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1033  
 
 
  Planning rewriting "Hello Magnolia"   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 1:16 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christoph Meier  
 

  
 
 
 
 

 
 
 

 
 
 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-1032) Planning the tutorial

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1032  
 
 
  Planning the tutorial   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 1:11 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christoph Meier  
 

  
 
 
 
 

 
 Get a clear idea what we will do here. Define subtasks. Define the examples, etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (DOCU-1032) Planning the tutorial

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1032  
 
 
  Planning the tutorial   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 
 
Parent: 
 DOCU-747  
 
 
Issue Type: 
 Sub-task Task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (DOCU-929) Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-929  
 
 
  Rewrite or replace (old) 'Hello Magnolia' using CLI to full extent   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 26  
 

  
 
 
 
 

 
 
 

 
 
 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-747) NPM - wrap up

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-747  
 
 
  NPM - wrap up   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Issue Type: 
 Task Story  
 

  
 
 
 
 

 
 
 

 
 
 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-1031) Release notes for 5.5.5

2017-06-01 Thread on behalf of Martin Drápela 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Drápela created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1031  
 
 
  Release notes for 5.5.5   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 12:53 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Martin Drápela  
 

  
 
 
 
 

 
 Create 5.5.5 Release Notes. Tracking: https://docs.google.com/spreadsheets/d/1RPuH0sQbLNXHwFhNg8FjtZ-tj2uUYaTAdDW4XZUVHLk/edit?pref=2=1#gid=182815287 Changelog: https://jira.magnolia-cms.com/issues/?filter=16856 RN required: https://jira.magnolia-cms.com/issues/?filter=16865 RN page: https://documentation.magnolia-cms.com/display/DOCS/Release+notes+for+Magnolia+CORE+5.5.5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-4216) Double clicking on the Types column in the JCR browser makes node type values disappear

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4216  
 
 
  Double clicking on the Types column in the JCR browser makes node type values disappear   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 11:49 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Julie Legendre  
 

  
 
 
 
 

 
 To reproduce: 
 
In the Magnolia demo, open Tools > JCR. For example: https://demo.magnolia-cms.com/.magnolia/admincentral#app:jcr-browser:browser;/travel:treeview: 
Double click on a node type value in the Types column. Result: All the node type values in the column disappear (only String/Boolean remain displayed). 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4215) Adjust unsupported browser info message

2017-06-01 Thread JIRA (on behalf of Cedric Reichenbach) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cedric Reichenbach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4215  
 
 
  Adjust unsupported browser info message   
 

  
 
 
 
 

 
Change By: 
 Cedric Reichenbach  
 
 
Original Estimate: 
 1m  
 
 
Remaining Estimate: 
 1m  
 

  
 
 
 
 

 
 
 

 
 
 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-1021) Reflect latest changes on the 'content-editor' modules

2017-06-01 Thread JIRA (on behalf of Julie Legendre) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1021  
 
 
  Reflect latest changes on the 'content-editor' modules   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 

  
 
 
 
 

 
 This is rather a "wild card" - however we expect some changes on these modules.  For a list of dev tickets tackled since the last doc update, see: https://jira.magnolia-cms.com/issues/?filter=16862---(added by Julie  on 29/05) Doc update needed for VI, release week after next? See recording of demo from PD team meeting 29/05.- Update doc about the "outline" to describe multiple collapsible composite fields.- Add the "Link to Magnolia item" option in block chooser bar to the Stories app page.- To configure the apps you can link to, in the content definition add:linkableApps: + appsNB: Plugin only available in the content-editor (not in normal ck editor YET).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-4215) Adjust unsupported browser info message

2017-06-01 Thread JIRA (on behalf of Cedric Reichenbach) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cedric Reichenbach created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4215  
 
 
  Adjust unsupported browser info message   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Jun/17 10:58 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Cedric Reichenbach  
 

  
 
 
 
 

 
 Currently, the message still suggests using IE 8+, even though we only support IE 11 at by now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (DOCU-1023) Release notes for 5.4.13

2017-06-01 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1023  
 
 
  Release notes for 5.4.13   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 26  
 

  
 
 
 
 

 
 
 

 
 
 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-215) Allow to use YAML export in Tours app

2017-06-01 Thread on behalf of Roman Kovařík 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-215  
 
 
  Allow to use YAML export in Tours app   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCE-38) Add more Log Tools UI tests

2017-06-01 Thread JIRA (on behalf of Maxime Michel) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-38  
 
 
  Add more Log Tools UI tests   
 

  
 
 
 
 

 
Change By: 
 Maxime Michel  
 
 
Story Points: 
 3 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: