[magnolia-dev] [JIRA] (MGNLUI-4025) Total Dialog Validation Error Messages and Total Figure Not Synchronised

[JIRA (on behalf of Chris Jennings)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Jennings created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4025 
 
 
 
  Total Dialog Validation Error Messages and Total Figure Not Synchronised  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 23/Sep/16 8:45 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Chris Jennings 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
This may be timely as I see MGNLUI-2542 has been looked at in June. 
I have attempted to build a system for cross-field validation ensuring that two or more fields contain distinct values. I have found that error messages are shown to the user when there is a value returned from AbstractField.getErrorMessage() but the total errors in the dialog header is calculated by re-running isValid on each item - this happens within info.magnolia.ui.vaadin.form.Form.isValid(). 
In my case, this means that a field that was valid when first evaluated but becomes invalid because of a clash will not show an error message but 

[magnolia-dev] [JIRA] (MGNLUI-3767) Use resources (fonts, images) from core module in defaultMagnoliaLoginForm

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3767 
 
 
 
  Use resources (fonts, images) from core module in defaultMagnoliaLoginForm  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Labels:
 
 estimate-pm-5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Labels:
 
 selected-for-backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Sprint:
 
 Basel 62 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCACHE-148) Update module in order to use newer Swagger version defined in REST (and imported through depMgmt)

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-148 
 
 
 
  Update module in order to use newer Swagger version defined in REST (and imported through depMgmt)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Sprint:
 
 Basel 62 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCACHE-148) Update module in order to use newer Swagger version defined in REST (and imported through depMgmt)

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-148 
 
 
 
  Update module in order to use newer Swagger version defined in REST (and imported through depMgmt)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 

Created:
 

 23/Sep/16 3:35 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCACHE-147) Cache filter is not triggered for forwards

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-147 
 
 
 
  Cache filter is not triggered for forwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 The cache filter is currently triggered only once per request (it extends {{OncePerRequestAbstractMgnlFilter}}). This is currently an  issuer  issue  for MSITEMESH-13 since the cache is not triggered for forwards.Instead of extending {{OncePerRequestAbstractMgnlFilter}}, we can provide a voter which does the function so we can replace it with a custom one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCACHE-147) Cache filter is not triggered for forwards

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-147 
 
 
 
  Cache filter is not triggered for forwards  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Roman Kovařík 
 
 
 

Components:
 

 cache core 
 
 
 

Created:
 

 23/Sep/16 1:51 PM 
 
 
 

Fix Versions:
 

 5.4.7 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 
The cache filter is currently trigger only once per request (it extends OncePerRequestAbstractMgnlFilter).  This is currently an issuer for MSITEMESH-13 since the cache is not triggered for forwards. Instead of extending OncePerRequestAbstractMgnlFilter, we can provide a voter which does the function so we can replace it with a custom one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLCACHE-147) Cache filter is not triggered for forwards

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-147 
 
 
 
  Cache filter is not triggered for forwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 The cache filter is currently  trigger  triggered  only once per request (it extends {{OncePerRequestAbstractMgnlFilter}}). This is currently an issuer for MSITEMESH-13 since the cache is not triggered for forwards.Instead of extending {{OncePerRequestAbstractMgnlFilter}}, we can provide a voter which does the function so we can replace it with a custom one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Component/s:
 
 p13n 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLGROOVY-152) Update Vaadin version to 7.7.0

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-152 
 
 
 
  Update Vaadin version to 7.7.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLFORUM-293) Remove Forum and Admin-Legacy from the bundle

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Forum Module /  MGNLFORUM-293 
 
 
 
  Remove Forum and Admin-Legacy from the bundle  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4024) It is possible to create 'same name' siblings

