[magnolia-dev] [JIRA] (LANG-44) Extract DE language files from demo-projects to lang-de

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Language Bundles /  LANG-44 
 
 
 
  Extract DE language files from demo-projects to lang-de   
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Labels:
 
 blocked 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3800) "detail" subapp is hardcoded in info.magnolia.ui.contentapp.browser.action.ShowVersionsAction#getLocation method

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3800 
 
 
 
   "detail" subapp is hardcoded in info.magnolia.ui.contentapp.browser.action.ShowVersionsAction#getLocation method  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Saigon 36 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself. UPDATE: Copied from the comments 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLDEMO-152) Error with page created at root.

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-152 
 
 
 
  Error with page created at root.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 ON CE bundle. I created a page at the root with template "Travel Standard". When opening the page in the page editor there is an error:Problem appears to be in navigation ftl.#assign pages = model.rootPages!{ { code} Error while rendering [/Test] with template [null] for URI [/Test.html?mgnlPreview=false=desktop]:RenderException: freemarker.core._TemplateModelException: An error has occurred when reading existing sub-variable "rootPages"; see cause exception! The type of the containing value was: extended_hash+string (info.magnolia.demo.travel.model.NavigationAreaModel wrapped into f.e.b.StringModel)FTL stack trace ("~" means nesting-related): - Failed at: #assign pages = model.rootPages!  [in template "travel-demo/templates/pages/areas/navigation.ftl" at line 6, column 1] {code } } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-680) Create content-app which allows to categorize its items

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-680 
 
 
 
  Create content-app which allows to categorize its items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Christoph Meier Antti Hietala 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LMPLUGIN-5) Generated light-modules should be scoped 'magnolia'

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-5 
 
 
 
  Generated light-modules should be scoped 'magnolia'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Sprint:
 
 Basel 35 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3818) SelectFieldFactory is not translating keys, if options are build from repository path

[JIRA (on behalf of Sergio Vidangos)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sergio Vidangos created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3818 
 
 
 
  SelectFieldFactory is not translating keys, if options are build from repository path  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 18/Mar/16 1:46 PM 
 
 
 

Labels:
 

 dialogs select i18n 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Sergio Vidangos 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
After the changes made in this revision, the labels of the options are not being internationalized anymore (only the keys are shown; the translations are not being loaded using the keys). 
This happens in case the options are loaded from JCR using the parameters 'repository' and 

[magnolia-dev] [JIRA] (MGNLDEMO-114) Use i18n "best practices" on the travel-demo

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-114 
 
 
 
  Use i18n "best practices" on the travel-demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 Do not set i18n-basename, label, description on dialogs and templates - instead make use of autogenerated keys and use bundles within {{ mgnl- i18n}} folder.Move keys from "old" bundles - magnolia-travel-tours/src/main/resources/info/magnolia/module/travel-tours/messages- magnolia-travel-demo/src/main/resources/info/magnolia/module/travel-demo/messages into {{i18n}} folder wherever possible. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-63) Research a way to apply default values when creating new items

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-63 
 
 
 
  Research a way to apply default values when creating new items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Comment:
 
 We have an *issue with default values when creating a new item* in that we *can't set them without jumping through some loops*.* For pages, we used to just create a new page when a user clicked "add page". This would add a new node, but not set any default values. We fixed that by showing the page properties dialog right after the user picked the page template. See PAGES-61.* For areas, we solved this issue using auto-generation.Not every such solution works for every item and for every case. We should thus *find a mechanism that allows us to reliably set default values when creating a new item* based on the dialog definition that defines it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LANG-44) Extract DE language files from demo-projects to lang-de

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Language Bundles /  LANG-44 
 
 
 
  Extract DE language files from demo-projects to lang-de   
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Assignee:
 
 Evzen Fochr Roman Kovařík 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-574) Update Categorization doc and catfn

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-574 
 
 
 
  Update Categorization doc and catfn  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Christoph Meier Antti Hietala 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-63) Research a way to apply default values when creating new items

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-63 
 
 
 
  Research a way to apply default values when creating new items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We have an *issue with default values when creating a new item* in that we *can't set them without jumping through some loops*.* For pages, we used to just create a new page when a user clicked "add page". This would add a new node, but not set any default values. We fixed that by showing the page properties dialog right after the user picked the page template. See PAGES-61.* For areas, we solved this issue using auto-generation.Not every such solution works for every item and for every case. We should thus *find a mechanism that allows us to reliably set default values when creating a new item* based on the dialog definition that defines it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-697) Document the i18n key generators and best practices

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-697 
 
 
 
  Document the i18n key generators and best practices  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 16/Mar/16 12:26 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We need a list of all of the implemented key generators. We need a description of why there are so many. The advantages and recommendation to use the less specific ones in most cases. The need to use more specific ones sometimes. 
For internal and external audiences. We want to encourage the less specific keys so that we dont have so much duplication i the language files. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (DOCU-704) Change the version of the used log4j lib / Magnolia, logging and logstash

[JIRA (on behalf of marcel koch)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 marcel koch created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-704 
 
 
 
  Change the version of the used log4j lib / Magnolia, logging and logstash  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Support Request 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Mar/16 12:41 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 marcel koch 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
As you describing in the Docu Magnolia uses log4j for logging. As I can see after building the WAR file the exact version is log4j-1.2.17.  Furthermore, another dependency to slf4j is resolved - the exact versions are slf4j-api-1.7.7 and slf4j-log4j12-1.7.7. 
Without looking into the code I'm wondering...  
 

why you have the dependency to slf4j when you only want to use log4j?
 

if from your perspective it would be possible to change the the log4j version to something like 2.x?
 
 
I'm asking since we are doing some experiments regarding Magnolia logging directly to logstash without having the step in between of writing files to the disk. Are there maybe any hints you could provide? 
Thank you very much 
 
 
 
 
 
 

[magnolia-dev] Re: Using RichText in MultiValueField Issue

[Jennylyn Sze (via Magnolia Forums)]

I'm using magnolia 5.4.5.
I forgot to mention that I'm using a composite field.
Although I tried to using only richtext as the field in the MultiValue but 
still have the same error.

Try to add more than one rich text, then click the up down button to change the 
order of the rich text, then you'll see that one of the rich text is missing.

Here's the code:

[code]
   tabs:
 - name: tncInfo
label: T
fields:
  - name: tnc
class: 
info.magnolia.ui.form.field.definition.MultiValueFieldDefinition
transformerClass: 
info.magnolia.ui.form.field.transformer.multi.MultiValueSubChildrenNodePropertiesTransformer
label: Terms and Conditions
field:
  name: compositeField
  class: 
info.magnolia.ui.form.field.definition.CompositeFieldDefinition
  description: Terms and Conditions
  layout: vertical
  fields:
title:
  class: 
info.magnolia.ui.form.field.definition.TextFieldDefinition
  label: Title
  type: String
content:
  class: 
info.magnolia.ui.form.field.definition.RichTextFieldDefinition
  height: 200
  label: Content
  type: String

[/code]

Thanks :)

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=6fb715f0-d6ee-4896-b2d3-acc97e6feeb3



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-3780) Show Version action fails when contentConnector rootPath is not '/'

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3780 
 
 
 
  Show Version action fails when contentConnector rootPath is not '/'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Affects Version/s:
 
 5.4.5 
 
 
 

Affects Version/s:
 
 5.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-701) Integration options overview

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-701 
 
 
 
  Integration options overview  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 content 
 
 
 

Created:
 

 18/Mar/16 8:47 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antti Hietala 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Improve the Integration page. Provide a better overview of integration options and Magnolia capabilities. The corresponding page on the Magnolia corporate website is much more informative. Describe typical integration targets and link to supporting documentation such as REST API, Google Analytics module and Marketing Tags module. 
Idea: add an integration label to relevant documentation pages and use the Content by Label macro to display an aggregated list of resources like we do in Tutorials 
 
 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (DOCU-680) Create content-app which allows to categorize its items

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-680 
 
 
 
  Create content-app which allows to categorize its items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Antti Hietala Christoph Meier 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself.UPDATE: Copied from the comments Here's the clarification, after double-checking with Andreas:* We call for radio options in the {{pages:newComponent}} dialog. This is a relatively cheap solution to let e.g. news editors to add latest articles on top easily.** We acknowledge that we skipped the component dialog (in PAGES-58) when there is only one type of component available; we're ok with this.** We don't show this field for single component areas. * We don't do the secondary split of the "add component" action in the end, not to bloat the action bar.* We consider configuring position of the placeholder(s) on the area definition (cc [~weder] to file a follow-up issue).Anything I missed? Reopening/updating this issue; I will also decline the current PR. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (PAGES-63) Research a way to apply default values when creating new items

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-63 
 
 
 
  Research a way to apply default values when creating new items  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 17/Mar/16 4:23 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLDEMO-152) Error with page created at root.

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-152 
 
 
 
  Error with page created at root.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 17/Mar/16 10:14 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 
ON CE bundle. I created a page at the root with template "Travel Standard". When opening the page in the page editor there is an error: Problem appears to be in navigation ftl. #assign pages = model.rootPages! 
{{Error while rendering [/Test] with template [null] for URI [/Test.html?mgnlPreview=false=desktop]: RenderException: freemarker.core._TemplateModelException: An error has occurred when reading existing sub-variable "rootPages"; see cause exception! The type of the containing value was: extended_hash+string (info.magnolia.demo.travel.model.NavigationAreaModel wrapped into f.e.b.StringModel) 
 
FTL stack trace ("~" means nesting-related): 
 

Failed at: #assign pages = model.rootPages! [in template "travel-demo/templates/pages/areas/navigation.ftl" at line 6, column 1] 
 
}}
 
 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3780) Show Version action fails when contentConnector rootPath is not '/'

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3780 
 
 
 
  Show Version action fails when contentConnector rootPath is not '/'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Affects Version/s:
 
 5.4.4 
 
 
 

Affects Version/s:
 
 5.4.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3815) i18n & MultiValueFieldFactory

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3815 
 
 
 
  i18n & MultiValueFieldFactory  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 17/Mar/16 8:36 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Roman Kovařík 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
If you don't set a label property on the nested field, info.magnolia.ui.form.field.definition.FieldDefinitionKeyGenerator#keysFor fails with NPE since the name of the field is not set. To reproduce: 
 

/tours/dialogs/components/tourTypeTeaserRow.yaml Remove the label property of the field
 

Open tourTypeTeaserRow dialog on the home page. 

 

[magnolia-dev] [JIRA] (MGNLUI-3799) ShowVersionsAction doesn't use ContentConnector

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3799 
 
 
 
  ShowVersionsAction doesn't use ContentConnector  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Saigon 36 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-700) Better landing page for apps

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-700 
 
 
 
  Better landing page for apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 
 
 
 
 
 
 
 The current [Apps|https://documentation.magnolia-cms.com/display/DOCS/Apps] page is a poor entry point into Magnolia apps, as the user comment on the page indicates. Most of the answers are on the child pages but it requires digging, which should not be  need  needed  to get a good overview.Improve the page:* What are apps and how they are similar/different from the conventional understanding of "app"* How do apps work together in Magnolia, for example content apps and the Pages app* Are all apps the same? If not, what are the main types of apps?* Add screenshots of main app types. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3817) Ask a user where to add a new component, even if an area accepts just a single component type

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3817 
 
 
 
  Ask a user where to add a new component, even if an area accepts just a single component type  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 17/Mar/16 6:36 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Andreas Weder 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We should offer an option to force the "choose component" dialog to be shown, even if an area only accepts a single type of component, to still allow a user to specify if that component should be added at the top or the bottom of the list of components in that area. 
We've recently made two improvements: 
 

PAGES-59: when adding a new component, an editor may now specify if that component is added at the top or at the bottom of an area.
 



PAGES-58
: we no longer ask the user to pick the type of component to add, if an area only accepts a single type of component anyway
 
 
While both are valid usability improvements, they can conflict with each other: if an area now only accepts a single component type, an editor may no longer choose to 

[magnolia-dev] [JIRA] (MTE-50) HTML5 video Component

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-50 
 
 
 
  HTML5 video Component  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Attachment:
 
 video.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-48) Create registry for themes to allow them to be configured via jcr or yaml definitions

[JIRA (on behalf of Evzen Fochr)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Theme should extend NamedDefinition 
 
 
 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-48 
 
 
 
  Create registry for themes to allow them to be configured via jcr or yaml definitions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-693) Documentation for Google analytics visualization

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-693 
 
 
 
  Documentation for Google analytics visualization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 See https://documentation.magnolia-cms.com/display/DOCS/Google+Analytics+Visualization+module 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-145) NPE in in ConsoleContext when strategy is not set (when executing console OUT of web context (on a separate thread for example)

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-145 
 
 
 
  NPE in in ConsoleContext when strategy is not set (when executing console OUT of web context (on a separate thread for example)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Mar/16 1:54 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Jan Haderka 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 

 
Caused by: java.lang.NullPointerException
	at info.magnolia.context.RequestAttributeStrategy.getAttribute(RequestAttributeStrategy.java:83)
	at info.magnolia.context.AbstractContext.getAttribute(AbstractContext.java:107)
	at info.magnolia.context.ContextDecorator.getAttribute(ContextDecorator.java:74)
	at info.magnolia.module.groovy.console.MgnlGroovyConsoleContext.getRepositoryStrategy(MgnlGroovyConsoleContext.java:111)
 

 
(Ugly) workaround is to set strategy explicitly to null to prevent this error before invoking console on the context: 

 

final String STRATEGY_ATTRIBUTE = MgnlGroovyConsole.class.getName() + ".strategy";
groovyCtx.setAttribute(STRATEGY_ATTRIBUTE, null, Context.SESSION_SCOPE);
...
MgnlContext.setInstance(groovyCtx);
MgnlGroovyConsole console = new MgnlGroovyConsole(new Binding());

 

 

[magnolia-dev] [JIRA] (PAGES-64) Ask a user where to add a new component, even if an area accepts just a single component type

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-64 
 
 
 
  Ask a user where to add a new component, even if an area accepts just a single component type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Project:
 
 Magnolia  UI  pages module 
 
 
 

Key:
 
 MGNLUI PAGES - 3817 64 
 
 
 

Security:
 
 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3816) Missing translation in Pulse "publish.actions.delete"

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3816 
 
 
 
  Missing translation in Pulse "publish.actions.delete"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Attachment:
 
 Screen Shot 2016-03-17 at 10.03.24.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] Re: How to include javascript into magnolia dialog

[Jack Son (via Magnolia Forums)]

Here I would like to share something for fresheres who is confused about 
career. Those people please look at my message. Its really helpful for u. 
Besant technologies provide hands on 
[url=http://www.traininginsholinganallur.in/selenium-training-in-chennai.html]Selenium
 training in Chennai[/url] with years of experienced professionals.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=73834049-0a81-4b2f-95ba-60d383d625a7



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-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself.*UPDATE*: Copied from the commentsHere's the clarification, after double-checking with Andreas:* We call for radio options in the {{pages:newComponent}} dialog. This is a relatively cheap solution to let e.g. news editors to add latest articles on top easily.** We acknowledge that we skipped the component dialog (in PAGES-58) when there is only one type of component available; we're ok with this.** We don't show this field for single component areas. * We don't do the secondary split of the "add component" action in the end, not to bloat the action bar.* We consider configuring position of the placeholder(s) on the area definition * Added a wireframe showing the radio button group for picking where to add the component (at the beginning or at the end).* As a side note, you'll notice I've also renamed the dialog title and the label of the first input field to be more in-line with what we have elsewhere. If that's easy to change in one go, please do so, else feel free to create a follow-up issue for these label changes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3624) CustomMultiField components can't display help text

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3624 
 
 
 
  CustomMultiField components can't display help text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 36 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] Re: Using RichText in MultiValueField Issue

[via Magnolia Forums]

An alternative to very complex forms with composite and multi value fields is 
it to use multiple content types in an app. For instance an item 'company' can 
have sub items employees. Each item has then its own form. It is more work to 
setup the actions but it allows to build rather complex item trees without 
confusing the users to much.

Have a nice day!

Philipp

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=6fb715f0-d6ee-4896-b2d3-acc97e6feeb3



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

[magnolia-dev] [JIRA] (MTE-74) Use i18n "best practices" in MTK

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-74 
 
 
 
  Use i18n "best practices" in MTK  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 Do not set i18n-basename, label, description on dialogs and templates - instead make use of autogenerated keys and use bundles within {{ mgnl- i18n}} folder.Move keys from "old" bundles into {{ mgnl- i18n}} folder wherever possible. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-698) Update Maven setup page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-698 
 
 
 
  Update Maven setup page  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 16/Mar/16 3:52 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christoph Meier 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Page: https://documentation.magnolia-cms.com/display/DEV/Maven+setup The "recipe" isn't working anymore. Fix it  
Current description: 
 

generate settings (for a magnolia employee)
 

create password encryption
 
 
=> no working You have to: 
 

Create generate settings fro CE user
 

Create password encryption
 

Create generate settings fro EE / magnolia employee / forge user
 
 
Check what has 

[magnolia-dev] [JIRA] (LANG-45) Wrong French delete information message shown when removing an item

[JIRA (on behalf of Viet Nguyen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Language Bundles /  LANG-45 
 
 
 
  Wrong French delete information message shown when removing an item  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 - The issue happen due to a wrong i18n message from Magnolia.-  Fix  Temporarily fix  by overriding as below:{{/modules/pages/apps/pages/subApps/browser/actions/confirmDeletion@confirmationMessage="\{0,choice,1# l-objet|1< \{1\} les objets\} et tous \{1,choice,1#ses|1< leurs\} sous-nœuds seront supprimés."}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-62) Disable duplicate action in 'single' areas and when 'maxComponents' is reached

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-62 
 
 
 
  Disable duplicate action in 'single' areas and when 'maxComponents' is reached  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 5.4.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LANG-45) Wrong French delete information message shown when removing an item

[JIRA (on behalf of Viet Nguyen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Language Bundles /  LANG-45 
 
 
 
  Wrong French delete information message shown when removing an item  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 - The issue happen due to a wrong i18n message from Magnolia. - Fix by overriding as below: {{ /modules/pages/apps/pages/subApps/browser/actions/confirmDeletion@confirmationMessage=" \ {0,choice,1# l-objet|1<  \  {1 \ } les objets \ } et tous  \  {1,choice,1#ses|1< leurs \ } sous-nœuds seront supprimés." }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] Re: Using RichText in MultiValueField Issue

[Simon (via Magnolia Forums)]

Composite fields in multivaluefields are kind of an issue.
You probably need a noopcomposite transformerclass on your composite field.
I wrote up a solution on this page:
https://documentation.magnolia-cms.com/display/DOCS/Transforming+field+values?focusedCommentId=114728444#comment-114728444

Hope this helps :)

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=6fb715f0-d6ee-4896-b2d3-acc97e6feeb3



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-3814) Content Connector: Allow configuration of defaultOrder: decending or ascending

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3814 
 
 
 
  Content Connector: Allow configuration of defaultOrder: decending or ascending  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Summary:
 
 ContentConnector defaultOrder Content Connector : Allow  Descending Order by Default  configuration of defaultOrder: decending or ascending 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-700) Better landing page for apps

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-700 
 
 
 
  Better landing page for apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 
 
 
 
 
 
 
 The current [Apps|https://documentation.magnolia-cms.com/display/DOCS/Apps] page is a poor entry point into Magnolia apps, as the user comment on the page indicates. Most of the answers are on the child pages but it requires digging, which should not be needed to get a good overview.Improve the page:* What are apps and how  they  are  they  similar/different from the conventional understanding of "app"* How do apps work together in Magnolia, for example content apps and the Pages app* Are all apps the same? If not, what are the main types of apps?* Add screenshots of main app types. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-700) Better landing page for apps

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-700 
 
 
 
  Better landing page for apps  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 content 
 
 
 

Created:
 

 17/Mar/16 4:09 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Antti Hietala 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The current Apps page is a poor entry point into Magnolia apps, as the user comment on the page indicates. Most of the answers are on the child pages but it requires digging, which should not be need to get a good overview. 
Improve the page: 
 

What are apps and how they are similar/different from the conventional understanding of "app"
 

How do apps work together in Magnolia, for example content apps and the Pages app
 

Are all apps the same? If not, what are the main types of apps?
 

[magnolia-dev] Re: How to get selected node?

[jessicaamirr (via Magnolia Forums)]

How is it possible to get the selected (clicked on) node in a treeview and 
return it as a string? 
[url=http://www.traininginsholinganallur.in/dot-net-training-in-chennai.html]Dot
 net Training in Chennai[/url] | 
[url=http://www.traininginsholinganallur.in/cloud-computing-training-in-chennai.html]Cloud
 Computing Training in Chennai[/url] | 
[url=http://www.traininginsholinganallur.in/linux-training-in-chennai.html]Linux
 Training in Chennai[/url] | 
[url=http://www.traininginsholinganallur.in/salesforce-training-in-chennai.html]Salesforce
 Training in Chennai[/url]

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=a0576bb2-5300-4f75-9d4d-c943868c2311



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-48) Create registry for themes to allow them to be configured via jcr or yaml definitions

[JIRA (on behalf of Evzen Fochr)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-48 
 
 
 
  Create registry for themes to allow them to be configured via jcr or yaml definitions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Fix Version/s:
 
 1.0.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LANG-44) Extract DE language files from demo-projects to lang-de

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Language Bundles /  LANG-44 
 
 
 
  Extract DE language files from demo-projects to lang-de   
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Sprint:
 
 Kromeriz 35 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-114) Use i18n "best practices" on the travel-demo

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-114 
 
 
 
  Use i18n "best practices" on the travel-demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 Do not set i18n-basename, label, description on dialogs and templates - instead make use of autogenerated keys and use bundles within {{mgnl-i18n}} folder.Move keys from "old" bundles - magnolia-travel-tours/src/main/resources/info/magnolia/module/travel-tours/messages- magnolia-travel-demo/src/main/resources/info/magnolia/module/travel-demo/messages into {{ mgnl- i18n}} folder wherever possible. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LMPLUGIN-2) Versioning and deployment for SNAPSHOT and FINAL versions

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-2 
 
 
 
  Versioning and deployment for SNAPSHOT and FINAL versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 Update: Nexus3 allows re-publishing packages, so we are able to publish e.g. mtk-0.10.0-snapshot over and over again. This issue lost the importance for now, while we're in testing-mode. Re-publishing in production is another topic. So the ticket is still valid as such. It's not possible to have maven-like development snapshots for npm packages (light modules) - npm is using semantic versioning and their repository does not support re-publishing of packages with same version (meaning it is not possible to publish 1.0.0-SNAPSHOT version multiple times).Some options:- publish snapshot versions with jenkins build-number - 1.0.0-build-1, 1.0.0-build-2- publish snapshot versions with unix-timestamp - 1.0.0-SNAPSHOT-1457532202The final version won't need an identifier, according to http://semver.org/:bq. Example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.When fetching the latest package, you won't get alpha or beta-versions in this case. But that's conform with how maven handles this. You will need to pin the version. OTOH release-candidates might be a problem.. build.5 < rc.1Resources:https://docs.npmjs.com/misc/semver#prerelease-tagshttp://blog.npmjs.org/post/77758351673/no-more-npm-publish-fhttps://github.com/npm/npm-registry-couchapp/issues/148http://nolanlawson.com/2014/09/01/the-limitations-of-semantic-versioning/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 

[magnolia-dev] [JIRA] (PAGES-62) Disable duplicate action in 'single' areas and when 'maxComponents' is reached

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-62 
 
 
 
  Disable duplicate action in 'single' areas and when 'maxComponents' is reached  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Sprint:
 
 Basel 35 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] Re: How Much Does a CMS Website Development Cost?

[Dwarakesh Babu (via Magnolia Forums)]

A website designed and built with full CMS integration will typically run from 
$3,000 to $8,500 with an average of $5,750, depending on your specific needs 
and the extent of the customization requested. These websites will be designed 
with both functionality and appearance in mind. Custom art design and mid-level 
functionality will be included. You will be able to manage and update all of 
your content through the installed CMS interface. You can have an infinite 
number of pages (depending on the amount you want to spend for the time it 
takes to create them). With CMS you can manipulate, upload and change the 
pictures, content, and blog all day long. 
[url=http://www.traininginsholinganallur.in/java-training-in-chennai.html#]Java 
training in chennai[/url] | 
[url=http://www.traininginsholinganallur.in/android-training-in-chennai.html#]Android
 training in chennai[/url] | 
[url=http://www.traininginsholinganallur.in/oracle-dba-training-in-chennai.html]Oracle
 dba Training in Chennai[/url] | 
[url=http://www.traininginsholinganallur.in/python-training-in-chennai.html]Python
 Training in chennai[/url]

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=b63adf3b-d82b-45ca-9981-72c95eee7bfa



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-693) Documentation for Google analytics visualization

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-693 
 
 
 
  Documentation for Google analytics visualization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Milan Divilek Julie Legendre 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LMPLUGIN-4) Extracted npm packages should end up in 'package'-directory

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-4 
 
 
 
  Extracted npm packages should end up in 'package'-directory  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 16/Mar/16 6:10 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
We currently create the tgz of the light modules, so they extract themselves into module-name-1.0.0-prerelease folder. This is wrong, they should simply extract into a folder called 'package'.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 

[magnolia-dev] [JIRA] (MGNLDEMO-114) Use i18n "best practices" on the travel-demo

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-114 
 
 
 
  Use i18n "best practices" on the travel-demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Sprint:
 
 Kromeriz 35 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LMPLUGIN-3) Add possibility to pass auth method and token for the npm repository

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-3 
 
 
 
  Add possibility to pass auth method and token for the npm repository  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The current implementation uses nexus' user token obtained from ~/.m2/settings.xml to authenticate. When moving to nexus 3 MS7 we realized that this authentication method was not supported (yet). We would still like to use that method as soon as it's implemented, but for now, we will add the possibility to explicitly set the auth-method and the auth-token.Usage before:{code}mvn deploy{code}Additionally you will be able to do:{code}mvn deploy -Dnpm.repo.url=""> "  -Dnpm.auth.realm="Bearer" -Dnpm.auth.token="a-b-c-d-x"{code}References:https://books.sonatype.com/nexus-book/reference/usertoken.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-699) Write a 3- 4 page Linux tutorial in English for starting off with Magnolia. This article will be translated by us to be used for publication in http://www.pro-linux.d

[JIRA (on behalf of Lorraine Chandler)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lorraine Chandler created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-699 
 
 
 
  Write a 3- 4 page Linux tutorial in English for starting off with Magnolia. This article will be translated by us to be used for publication in http://www.pro-linux.de  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 documentation-examples, hello-magnolia 
 
 
 

Created:
 

 17/Mar/16 11:17 AM 
 
 
 

Due Date:
 

10/May/16
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Lorraine Chandler 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Marketing can get a free article published in http://www.pro-linux.de/ on the lines of a Magnolia tutorial.  Examples are http://www.pro-linux.de/artikel/2/1813/3,einstellungen.html and http://www.pro-linux.de/artikel/2/1756/pydio-tutorial.html 
Such an article could be written using a combination of elements from https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia and https://documentation.magnolia-cms.com/display/DOCS/Tutorials 
Christoph has mentioned that after 

[magnolia-dev] Re: Using RichText in MultiValueField Issue

[Simon (via Magnolia Forums)]

Can you show me the code you built this op with, and the version of Magnolia 
you are using?
I can't reproduce this issue in magnolia 5.4.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=6fb715f0-d6ee-4896-b2d3-acc97e6feeb3



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-114) Use i18n "best practices" on the travel-demo

[JIRA (on behalf of Jaroslav Simak)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jaroslav Simak reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-114 
 
 
 
  Use i18n "best practices" on the travel-demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jaroslav Simak 
 
 
 

Status:
 
 Reviewed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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-3774) Content Apps should offer a default action per node type

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3774 
 
 
 
  Content Apps should offer a default action per node type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

Sprint:
 
 Kromeriz 35 
 
 
 

Account:
 
 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LMPLUGIN-3) Add possibility to pass auth method and token for the npm repository

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-3 
 
 
 
  Add possibility to pass auth method and token for the npm repository  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 The current implementation uses nexus' user token obtained from ~/.m2/settings.xml to authenticate. When moving to nexus 3 MS7 we realized that this authentication method was not supported (yet). We would still like to use that method as soon as it's implemented, but for now, we will add the possibility to explicitly set the auth-method and the auth-token.Usage before:{code}mvn deploy{code}Additionally you will be able to do:{code}mvn deploy -Dnpm.repo.url="" />{code} Known possibilities so far:  Realm: BearerToken: obtained by {{npm login --registry=https://nexustest/repository/npm-internal}}Realm: BasicToken: Base64-encoded "username:password"Former: BearerToken: Base64 encoded "username:password" taken from {{~/.m2/settings.xml}} (nexus' user-token) References:https://books.sonatype.com/nexus-book/reference/usertoken.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] (LMPLUGIN-3) Add possibility to pass auth method and token for the npm repository

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Light Module Maven Plugin /  LMPLUGIN-3 
 
 
 
  Add possibility to pass auth method and token for the npm repository  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 16/Mar/16 4:36 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
The current implementation uses nexus' user token obtained from ~/.m2/settings.xml to authenticate. When moving to nexus 3 MS7 we realized that this authentication method was not supported (yet). We would still like to use that method as soon as it's implemented, but for now, we will add the possibility to explicitly set the auth-method and the auth-token. 
Usage before: ```mvn deploy``` 
Additionally you will be able to do: ``` mvn deploy -Dnpm.repo.url="" -Dnpm.auth.realm="Bearer" -Dnpm.auth.token="a-b-c-d-x" ``` 
References: https://books.sonatype.com/nexus-book/reference/usertoken.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
   

[magnolia-dev] [JIRA] (MGNLUI-3749) Regression: Error flash on user/group/role creation

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3749 
 
 
 
  Regression: Error flash on user/group/role creation   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 36 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




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] Re: How to include javascript into magnolia dialog

[Jack Son (via Magnolia Forums)]

Hii all..Welcome. We are happy to inform you, we are providing real time Big 
Data Training and Primavera Training for freshers as well as experienced 
professionals. We also provide several technical related training. So join our 
institute and get bright future in IT industry. 
[url=http://www.traininginsholinganallur.in/big-data-analytics-training-in-chennai.html]Big
 Data Training in Chennai[/url] | 
[url=http://www.traininginsholinganallur.in/primavera-training-in-chennai.html]Primavera
 Training in Chennai[/url]

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=73834049-0a81-4b2f-95ba-60d383d625a7



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: