[magnolia-dev] [JIRA] (MGNLUI-3636) Security App: Provide the possiblity to see what users are members of a certain group.

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3636 
 
 
 
  Security App: Provide the possiblity to see what users are members of a certain group.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3731) Migrate legacy permissions app to security app

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3999) Provide tools subapps with configured forms and actions out of the box

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3999 
 
 
 
  Provide tools subapps with configured forms and actions out of the box  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Fix Version/s:
 
 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] (MGNLACTIVATION-135) multiple publishing leaves page in "modified" state

[JIRA (on behalf of Evzen Fochr)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-135 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 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] (BLOSSOM-239) Defining a Blossom component with a DynamicFragmentDefinition

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-239 
 
 
 
  Defining a Blossom component with a DynamicFragmentDefinition   
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 We are trying to define a component, and we wonder if it would be possible to define the fragmentDefintion as a @Template property, as [explained in the docs | https://documentation.magnolia-cms.com/display/DOCS/Component+definition#fcc4a9d14bd64e04a8ae8537b199e9b8].We checked the Blossom module code and didn't find anything related with the DynamicFragmentDefinition, so maybe it's still not implemented.  Example with For now, we're  using the @PreRegister annotation to define this property:{code}@PreRegisterpublic void register(BlossomTemplateDefinition templateDefinition) {FragmentDefinition fragmentDefinition = new DynamicFragmentDefinition();templateDefinition.setFragmentDefinition(fragmentDefinition);}{code}  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BLOSSOM-239) Defining a Blossom component with a DynamicFragmentDefinition

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-239 
 
 
 
  Defining a Blossom component with a DynamicFragmentDefinition   
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 We are trying to define a component, and we wonder if it would be possible to define the fragmentDefintion as a  {{  @Template }}  property, as [explained in the docs | https://documentation.magnolia-cms.com/display/DOCS/Component+definition#fcc4a9d14bd64e04a8ae8537b199e9b8].We checked the Blossom module code and didn't find anything related with the  {{  DynamicFragmentDefinition }} , so maybe it's still not implemented. For now, we're using the @PreRegister annotation to define this property:{code}  @PreRegister  public void register(BlossomTemplateDefinition templateDefinition) {  FragmentDefinition fragmentDefinition = new DynamicFragmentDefinition();  templateDefinition.setFragmentDefinition(fragmentDefinition);}{code}  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-55) Integrate app switcher into community edition

[JIRA (on behalf of Hieu Nguyen Duc)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hieu Nguyen Duc updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Hieu Nguyen Duc 
 
 
 

Original Estimate:
 
 0.5d 
 
 
 

Remaining Estimate:
 
 0.5d 
 
 
 

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] (MGNLCE-55) Integrate app switcher into community edition

[JIRA (on behalf of Hieu Nguyen Duc)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hieu Nguyen Duc updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Hieu Nguyen Duc 
 
 
 

Original Estimate:
 
 0.5d 
 
 
 

Remaining Estimate:
 
 0.5d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BLOSSOM-239) Defining a Blossom component with a DynamicFragmentDefinition

[on behalf of Ervín Výstup]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ervín Výstup updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-239 
 
 
 
  Defining a Blossom component with a DynamicFragmentDefinition   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 
 
 
 
 
 
 
 Hello, We are  developing a new version of our booking engine with the latest version of Magnolia and the new Blossom module (3.1.3). We are  trying to define a component, and we wonder if it would be possible to define the fragmentDefintion as a @Template property, as [explained in the docs | https://documentation.magnolia-cms.com/display/DOCS/Component+definition#fcc4a9d14bd64e04a8ae8537b199e9b8]. If by chance it's possible, could you please provide a quick code sample of how the definition would be?Our code looks like this so far:{code:java}@Template(id = "hotetec-blossom-engine:components/testComponent", title = "Test Blossom", dialog = "testComponentDialog")@TemplateDescription("Blossom Text Component")@Controllerpublic class testComponent {   @RequestMapping("/testComponent")   public String render(BlossomTemplateDefinition templateDefinition) {  try { // Do Stuff  } catch (Exception e) { System.out.println("Something went wrong");  }  return "components/testComponent.ftl";   }}{code} We checked the Blossom module code and didn't find anything related with the DynamicFragmentDefinition, so maybe it's still not implemented.  Maybe we could use Example with using  the @PreRegister annotation to define this property ? :{code}@PreRegisterpublic void register(BlossomTemplateDefinition templateDefinition) {FragmentDefinition fragmentDefinition = new DynamicFragmentDefinition();templateDefinition.setFragmentDefinition(fragmentDefinition);}{code}   Thank you! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (BLOSSOM-239) Defining a Blossom component with a DynamicFragmentDefinition

[on behalf of Ervín Výstup]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ervín Výstup updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-239 
 
 
 
  Defining a Blossom component with a DynamicFragmentDefinition   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Assignee:
 
 Zdenek Skodik 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (BLOSSOM-239) Defining a Blossom component with a DynamicFragmentDefinition

[on behalf of Ervín Výstup]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ervín Výstup updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Blossom Module /  BLOSSOM-239 
 
 
 
  Defining a Blossom component with a DynamicFragmentDefinition   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Project:
 
 Support -  Magnolia  Blossom Module 
 
 
 

Key:
 
 SUPPORT BLOSSOM - 6535 239 
 
 
 

Issue Type:
 
 Support Request Improvement 
 
 
 

Workflow:
 
 Support New Product Dev  Workflow 
 
 
 

Security:
 
 Private 
 
 
 

Component/s:
 
 HowTo/Documentation 
 
 
 

Project or customer:
 
 Hotetec 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (PAGES-89) Consolidate display of edit-bars for inherited elements

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-89 
 
 
 
  Consolidate display of edit-bars for inherited elements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar-widgets and their actions were disabled. Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area  and different display for inherited areas vs inherited components .This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for  disaplay  display .- Do we actually need to display the inherited once? adding more noise to the page.    
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-89) Consolidate display of edit-bars for inherited elements

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-89 
 
 
 
  Consolidate display of edit-bars for inherited elements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar-widgets and their actions were disabled.   Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area and different display for inherited areas vs inherited components.This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for display.- Do we actually need to display the inherited once? adding more noise to the page. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-89) Consolidate display of edit-bars for inherited elements

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-89 
 
 
 
  Consolidate display of edit-bars for inherited elements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on  bar  edit - widgets bars  and their actions were disabled.Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area and different display for inherited areas vs inherited components.This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for display.- Do we actually need to display the inherited once? adding more noise to the page. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-89) Consolidate component-bar forinherited elements

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-89 
 
 
 
  Consolidate component-bar forinherited elements  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 29/Aug/16 1:04 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
The display of inherited areas and components have changed due to various unrelated changes in the page-editor. IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar-widgets and their actions were disabled. Looking at the code this changed in 

MAGNOLIA-5439
: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area. This ended up crashing when 

PAGES-62
 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those. 
Some more notes: 
 

the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for disaplay.

[magnolia-dev] [JIRA] (PAGES-89) Consolidate display of edit-bars for inherited elements

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-89 
 
 
 
  Consolidate display of edit-bars for inherited elements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 

Summary:
 
 Consolidate  component  display of edit - bar forinherited bars for inherited  elements 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-181) Demonstrate behavioral personalization with a cookie trait

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-181 
 
 
 
  Demonstrate behavioral personalization with a cookie trait  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Fix Version/s:
 
 0.14 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4003) CKEditor errors

[JIRA (on behalf of Jaroslav Simak)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jaroslav Simak updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4003 
 
 
 
  CKEditor errors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jaroslav Simak 
 
 
 

Project:
 
 CKEditor module Magnolia UI 
 
 
 

Key:
 
 MGNLCKEDIT MGNLUI - 24 4003 
 
 
 

Security:
 
 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: 

AW: [magnolia-dev] Re: Problem with imaging module on clustered environment

[Unger, Richard]

Hi Ged,

The questions you're asking are in the direction of operational management of 
your mangolia setup. They are good questions, and I don't know if there is a 
perfect answer - it depends on your operations team, server infrastructure, 
etc...

For the Jackrabbit files, I think a good approach is to use a "generic" file 
that has variables in it. This file can be part of the deployed webapp. The 
variable values can be defined differently for each server using a 
magnolia.properties config file. I find it best to keep this .properties file 
outside the webapp, e.g. it isn't part of the deployment, it is part of the 
server setup. tomcat/conf can be a natural place to store it. You can define 
where to find it to magnolia using a -D parameter.

In this way all your nodes use the same jackrabbit configuration, but with 
different parameters like database host or schema name.

Regarding mysql setup, you have the full range of options: separate servers, 
separate databases, or different prefixes within the same database. Personally 
I don't see the advantage of putting everything in the same database, but maybe 
there is a good reason to do so.

Backing up your magnolia instances is a separate problem again. Really, a 
Jackrabbit Repository has to be stopped to guarantee a consistent backup at the 
database/datastore level. This means that you have to shut down the magnolia 
instance using it if you want to create a backup at the database level.
Some ideas for dealing with this:
1) some people back up on the JCR level rather than the database level, by 
using the JCR export functions. This then does not require a magnolia shutdown.
2) you can consider not backing up your public nodes, or at least not 
regularly. This is especially true if you have multiple public servers. If you 
have a fast way to restore a "naked" public node, the data can then be restored 
by publishing from the author instance (using the synchronization module, or 
manually).
3) and for your author instance, it is usually ok to shut it down at night in 
order to create a consistent backup...

If you are running a lot of magnolia instances, it really pays to take the time 
to think about these issues, and the management of the servers. By using 
virtualization or containerization, separating the per-node configuration from 
the webapp, and automating deployments you can really save a lot of time and 
effort in a large installation.

Regards from Vienna,

Richard



> -Ursprüngliche Nachricht-
> Von: dev-list-ow...@magnolia-cms.com [mailto:dev-list-owner@magnolia- 
> cms.com] Im Auftrag von Gediminas Zalys (via Magnolia Forums)
> Gesendet: Samstag, 20. August 2016 08:17
> An: Magnolia Dev List
> Betreff: [magnolia-dev] Re: Problem with imaging module on clustered 
> environment
> 
> Many thanks for your support Richard!
> 
> I feel that derby is not a wise choice for production systems, so ill 
> leave this option out.
> 
> I am slightly concerned in regards to managing this setup.
> Lets say i have 10 nodes running magnolia public instances. This means 
> i will need 10 jackrabbit files pointing to different mysql databases.
> And also what about backups? backing up that many databases will 
> surely eventually create inconstancies.
> 
> feels to me that data will end up all over the place.
> 
> maybe there is a way to say use one jackrabbit file, that points to 
> one DB, however create tables with different prefixes, i.e node1_ mgnlVersion 
> etc?
> 
> Thanks again for your help,
> Ged
> 
> --
> Context is everything: http://forum.magnolia-
> cms.com/forum/thread.html?threadId=c9a18b1f-e47a-4d11-9c15-
> 448c5e14a519
> 
> 
> 
> 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: 
> 




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: 

AW: [magnolia-dev] Re: Autodeployment

[Unger, Richard]

Hi Daniel,

This is a standard problem, and Magnolia provides ways to develop that get 
around this:

Basically, if you are developing in Java, then the JVM *needs* to reload your 
classes when you change them. There are three levels of this:
1) restart the whole java process (restart tomcat). This will reload 
everything, but with a lengthy down-time, and lost sessions
2) tomcat reloads your webapp. Depending on your configuration, it will do this 
automatically when it detects changes. This has a shorter downtime, but 
otherwise the same disadvantages as 1). Additionally, most setups will only 
survive a certain number of reloads before running out of RAM, because tomcat 
usually doesn't manage to release all the memory the previous instances of the 
webapp allocated.
3) hot-code-deploy via your IDE. In the correct setup, while debugging, your 
IDE can "live-change" some java changes (not all) without restarting anything.

That all applies for developing in Java.
If you are are doing so called "light development", not in Java, things can be 
much more comfortable:

When you are talking about developing templates, html, javascript, etc... then 
all you are changing is your resources. Magnolia can detect those changes and 
reload your resources and definitions automatically, without any need to 
restart the webapp.

***The trick to make this work is to make sure these resources are not part of 
the webapp, e.g. don't get loaded from the classpath.*** Magnolia provides two 
mechanisms for your resources outside the classpath:

1. Light development via filesystem: store your resources on the filesystem 
(outside the webapp!) and configure the resource base path to point to that 
folder. Magnolia will find your resources there, and automatically reload them 
as they change.

2. Store resources in JCR, in the resources workspace. Again, magnolia will 
automatically reload them as they change. You can use the webdav module to 
connect to JCR in a convenient way and thereby edit the files in your favourite 
editor.

Hope that helps you!

Regards from Vienna,

Richard