[JIRA (on behalf of Bradley Andersen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bradley Andersen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4024 
 
 
 
  It is possible to create 'same name' siblings   
 
 
 
 
 
 
 
 
 

Change By:
 
 Bradley Andersen 
 
 
 

Support Score:
 
 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4024) It is possible to create 'same name' siblings

[JIRA (on behalf of Bradley Andersen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bradley Andersen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4024 
 
 
 
  It is possible to create 'same name' siblings   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Screen Shot 2016-09-23 at 11.28.11.png, Screen Shot 2016-09-23 at 11.28.33.png, Screen Shot 2016-09-23 at 11.33.10.png, Screen Shot 2016-09-23 at 11.41.46.png 
 
 
 

Created:
 

 23/Sep/16 11:55 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Bradley Andersen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
It is possible to create 'same-name' siblings, at least in the Pages app, and at least in Magnolia 5.4.8. Please see attached images, and connected SUPPORT-6660. 
While technically the siblings do not have the same name in the system ('page', 'page[2]' will be created, for example), the user is provided no visual cues to that effect (sees 'page', 'page'), and is permitted to create an Nth page with the 'same name' as an existing page. 
 
 

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 {{magnolia-travel-demo-component-personalization}} uses the _javascript_ cookie library [https://github.com/js-cookie/js-cookie] to set/remove tour type preferences.  Antti would like this mechanism to be documented.Starting with {{Magnolia 5.4.9}} the {{travel-demo-theme}} ships with https://github.com/js-cookie/js-cookie, a nifty _javascript_ library to handle... cookies (duh!). Its usage is quite straightforward and it's well explained in their docs.  The library also handles browsers' quirks and spare us with some boilerplate coding, so that's why it was introduced instead of working directly with HTTP cookies.  In particular, we use it to achieve the functionality required by {{magnolia-travel-demo-component-personalization}} where, based on the visitor's choice in the travel home page, we show featured tours of their favorite tour type.Here's how we use it.To set a cookie named {{tourType}} we use this simple function{code}  
   function setTourTypeAsCookie(tourType) {
[#-- Always remove cookie when we're about to set it or we might end up with multiple cookies with the same name. --]
Cookies.remove('tourType');
...
Cookies.set('tourType', tourType)
}
{code}And of course its counterpart to remove a {{tourType}} cookie{code}
function removeTourTypePreference() {
Cookies.remove('tourType')
...
}
{code}Finally, a Freemarker function is used to detect a cookie with a given name in the request and return its value{code}[#function detectCookie cookieName] [#if ctx.request.cookies?has_content][#list ctx.request.cookies as cookie][#if cookie.name == cookieName][#return cookie.value][/#if][/#list][/#if][#return ""][/#function]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

  

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Labels:
 
 backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Labels:
 
 selected-for-backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Labels:
 
 backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Sprint:
 
 Basel 62 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 {{magnolia-travel-demo-component-personalization}} uses the _javascript_ cookie library [https://github.com/js-cookie/js-cookie] to set/remove tour type preferences.  Antti would like this mechanism to be documented.Starting with {{Magnolia 5.4.9}} the {{travel-demo-theme}} ships with https://github.com/js-cookie/js-cookie, a nifty _javascript_ library to handle... cookies (duh!). Its usage is quite straightforward and it's well explained in their docs. In particular, we use it to achieve the functionality required by {{magnolia-travel-demo-component-personalization}} where, based on the visitor's choice in the travel home page, we show featured tours of their favorite tour type.Here's how we use it.To set a cookie named {{tourType}} we use this simple function{code}  
   function setTourTypeAsCookie(tourType) {
[#-- Always remove cookie when we're about to set it or we might end up with multiple cookies with the same name. --]
Cookies.remove('tourType');
...
Cookies.set('tourType', tourType)
}
{code}And of course its counterpart to remove a {{tourType}} cookie{code}
function removeTourTypePreference() {
Cookies.remove('tourType')
...
}
{code}Finally, a Freemarker function is used to detect  cookies  a cookie  with a given name in the request    and return its value   {code}[#function detectCookie cookieName] [#if ctx.request.cookies?has_content][#list ctx.request.cookies as cookie][#if cookie.name == cookieName][#return cookie.value][/#if][/#list][/#if][#return ""][/#function]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 {{magnolia-travel-demo-component-personalization}} uses the _javascript_ cookie library [https://github.com/js-cookie/js-cookie] to set/remove tour type preferences.  Antti would like this mechanism to be documented.Starting with {{Magnolia 5.4.9}} the {{travel-demo-theme}} ships with https://github.com/js-cookie/js-cookie, a nifty _javascript_ library to handle... cookies (duh!). Its usage is quite straightforward and it's well explained in their docs. In particular, we use it to achieve the functionality required by {{magnolia-travel-demo-component-personalization}} where, based on the visitor's choice in the travel home page, we show featured tours of their favorite tour type.Here's how we use it.To set a cookie named {{tourType}} we use this simple function at{{demo-projects/enterprise/magnolia-travel-demo-component-personalization/src/main/resources/travel-demo-component-personalization/templates/components/personalizedTourTypeTeaserRow.ftl}}{code}   function setTourTypeAsCookie(tourType) {[#-- Always remove cookie when we're about to set it or we might end up  with multiple cookies with the same name. The empty path means remove for the whole site not for some specific path.  --]Cookies.remove('tourType' , { path: '' } ); ... Cookies.set('tourType', tourType)}{code}  And of course its counterpart to remove    a { {tourType}} cookie{ code}
function removeTourTypePreference() {
Cookies.remove('tourType')
...
}
{code}  Finally  this , a  Freemarker function is used to detect cookies  in the request  with a given name .  in the request  {code}[#function detectCookie cookieName] [#if ctx.request.cookies?has_content][#list ctx.request.cookies as cookie][#if cookie.name == cookieName][#return cookie.value][/#if][/#list][/#if][#return ""][/#function]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 {{magnolia-travel-demo-component-personalization}} uses the _javascript_ cookie library [https://github.com/js-cookie/js-cookie] to set/remove tour type preferences.  Antti would like this mechanism to be documented. Starting with {{Magnolia 5.4.9}} the {{travel-demo-theme}} ships with https://github.com/js-cookie/js-cookie, a nifty _javascript_ library to handle... cookies (duh!). Its usage is quite straightforward and it's well explained in their docs. In particular, we use it to achieve the functionality required by {{magnolia-travel-demo-component-personalization}} where, based on the visitor's choice in the travel home page, we show featured tours of their favorite tour type.Here's how we use it.To set a cookie named {{tourType}} we use this simple function at{{demo-projects/enterprise/magnolia-travel-demo-component-personalization/src/main/resources/travel-demo-component-personalization/templates/components/personalizedTourTypeTeaserRow.ftl}}{code}   function setTourTypeAsCookie(tourType) {[#-- Always remove cookie when we're about to set it or we might end upwith multiple cookies with the same name.The empty path means remove for the whole site not for some specific path. --]Cookies.remove('tourType', { path: '' });Cookies.set('tourType', tourType)}{code}And of course its counterpart to remove {code}
function removeTourTypePreference() {
Cookies.remove('tourType')
...
}
{code}Finally this Freemarker function is used to detect cookies in the request with a given name.{code}[#function detectCookie cookieName] [#if ctx.request.cookies?has_content][#list ctx.request.cookies as cookie][#if cookie.name == cookieName][#return cookie.value][/#if][/#list][/#if][#return ""][/#function]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 {{magnolia-travel-demo-component-personalization}} uses the _javascript_ cookie library [https://github.com/js-cookie/js-cookie] to set/remove tour type preferences.  Antti would like this mechanism to be documented.Starting with {{Magnolia 5.4.9}} the {{travel-demo-theme}} ships with https://github.com/js-cookie/js-cookie, a nifty _javascript_ library to handle... cookies (duh!). Its usage is quite straightforward and it's well explained in their docs. In particular, we use it to achieve the functionality required by {{magnolia-travel-demo-component-personalization}} where, based on the visitor's choice in the travel home page, we show featured tours of their favorite tour type.Here's how we use it.To set a cookie named {{tourType}} we use this simple function  at  {{demo-projects/enterprise/magnolia-travel-demo-component-personalization/src/main/resources/travel-demo-component-personalization/templates/components/personalizedTourTypeTeaserRow.ftl}} {code}   function setTourTypeAsCookie(tourType) {[#-- Always remove cookie when we're about to set it or we might end up with multiple cookies with the same name. --]Cookies.remove('tourType');...Cookies.set('tourType', tourType)}{code}And of course its counterpart to remove a {{tourType}} cookie{code}
function removeTourTypePreference() {
Cookies.remove('tourType')
...
}
{code}Finally, a Freemarker function is used to detect cookies with a given name in the request {code}[#function detectCookie cookieName] [#if ctx.request.cookies?has_content][#list ctx.request.cookies as cookie][#if cookie.name == cookieName][#return cookie.value][/#if][/#list][/#if][#return ""][/#function]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This 

[magnolia-dev] [JIRA] (DOCU-832) Setting and reading cookies

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-832 
 
 
 
  Setting and reading cookies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 {{magnolia-travel-demo-component-personalization}} uses the _javascript_ cookie library [https://github.com/js-cookie/js-cookie] to set/remove tour type preferences.  Antti would like this mechanism to be documented.Starting with {{Magnolia 5.4.9}} the {{travel-demo-theme}} ships with https://github.com/js-cookie/js-cookie, a nifty _javascript_ library to handle... cookies (duh!). Its usage is quite straightforward and it's well explained in their docs. In particular, we use it to achieve the functionality required by {{magnolia-travel-demo-component-personalization}} where, based on the visitor's choice in the travel home page, we show featured tours of their favorite tour type.Here's how we use it.To set a cookie named {{tourType}} we use this simple function{code}   
    function setTourTypeAsCookie(tourType) {
[#-- Always remove cookie when we're about to set it or we might end up with multiple cookies with the same name. --]
Cookies.remove('tourType');
...
Cookies.set('tourType', tourType)
}
{code}And of course its counterpart to remove a {{tourType}} cookie{code}
function removeTourTypePreference() {
Cookies.remove('tourType')
...
}
{code}Finally, a Freemarker function is used to detect cookies with a given name in the request {code}[#function detectCookie cookieName] [#if ctx.request.cookies?has_content][#list ctx.request.cookies as cookie][#if cookie.name == cookieName][#return cookie.value][/#if][/#list][/#if][#return ""][/#function]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCE-55) Integrate app switcher into community edition

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-55 
 
 
 
  Integrate app switcher into community edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-332) Session numbers add up in the workflow workspace

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-332 
 
 
 
  Session numbers add up in the workflow workspace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PROCRES-6) Resource without template causes NPE when trying to edit it

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-6 
 
 
 
  Resource without template causes NPE when trying to edit it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCACHE-146) Cache-settings keep being reset.

[JIRA (on behalf of Michiel Meeuwissen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michiel Meeuwissen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-146 
 
 
 
  Cache-settings keep being reset.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 23/Sep/16 9:19 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Michiel Meeuwissen 
 
 
 
 
 
 
 
 
 
 
We configured a few caches (via https://github.com/vpro/jsr107-magnolia). In a production-environment, the seem to be configured a bit too large (using too much memory). 
We wanted to decrease the size of the cache. Since I didn't find a way to make the cache-module reload it's configuration (is there one?), I simply also adjusted the cache size using the JMX-operations provided by ehcache, hoping to prevent a restart. 
This seems to work, but after a few hours the cache have their original sizes yet again. I don't know why, but I suspect the magnolia cache wrapper, since it was responsible for the cache sizes in the first place. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
   

[magnolia-dev] [JIRA] (MGNLUI-4021) Introduce Copy & Paste actions in content apps

[JIRA (on behalf of Milan Divilek)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milan Divilek reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4021 
 
 
 
  Introduce Copy & Paste actions in content apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Milan Divilek 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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