[magnolia-dev] [JIRA] (MGNLUI-3783) SwitchableField can't have a DamUploadField

2016-02-18 Thread JIRA (on behalf of Ugo La Giorgia) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ugo La Giorgia created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3783 
 
 
 
  SwitchableField can't have a DamUploadField  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 media-image.yaml, stacktrace.txt 
 
 
 

Created:
 

 18/Feb/16 6:25 PM 
 
 
 

Environment:
 

 Windows 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Ugo La Giorgia 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
ClassCastException occurs when DAMUploadField is added into SwitchableField.  
I have uncluded the dialog configuration in YAML format 
See stacktrace in attachment

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

2016-02-18 Thread JIRA (on behalf of Christopher Zimmermann) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Reopening because all files associated with a light module must be in the main/src/resources/[module-name] directory. In this case, the i18n files should be in a directory within "mtk".  I need to be able to drop the mtk directory in the webapp resources directory and have mtk work. See related ticket: https://jira.magnolia-cms.com/browse/DEV-135 
 
 
 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-74 
 
 
 
  Use i18n "best practices" in tempting essentials  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed 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] (MGNLWORKFLOW-317) Upon changing configuration of workflow manager, no workflow can be executed until restart

2016-02-18 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-317 
 
 
 
  Upon changing configuration of workflow manager, no workflow can be executed until restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Comment:
 
 I spent some time trying to evaluate both options and while Jan's suggestion of dropping the {{WorkflowManager}} instance (and implicitly the {{RuntimeManager}} it uses) seems to be the right approach I would not know how to do it, since they're both singletons whose instances are created when Magnolia starts up and destroyed when it shuts down. I might miss something here but I don't think we currently have the ability to do that at runtime. And, just for the records, there seems to be no significant overhead in doing {{JbpmWorkflowManager#startEngine()}}  (I added a new log info when it's done){code}2016-02-10 10:36:57,403 INFO  info.magnolia.module.workflow.WorkflowBaseModule  : Starting workflow engine via info.magnolia.module.workflow.jbpm.MyWorkflowManager...2016-02-10 10:36:58,055 WARN  .ruleflow.core.validation.RuleFlowProcessValidator: Process variable exception uses ObjectDataType for default type (java.lang) which could cause problems with setting variables, use dedicated type instead2016-02-10 10:37:00,450 INFO  info.magnolia.module.workflow.WorkflowBaseModule  : Workflow engine started.{code}Rich's approach fixes the issue (well, it keeps the workflow usable w/o restarting Magnolia) even though I had to add the following check at {{info.magnolia.module.workflow.jbpm.runtime.manager.MgnlRuntimeManager.init()}} {code}if (!registry.isRegistered(IDENTIFIER)) {   registry.register(this);}{code}else upon restarting the module and reinitialising the {{RuntimeManager}} one would get{code}java.lang.IllegalStateException: RuntimeManager is already registered with id default-mgnl at org.kie.internal.runtime.manager.RuntimeManagerRegistry.register(RuntimeManagerRegistry.java:23) at info.magnolia.module.workflow.jbpm.runtime.manager.MgnlRuntimeManager.init(MgnlRuntimeManager.java:101){code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message

[magnolia-dev] [JIRA] (PAGES-57) Re-allow a page with UTF-8 chars in name to be exported from pages app

2016-02-18 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-57 
 
 
 
  Re-allow a page with UTF-8 chars in name to be exported from pages app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Saigon 32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-53) Changing of filters order after migration from 5.3.5 to 5.4.4

2016-02-18 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-53 
 
 
 
  Changing of filters order after migration from 5.3.5 to 5.4.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-56) Variants Not Marked as Modified when Audience Selected

2016-02-18 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-56 
 
 
 
  Variants Not Marked as Modified when Audience Selected  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Saigon 32 
 
 
 

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-3773) SelectFieldFactory should not translate options with old I18n

2016-02-18 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3773 
 
 
 
  SelectFieldFactory should not translate options with old I18n  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.form.field.factory.SelectFieldFactory#getSelectFieldOptionDefinition}} does:# {{option.getLabel()}}: Since it's wrapped by i18n proxy and there is no translation in new message bundles, the longest key is returned.# getMessage(option.getLabel):  translates select definitions  The old translation mechanism uses this longest key returned from new i18n and looks in default UI message bundles .  Usage of {{I18nizer}} on these definitions doesn't have any effect since => We use  the  labels are already translated with  key generated by NEW i18n as  the  first (  key to translate by OLD i18n.=> This only works if there is a translation for the longest )  key , otherwise it doesn't work . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3773) SelectFieldFactory should not translate options with old I18n

2016-02-18 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3773 
 
 
 
  SelectFieldFactory should not translate options with old I18n  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.form.field.factory.SelectFieldFactory#getSelectFieldOptionDefinition}} does:# {{option.getLabel()}}: Since it's wrapped by i18n proxy and there is no translation in new message bundles, the longest key is returned.# {{getMessage(option.getLabel)}}: The old translation mechanism uses this longest key returned from new i18n and looks in default UI message bundles.=> We use the key generated by NEW i18n as the key to translate by OLD i18n.=> This only works if there is a translation for the longest key, otherwise it doesn't work. The old i18n mechanism should not be called at all since the option definition is already wrapped by i18n proxy. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3773) SelectFieldFactory should not translate options with old I18n

2016-02-18 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3773 
 
 
 
  SelectFieldFactory should not translate options with old I18n  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.form.field.factory.SelectFieldFactory#getSelectFieldOptionDefinition}} does:# {{option.getLabel()}}: Since it's wrapped by i18n proxy and there is no translation in new message bundles, the longest key is returned.#  {{  getMessage(option.getLabel) }} : The old translation mechanism uses this longest key returned from new i18n and looks in default UI message bundles.=> We use the key generated by NEW i18n as the key to translate by OLD i18n.=> This only works if there is a translation for the longest key, otherwise it doesn't work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3773) SelectFieldFactory should not translate options with old I18n

2016-02-18 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3773 
 
 
 
  SelectFieldFactory should not translate options with old I18n  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.form.field.factory.SelectFieldFactory#getSelectFieldOptionDefinition}}  does:# {{option.getLabel()}}: Since it's wrapped by i18n proxy and there is no translation in new message bundles, the longest key is returned.# getMessage(option.getLabel):   translates select definitions. Usage of {{I18nizer}} on these definitions doesn't have any effect since the labels are already translated with the first (longest) key. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3749) Regression: Error flash on user/group/role creation

2016-02-18 Thread 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 
 
 
 

Priority:
 
 Neutral Major 
 
 
 

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] (MGNLDATA-144) Validation does not work for subtype dialogs

2016-02-18 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Data Module /  MGNLDATA-144 
 
 
 
  Validation does not work for subtype dialogs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Philipp Bärfuss 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDATA-146) Setting a field as NodeNameControl and the flag sortByName does not sort by custom node name, it keeps sorting by default 'name'

2016-02-18 Thread on behalf of Michael Mühlebach 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Data Module /  MGNLDATA-146 
 
 
 
  Setting a field as NodeNameControl and the flag sortByName does not sort by custom node name, it keeps sorting by default 'name'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Philipp Bärfuss 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCKEDIT-20) The RichText field not works as expected

2016-02-18 Thread JIRA (on behalf of Revathy Varadhan) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Revathy Varadhan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 CKEditor module /  MGNLCKEDIT-20 
 
 
 
  The RichText field not works as expected  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jaroslav Simak 
 
 
 

Created:
 

 18/Feb/16 1:31 PM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Revathy Varadhan 
 
 
 
 
 
 
 
 
 
 
Hi,  
Login into your demo author website. https://demoauthor.magnolia-cms.com/.magnolia/admincentral 
Go to your tour module under configuration/modules/tours/apps/tour/  
The body field in the form of tour app is Richtext Definition. so add source = true property.  Now visit the below page  
https://demoauthor.magnolia-cms.com/.magnolia/admincentral#app:tours:detail;/magnolia-travels/Vietnam--Tradition-and-Today:edit 
You will be allowed to edit the body of tour app.  click source button --> try to embed some video for eg inside an iframe -->  like this  
Magnolia is good 
click source button again.. --> You see only Magnolia is good . What about the iframe or div pasted. You have no clue.  
When you see Inside JCR , you dont see your contents. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (MGNLGA-20) Change the Google analytics library from "ga.js" to "analytics.js"

2016-02-18 Thread JIRA (on behalf of Matic Ferjan) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matic Ferjan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-20 
 
 
 
  Change the Google analytics library from "ga.js" to "analytics.js"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Feb/16 12:58 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Matic Ferjan 
 
 
 
 
 
 
 
 
 
 
Google describes that the "ga.js" library, which magnolia still uses, is deprecated and has been replaced with "analytics.js" library. link to legacy library 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3781) ActionDefinitionKeyGenerator supports only first ancestor key

2016-02-18 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3781 
 
 
 
  ActionDefinitionKeyGenerator supports only first ancestor key  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

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] (MGNLSITE-53) Changing of filters order after migration from 5.3.5 to 5.4.4

2016-02-18 Thread on behalf of Ervín Výstup 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ervín Výstup updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-53 
 
 
 
  Changing of filters order after migration from 5.3.5 to 5.4.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Comment:
 
 A comment with security level 'magnolia-intl-staff' was removed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3778) Adjust tests to changes by MAGNOLIA5522

2016-02-18 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3778 
 
 
 
  Adjust tests to changes by MAGNOLIA5522  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Fix 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] (MGNLSITE-53) Changing of filters order after migration from 5.3.5 to 5.4.4

2016-02-18 Thread on behalf of Ervín Výstup 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ervín Výstup updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-53 
 
 
 
  Changing of filters order after migration from 5.3.5 to 5.4.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ervín Výstup 
 
 
 

Project:
 
 Support -  Magnolia  Site Module 
 
 
 

Key:
 
 SUPPORT MGNLSITE - 5705 53 
 
 
 

Issue Type:
 
 Support Request Bug 
 
 
 

Workflow:
 
 Support New Product Dev  Workflow 
 
 
 

Component/s:
 
 Installation, Upgrade and migration 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3778) Adjust tests to changes by MAGNOLIA5522

2016-02-18 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3778 
 
 
 
  Adjust tests to changes by MAGNOLIA5522  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved 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-3764) I18n Key generators should be consistent

2016-02-18 Thread JIRA (on behalf of Evzen Fochr) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3764 
 
 
 
  I18n Key generators should be consistent  
 
 
 
 
 
 
 
 
 

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-676) mgnl-conf-2016 workshop#

2016-02-18 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-676 
 
 
 
  mgnl-conf-2016 workshop#   
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 This story is a JIRA-wise high-level overview for all the tasks to be done for [*Workshop #2 - Dive into content pools with Magnolia*|https://conference.magnolia-cms.com/2016/basel/workshops.html] Task overview:- Create example content app which allows to categorize its content items- Create an AngularJS example doing which is able to read and filter data form the content app- Create a wiki page for the workshop participants which collects all the relevant infos for them 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-676) mgnl-conf-2016 workshop#

2016-02-18 Thread JIRA (on behalf of Christoph Meier) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-676 
 
 
 
  mgnl-conf-2016 workshop#   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Feb/16 10:18 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christoph Meier 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
This story is a JIRA-wise high-level overview for all the tasks to be done for Workshop #2 - Dive into content pools with Magnolia 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent

[magnolia-dev] [JIRA] (MGNLUI-3781) ActionDefinitionKeyGenerator supports only first ancestor key

2016-02-18 Thread on behalf of Roman Kovařík 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3781 
 
 
 
  ActionDefinitionKeyGenerator supports only first ancestor key  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Summary:
 
 ActionDefinitionKeyGenerators support ActionDefinitionKeyGenerator supports  only first ancestor key 
 
 
 

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-3585) Action bar is not well structured when there are many actions

2016-02-18 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3585 
 
 
 
  Action bar is not well structured when there are many actions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sang Ngo Huu 
 
 
 

Comment:
 
 For a hack of displaying multiple section (MGNLUI-3626): Action for {{Asset app}} still blank when selecting mixed items 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-3782) TreeView: Adding a property 'value' to a node, it's node also displays the same value. (Used for StaticField)

2016-02-18 Thread JIRA (on behalf of Christian Ringele) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3782 
 
 
 
  TreeView: Adding a property 'value' to a node, it's node also displays the same value. (Used for StaticField)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 PropertyValue.png 
 
 
 

Components:
 

 forms, tree/list 
 
 
 

Created:
 

 18/Feb/16 8:57 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The for field static expects to properties: 
 

label