> -Ursprüngliche Nachricht-
> Von: dev-list-ow...@magnolia-cms.com [mailto:dev-list-owner@magnolia- 
> cms.com] Im Auftrag von Daniel Baylon (via Magnolia Forums)
> Gesendet: Dienstag, 23. August 2016 11:06
> An: Magnolia Dev List
> Betreff: [magnolia-dev] Re: Autodeployment
> 
> Hello Christoph,
> 
> [quote]
> 
> Once again: What do you want to achieve with the update? What has 
> changed in the modules which you want to redeploy?
> 
> [/quote]
> 
> Say I just did add new label. Either way, I change something on the 
> code that I rebuild a module. Once I rebuild the module, I build the 
> whole war package for the deployment.
> 
> [quote]
> 
> And: Which servlet container / app-server are you suing? Tomcat? JBoss?
> WebLogic? Websphere? ...
> 
> [/quote]
> 
> I am using Tomcat 7.
> 
> Regards,
> 
> Dan
> 
> --
> Context is everything: http://forum.magnolia-
> cms.com/forum/thread.html?threadId=e5e78cef-8b5e-41f6-882a-
> 38fb9ce9db12
> 
> 
> 
> 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: 
> 




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-3977) Quick navigation by using a keyboard may cause of multiple selection

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3977 
 
 
 
  Quick navigation by using a keyboard may cause of multiple selection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3977) Quick navigation by using a keyboard may cause of multiple selection

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3977 
 
 
 
  Quick navigation by using a keyboard may cause of multiple selection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Labels:
 
 devwl resources-app tree 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4000) Update to Vaadin 7.7

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4000 
 
 
 
  Update to Vaadin 7.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-10) Add grouping by source

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-10 
 
 
 
  Add grouping by source  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-24) Define the place and level of integration with definiton decoration functionality

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-24 
 
 
 
  Define the place and level of integration with definiton decoration functionality  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-181) Demonstrate behavioral personalization with a cookie trait

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-181 
 
 
 
  Demonstrate behavioral personalization with a cookie trait  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3636) Security App: Provide the possiblity to see what users are members of a certain group.

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3636 
 
 
 
  Security App: Provide the possiblity to see what users are members of a certain group.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3898) Reveal moved item in the "move" dialog

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3898 
 
 
 
  Reveal moved item in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-60 
 
 
 
  Themes added by using the old mechanism (backwards-compatible) are not decorateable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 0.5 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3835) Provide a way to disable drag and drop

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3835 
 
 
 
  Provide a way to disable drag and drop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3999) Provide tools subapps with configured forms and actions out of the box

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3999 
 
 
 
  Provide tools subapps with configured forms and actions out of the box  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3731) Migrate legacy permissions app to security app

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3977) Quick navigation by using a keyboard may cause of multiple selection

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3977 
 
 
 
  Quick navigation by using a keyboard may cause of multiple selection  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3900) Show the root node in the "move" dialog

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3900 
 
 
 
  Show the root node in the "move" dialog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-60 
 
 
 
  Themes added by using the old mechanism (backwards-compatible) are not decorateable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 1 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-55) Integrate app switcher into community edition

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon 59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3973) After zip import, location points to non-existing /untitled node, shows multi-item actionbar section

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3973 
 
 
 
  After zip import, location points to non-existing /untitled node, shows multi-item actionbar section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-181) Demonstrate behavioral personalization with a cookie trait

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-181 
 
 
 
  Demonstrate behavioral personalization with a cookie trait  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4000) Update to Vaadin 7.7

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4000 
 
 
 
  Update to Vaadin 7.7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 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] (MGNLSITE-69) Implement DefinitionType#getName() for ThemeRegistry type

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-69 
 
 
 
  Implement DefinitionType#getName() for ThemeRegistry type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-60 
 
 
 
  Themes added by using the old mechanism (backwards-compatible) are not decorateable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-24) Define the place and level of integration with definiton decoration functionality

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-24 
 
 
 
  Define the place and level of integration with definiton decoration functionality  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-142) Update from commons-httpclient:commons-httpclient to org.apache.httpclient:httpclient

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-142 
 
 
 
  Update from commons-httpclient:commons-httpclient to org.apache.httpclient:httpclient  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLFORM-288) Update org.apache.commons:commons-lang3 to version 3.4

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-288 
 
 
 
  Update org.apache.commons:commons-lang3 to version 3.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 2.3.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4002) CLONE - After zip import, location points to non-existing /untitled node, shows multi-item actionbar section

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4002 
 
 
 
  CLONE - After zip import, location points to non-existing /untitled node, shows multi-item actionbar section  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.8 
 
 
 

Assignee:
 
 Oanh Thai Hoang 
 
 
 

Components:
 

 actionbar, admincentral, tree/list 
 
 
 

Created:
 

 29/Aug/16 9:55 AM 
 
 
 

Fix Versions:
 

 5.5, 5.4.9 
 
 
 

Labels:
 

 import tree 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Sang Ngo Huu 
 
 
 

Security Level:
 

 Public 
 
 
 

Original Estimate:
 

3d
   

[magnolia-dev] [JIRA] (MGNLACTIVATION-135) multiple publishing leaves page in "modified" state

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-135 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 3 8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-54) Use GWT.create (or similar) for selected components in the page-editor-widget

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-54 
 
 
 
  Use GWT.create (or similar) for selected components in the page-editor-widget  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3998) Introduce a new vaadin widgetset for the enterprise-pro webapp

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3998 
 
 
 
  Introduce a new vaadin widgetset for the enterprise-pro webapp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 0.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] (PAGES-84) Offer copy+paste of components in the page editor

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-84 
 
 
 
  Offer copy+paste of components in the page editor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 5 8 
 
 
 

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] (MGNLACTIVATION-135) multiple publishing leaves page in "modified" state

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-135 
 
 
 
  multiple publishing leaves page in "modified" state   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (PAGES-83) Find a way to customise page editor CSS

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-83 
 
 
 
  Find a way to customise page editor CSS   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz  58  59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: