[magnolia-dev] [JIRA] (DOCU-1013) Release notes for 5.5.4

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1013  
 
 
  Release notes for 5.5.4   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 *Tracking*: https://docs.google.com/spreadsheets/d/1RPuH0sQbLNXHwFhNg8FjtZ-tj2uUYaTAdDW4XZUVHLk/edit?pref=2=1#gid=841967187*Changelog*: https://jira.magnolia-cms.com/issues/?filter=16837*Filter*: https://jira.magnolia-cms.com/issues/?filter=16853Planned for week beginning May 8th. *Result*: https://documentation.magnolia-cms.com/display/DOCS/Release+notes+for+Magnolia+CORE+5.5.4  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] Re: Using Inheritance for TWO Templates

[Christoph Meier (via Magnolia Forums)]

Hello Giancarlo

What is a "TWO template"?

Note that you also can use a prototype with the community edition (CE).
On CE you have only one site - but on this site, you can define a prototype.
Depending on the bundle or webapp you are using, the site on a CE bundle maybe 
optimized for travel demo. But you can configure it for your own requirements.


Your last sentence ...
>> I also can't use the "Site" app, since the module is a companion to a normal 
>> Web site, which most likely will use that allowed one Site spot. <<
... i do not understand.

Btw. I recommend to use the latest version - atm this would be Magnolia 5.5.4

Further reading:

- https://documentation.magnolia-cms.com/display/DOCS/Site+definition
- https://documentation.magnolia-cms.com/display/DOCS/Releases
- 
https://documentation.magnolia-cms.com/display/DOCS/Bundles+and+webapps#Bundlesandwebapps-ListofpreconfiguredMagnoliabundles

i hope this helps,
kind regards,
 Christoph

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=5ed8f53f-9a0f-41e0-9d6c-bb91e7b511c9



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] Using Inheritance for TWO Templates

[Giancarlo (via Magnolia Forums)]

I am testing Magnolie 5.5.1 CE and am stuck with the inheritance feature. If I 
create child pages with the same template, all is fine.
Is it possible, in [b]Mg CE[/b], to share inheritance among TWO templates? In 
an EE version I would use "prototype". I also can't use the "Site" app, since 
the module is a companion to a normal Web site, which most likely will use that 
allowed one Site spot.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=5ed8f53f-9a0f-41e0-9d6c-bb91e7b511c9



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-293) i18n: German labels are missing

[JIRA (on behalf of Maria Fernanda Acero)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maria Fernanda Acero created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Form Module /  MGNLFORM-293  
 
 
  i18n: German labels are missing   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Form-labels.png  
 
 
Created: 
 08/May/17 4:26 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maria Fernanda Acero  
 

  
 
 
 
 

 
 Some german labels are missing: "NEW SUGARCRM FORMULARGRUPPENFELDER COMPONENT" "SUGARCRM FORMULARGRUPPENFELDER"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (FORMDB-18) Cannot map attachments to form fields (when form has multiple attachments)

[JIRA (on behalf of Fadi Wissa)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fadi Wissa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-18  
 
 
  Cannot map attachments to form fields (when form has multiple attachments)   
 

  
 
 
 
 

 
Change By: 
 Fadi Wissa  
 
 
Attachment: 
 storeAttachments modification.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4203) JcrNewNodeAdapter#isNew should not return hardcoded true

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4203  
 
 
  JcrNewNodeAdapter#isNew should not return hardcoded true
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 A more correct way Before saving  to  reflect the actual status of a  JCR  {{JcrNewNodeAdapter #isNew }}  would be to return the reverse value of the  returns  {{ appliedChanges}} field. That is initially {{false}} but becomes {{ true}}  as soon as the new node is saved to JCR . Saving to JCR doesn't necessarily mean that e.g. an app (or subapp) is done with the adapter, therefore, after the first save, subsequent calls to {{JcrNewNodeAdapter#isNew}} should return {{false}} in order to avoid incorrect or unexpected  behaviour in code relying on that method. To the objection that changing the behaviour of {{JcrNewNodeAdapter#isNew}} now may cause unexpected behaviour in code relying on the fact that it always returns {{true}} we could reply by saying that we would just make the method honour its semantics as per javadoc at {{info.magnolia.ui.vaadin.integration.ItemAdapter#isNew}}  {code}@return true if it's a new Item (not already persisted).{code}which basically is the same as {{javax.jcr.Item#isNew}}{code}Returns true if this is a new item, meaning that it existsonly in transient storage on the Session and has not yet been saved.{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

[magnolia-dev] [JIRA] (MGNLUI-4203) JcrNewNodeAdapter#isNew should not return hardcoded true

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4203  
 
 
  JcrNewNodeAdapter#isNew should not return hardcoded true
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 A more correct way to reflect the actual status of a {{JcrNewNodeAdapter}} would be to return the reverse value of the {{appliedChanges}} field. That is initially {{false}} but becomes {{true}} as soon as the new node is saved to JCR. Saving to JCR doesn't necessarily mean that e.g. an app (or subapp) is done with the adapter, therefore, after the first save, subsequent calls to {{JcrNewNodeAdapter#isNew}} should return {{false}} in order to avoid incorrect or unexpected  behaviour in code relying on that method. To the objection that changing the behaviour of {{JcrNewNodeAdapter#isNew}} now may cause unexpected behaviour in code relying on the fact that it always returns {{true}} we could reply by saying that we would just make the method honour its semantics as per javadoc at {{info.magnolia.ui.vaadin.integration.ItemAdapter#isNew}}  {code}@return true if it's a new Item (not already persisted).{code}which basically is the same as {{javax.jcr.Item#isNew}}{code}Returns true if this is a new item, meaning that it existsonly in transient storage on the   Session   and has not yet been saved.{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
 

[magnolia-dev] [JIRA] (MGNLUI-4203) JcrNewNodeAdapter#isNew should not return hardcoded true

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4203  
 
 
  JcrNewNodeAdapter#isNew should not return hardcoded true
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 A more correct way to reflect the actual status of a {{JcrNewNodeAdapter}} would be to return the reverse value of the {{appliedChanges}} field. That is initially {{false}} but becomes {{true}} as soon as the new node is saved to JCR. Saving to JCR doesn't necessarily mean that e.g. an app (or subapp) is done with the adapter, therefore, after the first save, subsequent calls to {{JcrNewNodeAdapter#isNew}} should return {{false}} in order to avoid incorrect or unexpected  behaviour in code relying on that method. To the objection that changing the behaviour of {{JcrNewNodeAdapter#isNew}} now may cause unexpected behaviour in code relying on the fact that it always returns {{true}} we could reply by saying that we would just make the method honour its semantics as per javadoc at {{info.magnolia.ui.vaadin.integration.ItemAdapter#isNew}}  { quote code }@return true if it's a new Item (not already persisted).{ quote code } which basically is the same as {{javax.jcr.Item#isNew}}{code}Returns true if this is a new item, meaning that it existsonly in transient storage on the Session and has not yet been saved.{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

[magnolia-dev] [JIRA] (MGNLUI-4203) JcrNewNodeAdapter#isNew should not return hardcoded true

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4203  
 
 
  JcrNewNodeAdapter#isNew should not return hardcoded true
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Fix Version/s: 
 5.5.5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4203) JcrNewNodeAdapter#isNew should not return hardcoded true

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4203  
 
 
  JcrNewNodeAdapter#isNew should not return hardcoded true
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Comment: 
 Looking closer when changes are applied the node isn't persisted yet, rather it's added to its parent (which does exist in JCR) but  it's only transient in the current JCR session. Only {{session.save()}} will persist it to JCR. So I'm afraid we can't do this without changing the meaning of {{new}} in this context (sadpanda).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (FORMDB-18) Cannot map attachments to form fields (when form has multiple attachments)

[JIRA (on behalf of Fadi Wissa)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fadi Wissa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-18  
 
 
  Cannot map attachments to form fields (when form has multiple attachments)   
 

  
 
 
 
 

 
Change By: 
 Fadi Wissa  
 
 
Summary: 
 Cannot mapattachments to form fields (when form has multiple attachments)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (FORMDB-18) Cannot map attachments to form fields (when form has multiple attachments)

[JIRA (on behalf of Fadi Wissa)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fadi Wissa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-18  
 
 
  Cannot map attachments to form fields (when form has multiple attachments)   
 

  
 
 
 
 

 
Change By: 
 Fadi Wissa  
 

  
 
 
 
 

 
 When I have two (or more) attachments on the same form,  after the user submits the form,  I cannot tell which attachment belongs to which field.   Let's say there's a customer logo attachment  field  and a customer background image attachment  field .   After the data is submitted and saved in the DB I cannot tell which attachment file belongs to which "field" in the original form.  My recommendation would be to keep the original file name as uploaded by the user, but to include the attachment mgnl:asset node within another node/folder that has the name of the field the file belongs to.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: 

[magnolia-dev] [JIRA] (FORMDB-18) Cannot map

[JIRA (on behalf of Fadi Wissa)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fadi Wissa created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Form2DB /  FORMDB-18  
 
 
  Cannot map
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Marvin Kerkhoff  
 
 
Created: 
 08/May/17 12:37 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Fadi Wissa  
 

  
 
 
 
 

 
 When I have two (or more) attachments on the same form, I cannot tell which attachment belongs to which field. Let's say there's a customer logo attachment and a customer background image attachment. After the data is submitted and saved in the DB I cannot tell which attachment file belongs to which "field" in the original form. My recommendation would be to keep the original file name as uploaded by the user, but to include the attachment mgnl:asset node within another node/folder that has the name of the field the file belongs to.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[magnolia-dev] [JIRA] (DOCU-1016) Reflect "JCR Export improvements"

[JIRA (on behalf of Julie Legendre)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julie Legendre updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1016  
 
 
  Reflect "JCR Export improvements"   
 

  
 
 
 
 

 
Change By: 
 Julie Legendre  
 
 
Assignee: 
 Julie Legendre  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4205) Setting "selected" is true in Select field doesn't work in case of existing item

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oanh Thai Hoang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4205  
 
 
  Setting "selected" is true in Select field doesn't work in case of existing item   
 

  
 
 
 
 

 
Change By: 
 Oanh Thai Hoang  
 
 
Affects Version/s: 
 5.5.3  
 
 
Affects Version/s: 
 5.4.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4180) Conduct UI-related IoC binding without Guice machinery ending up in the http session

[JIRA (on behalf of Philip Mundt)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Philip Mundt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4180  
 
 
  Conduct UI-related IoC binding without Guice machinery ending up in the http session   
 

  
 
 
 
 

 
Change By: 
 Philip Mundt  
 
 
Fix Version/s: 
 5.5.5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4202) Make Zip upload behavior configurable

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oanh Thai Hoang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4202  
 
 
  Make Zip upload behavior configurable   
 

  
 
 
 
 

 
Change By: 
 Oanh Thai Hoang  
 
 
Fix Version/s: 
 5.4.13  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4203) JcrNewNodeAdapter#isNew should not return hardcoded true

[on behalf of Michael Mühlebach]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4203  
 
 
  JcrNewNodeAdapter#isNew should not return hardcoded true
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 94 , Basel 95  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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