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

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 UI-related IoC bindings should be done ideally once and should manipulate/utilise http and Vaadin sessions through custom Guice scopes rather then emulating such scopes via multiple Injector instances (see linked wiki entry for more details).For the release notes:- All the UI related component bindings are now served by a single GuiceComponentProvider. Where before we were creating GuiceComponentProviders on demand (for apps, sub-apps etc), we now merely create a cheap ComponentProvider which delegates to the single one and  merely  sets its context.   
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLUI-4180) Conduct UI-related IoC binding without Guice machinery ending up in the http session

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 UI-related IoC bindings should be done ideally once and should manipulate/utilise http and Vaadin sessions through custom Guice scopes rather then emulating such scopes via multiple Injector instances (see linked wiki entry for more details). For the release notes:- All the UI related component bindings are now served by a single GuiceComponentProvider. Where before we were creating GuiceComponentProviders on demand (for apps, sub-apps etc), we now merely create a cheap ComponentProvider which delegates to the single one and merely sets its context.   
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLUI-4180) Conduct UI-related IoC binding without Guice machinery ending up in the http session

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Release notes required: 
 Yes  
 

  
 
 
 
 

 
 
 

 
 
 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-4204) Integrate IoC improvements

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4204  
 
 
  Integrate IoC improvements   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Affects Versions: 
 5.5.3  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 07/May/17 8:56 PM  
 
 
Fix Versions: 
 5.5.5  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 After the approval of the effort done in the scope of MGNLUI-4180, we need to make several finalisation steps in order to be able to integrate the effort: 
 
push more unit tests than there is a the moment 
make sure all the new classes have a decent amount of JavaDoc 
organise the satellite effort in main 
run load tests and make several screenshots supporting the effort results 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

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

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
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-4180) Conduct UI-related IoC binding without Guice machinery ending up in the http session

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 5.2.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 30/Mar/17 2:28 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 UI-related IoC bindings should be done ideally once and should manipulate/utilise http and Vaadin sessions through custom Guice scopes rather then emulating such scopes via multiple Injector instances (see linked wiki entry for more details).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-4173) Provide support for app and sub-app close confirmation requirement

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Provide support for app and sub-app close confirmation requirement
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 There's a handy support for guarding the Currently there is no easy way to guard apps/  sub- app apps  close  control  controls  with a confirmation dialog  (asks whether , that would warn  the  user really wants to close  users of potential data loss. One can implement such support for  the sub- app tab desHowever apps ,  there's currently no way to do the same for the whole app  but that would involve overriding of some rather low  -  currently level components like  {{ MagnoliaShell SubAppContext }}  will just instruct  itself. There should be a clear API/point of interception where  the  app controller to stop the app and there's no way to interfere this process  close event could be aborted .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   

[magnolia-dev] [JIRA] (MGNLUI-4173) Provide support for app and sub-app close confirmation requirement

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Provide support for app and sub-app close confirmation requirement
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Summary: 
 Provide support for app  and sub-app  close confirmation requirement   
 

  
 
 
 
 

 
 
 

 
 
 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-4173) Provide support for app and sub-app close confirmation requirement

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Provide support for app and sub-app close confirmation requirement
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 There's a handy support for guarding the sub-app close control with a confirmation dialog (asks whether the user really wants to close the sub-app tab  despite possible data loss). However  desHowever , there's currently no way to do the same for the whole app - currently {{MagnoliaShell}} will just instruct the app controller to stop the app and there's no way to interfere this process.  
 

  
 
 
 
 

 
 
 

 
 
 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-4173) Provide support for app close confirmation requirement

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Provide support for app close confirmation requirement
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 Currently, We can show confirmation dialogs to users within an subapp There's a handy support  for  instance attaching it to  guarding the sub-app close control with  a  button or similar works. However, we do not have  confirmation dialog (asks whether  the  functionality to show to the  user  when one  really  wants to close  an  the sub-  app . Although {{info.magnolia.ui.api.app.App}} interface provides #stop(  tab despite possible data loss )  method . However ,  we can  there ' t simply override it and s currently no way to  do the  trick there like subapp. The reason being that there are some listeners attached to  same for the whole app - currently  {{ info.magnolia.ui.api.shell.Shell MagnoliaShell }}  will just instruct the app controller to stop the app  and  they are not interceptable in that sense  there's no way to interfere this process .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

[magnolia-dev] [JIRA] (MGNLUI-4173) Provide support for app close confirmation requirement

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Provide support for app close confirmation requirement
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Summary: 
 Show confirmation dialog when user tries to close an Provide support for  app  close confirmation requirement   
 

  
 
 
 
 

 
 
 

 
 
 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-4169) Simplify FieldDefinitionKeyGenerator's logic of parent names collection

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4169  
 
 
  Simplify FieldDefinitionKeyGenerator's logic of parent names collection   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 20/Mar/17 4:38 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 {FieldDefinitionKeyGenerator#getParentName()}} method can be replaced with a AbstractI18nKeyGenerator#getIdOrNameForUnknownRoot(..) with a little bit of refactoring and care. This would allow us to simplify the internal logic of the field definition key generator.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-2824) AbstractFormKeyGenerator API should be complemented with getParentName(...) method

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-2824  
 
 
  AbstractFormKeyGenerator API should be complemented with getParentName(...) method   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 There exists {{AbstractI18nKeyGenerator#getIdOrNameForUnknownRoot}} method which resolves the name of the given definition's root parent.However, there is sometimes a need to resolve the name of the direct parent. For instance, there is {{FieldDefinitionKeyGenerator#getParentName}} method which does it. That method could  be  a nice improvement to the AbstractI18nKeyGenerator API.  
 

  
 
 
 
 

 
 
 

 
 
 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-4168) FieldDefinitionKeyGenerator#getParentName should emit log messages less severe than warnings

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4168  
 
 
  FieldDefinitionKeyGenerator#getParentName should emit log messages less severe than warnings   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 Currently when field's keys are populated, the generator walks from parent to parent and collects their names (via {{FieldDefinitionKeyGenerator#getParentName}} which merely attempts to call a {{getName()}} method). Under certain circumstances, some parents in such chain may not produce the name for some reason.One example could be a {{ContentDefinition}}:  { { code:java} @ I18nable I18nabe public class ContentDefinition {private List outlineFields;  private String defaultBlock;  private List blocks;public List getOutlineFields() {return outlineFields;}public void setOutlineFields(List outlineFields) {this.outlineFields = outlineFields;} public String getDefaultBlock() { ...  return defaultBlock; } public void setDefaultBlock(String defaultBlock)  { this.defaultBlock = defaultBlock; code } public List Such definition is included in an article editor sub-app descriptor and delivers such information as block identifiers and also the collection of the outline field definitions. Those fields should be i18n-izable and sufficient keys could look like {{ < String app >  getBlocks() ..}}. All works fine except for  { return blocks; {ContentDefinition } } does not provide its name which results in a warning similar to the following:  public void setBlocks {{..:Cannot obtain name of parent object: info.magnolia.editor.content.ContentDefinition$$EnhancerByCGLIB$$614a4d1b.getName ( List blocks )  { }}.  this We don't care about the content definition's name and field key generator doesn't fail on its absence - only emits the warning and moves on . blocks = blocks;  }  }}} Shouldn't we just lower the severity of the log statement to debug for such cases?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[magnolia-dev] [JIRA] (MGNLUI-4168) FieldDefinitionKeyGenerator#getParentName should emit log messages less severe than warnings

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4168  
 
 
  FieldDefinitionKeyGenerator#getParentName should emit log messages less severe than warnings   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 
 
Created: 
 20/Mar/17 10:44 AM  
 
 
Fix Versions: 
 5.5.3  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 Currently when field's keys are populated, the generator walks from parent to parent and collects their names (via FieldDefinitionKeyGenerator#getParentName which merely attempts to call a getName() method). Under certain circumstances, some parents in such chain may not produce the name for some reason. One example could be a ContentDefinition: {{ @I18nable public class ContentDefinition {  private List outlineFields;  private String defaultBlock;  private List blocks;  public List getOutlineFields()  { return outlineFields; }  public void setOutlineFields(List outlineFields)  { this.outlineFields = outlineFields; }  public String getDefaultBlock()  { return defaultBlock; }  public void setDefaultBlock(String defaultBlock)  { this.defaultBlock = defaultBlock; }  public List getBlocks()  { return blocks; }  public void setBlocks(List blocks)  { this.blocks = blocks; } } }}  
 

  
 
 
 
 

 
 
 

  

[magnolia-dev] [JIRA] (MGNLUI-4167) Shell shortcuts interfere with inline editing

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4167  
 
 
  Shell shortcuts interfere with inline editing   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Sprint: 
 Basel 87  
 

  
 
 
 
 

 
 
 

 
 
 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-4167) Shell shortcuts interfere with inline editing

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4167  
 
 
  Shell shortcuts interfere with inline editing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 
 
Created: 
 17/Mar/17 12:58 PM  
 
 
Fix Versions: 
 5.5.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 Shell shortcuts (1-3 and 9 and 0) won't trigger if focused element is input but do not take 'contenteditable' property in account.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
  

[magnolia-dev] [JIRA] (MGNLUI-4166) Update CKEditor wrapper add-on version to 7.11.1

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4166  
 
 
  Update CKEditor wrapper add-on version to 7.11.1   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Sprint: 
 Basel 87  
 

  
 
 
 
 

 
 
 

 
 
 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-4166) Update CKEditor wrapper add-on version to 7.11.1

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4166  
 
 
  Update CKEditor wrapper add-on version to 7.11.1   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 
 
Created: 
 16/Mar/17 8:26 PM  
 
 
Fix Versions: 
 5.3.3  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 The latest version of the add-on brings in CKEditor 4.6.2, which is required by the content editor.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 
 

 
 
 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-4158) FieldDefinitionKeyGenerator produces incomplete keys '.fieldName.label' for fields outside of a dialogs/tabs

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4158  
 
 
  FieldDefinitionKeyGenerator produces incomplete keys '.fieldName.label' for fields outside of a dialogs/tabs   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 
 
Assignee: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 
 

 
 
 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-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 It was noticed that if the text area stretcher is attached to a field which belongs to a layout which is not our FormView - the extension fails on the client-side and causes the whole layout to break.The cause for that is the usage of the {{form}} field which is initialised in {{TextAreaStretcherConnector#initFormView}} - the field may end up being null, but  than  then  in the rest of the class it is used as if it non-null. The right way of doing it would probably be that the extension does nothing and doesn't show itself if it is not in a Magnolia dialog (all the calculations would anyway be wrong).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-4130) TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4130  
 
 
  TextAreaStretcher causes client-side NPE when used in a non-FormView surrounding   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 01/Feb/17 1:08 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 It was noticed that if the text area stretcher is attached to a field which belongs to a layout which is not our FormView - the extension fails on the client-side and causes the whole layout to break. The cause for that is the usage of the form field which is initialised in TextAreaStretcherConnector#initFormView - the field may end up being null, but than in the rest of the class it is used as if it non-null.  The right way of doing it would probably be that the extension does nothing and doesn't show itself if it is not in a Magnolia dialog (all the calculations would anyway be wrong).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

[magnolia-dev] [JIRA] (MGNLUI-4118) FormFieldSectionConnector attempts to restrict the parent connector type to the form tab

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Pchelintcev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4118  
 
 
  FormFieldSectionConnector attempts to restrict the parent connector type to the form tab   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 11/Jan/17 12:56 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Aleksandr Pchelintcev  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCE-65) Create README.md for the integration tests sub-project

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-65 
 
 
 
  Create README.md for the integration tests sub-project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 14/Nov/16 3:22 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
I personally tend to forget the possible combinations of the Maven options for various integration test runs. Since our BitBucket supports nice rendering of the README.md files in the project source browser - I propose creating a simple description that'll point to the relevant wiki resources and maybe will give a tl;dr gist of the available profiles. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (CFGUI-55) Re-iterate over Definition app's data interfaces names and signatures

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-55 
 
 
 
  Re-iterate over Definition app's data interfaces names and signatures  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 04/Nov/16 1:56 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 

Id interface has unnecessary generic parameter
 

redundant properties like style have to go (probably - this is not certain)
 

name Id is in general not very suitable to the way things are in the app at the moment - it ahs been chosen when the app was in poc state and all the data was bound to a Vaadin container (which indeed operates over ids). Now a more generic word would be better I guess (e.g. entry or smth)
 

etc...
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

[magnolia-dev] [JIRA] (CFGUI-51) Definitions app overview tree toolbar is not aware of the light modules

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-51 
 
 
 
  Definitions app overview tree toolbar is not aware of the light modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 View filters don't know Definitions app overview tree toolbar is not aware of the  light modules 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-52) Provide a filter bar for problem list view

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-52 
 
 
 
  Provide a filter bar for problem list view  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 31/Oct/16 10:02 AM 
 
 
 

Fix Versions:
 

 1.0 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
It would be really helpful if the problems could be filtered by the module/definition name/severity type and some such. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-4043) Since Vaadin update (7.7.0?) app-specific themes sometimes aren't applied

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4043 
 
 
 
  Since Vaadin update (7.7.0?) app-specific themes sometimes aren't applied   
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Basel  68  67 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4043) Since Vaadin update (7.7.0?) app-specific themes sometimes aren't applied

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4043 
 
 
 
  Since Vaadin update (7.7.0?) app-specific themes sometimes aren't applied   
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-45) Polish problems subapp

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-45 
 
 
 
  Polish problems subapp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-50) Build unique url fragment in content connector

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-50 
 
 
 
  Build unique url fragment in content connector  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Cedric Reichenbach Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4043) Since Vaadin update (7.7.0?) app-specific themes sometimes aren't applied

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4043 
 
 
 
  Since Vaadin update (7.7.0?) app-specific themes sometimes aren't applied   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Oct/16 9:33 AM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
When admincentral starts-up with an app fragment specified (=> by default it displays some app instead of applauncher), the app theme is not applied right away. 
The reason is that by the time the method which is supposed to set up style injection is invoked, the app view is already in the component hierarchy. The method unfortunately instructs the style to be attached when the app view attaches => it never happens (until app re-start), since app is already attached.  
The solution would be to attach the stylesheet right away if the app view itself is attached and postpone it (like we do now) 

[magnolia-dev] [JIRA] (CFGUI-49) Prevent scrollbar from jumping back up when toggling an element open

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-49 
 
 
 
  Prevent scrollbar from jumping back up when toggling an element open  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-44) Configuration overview tree collapses during inter-app navigation

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-44 
 
 
 
  Configuration overview tree collapses during inter-app navigation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 30/Sep/16 3:58 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-90) Open-in-tab button does not open correct url

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-90 
 
 
 
  Open-in-tab button does not open correct url  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 

Fix Version/s:
 
 5.4.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-90) Open-in-tab button does not open correct url

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-90 
 
 
 
  Open-in-tab button does not open correct url  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.4.10 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-24) Define the place and level of integration with definiton decoration functionality

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-90) Open-in-tab button does not open correct url

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-90 
 
 
 
  Open-in-tab button does not open correct url  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  61  62 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  61  62 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  61  62 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-80) Adapt pages app to Content-Connector concept

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-80 
 
 
 
  Adapt pages app to Content-Connector concept  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4018) "Move Inside" button's state is incorrecly handled

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4018 
 
 
 
  "Move Inside" button's state is incorrecly handled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon 62 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3668) MultiValueFields must react on the changes of underlying datasource

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3668 
 
 
 
  MultiValueFields must react on the changes of underlying datasource  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 This issue is a follow-up of the fix/improvement done in the scope of MGNLUI-3633.  However, the  The  situation is far from ideal - even though the underlying datasource does not get overridden as a consequence of the fields not being in synch with the model, the fields still don't get updated if the underlying data changes.Vaadin's ValueChangeEvents should be sent in appropriate situations and fields, especially MultiFields must react on such changes and update their state/UI.  For the future assignee:One should delete the workarounds ( addition of  markAsDirty()  calls ) which  were  introduced with MGNLUI-3844. Have If  this ticket solves the root problem, those shouldn't be needed anymore. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3976) Copied path from bottom of the Pages app includes labels from actionbar

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3976 
 
 
 
  Copied path from bottom of the Pages app includes labels from actionbar  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 After triple-click on path there is path copied with labels from actionbar (Chrome)Tested on Magnolia 5.3.13 and 5.4.7On Safari, Firefox works as intendedWhen you mouse-select that path ( e.g. mouse drag ) works as intended As it was pointed by [~cedric] in the comments - this issue is caused by the Chromium bug:https://bugs.chromium.org/p/chromium/issues/detail?id=511962 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3976) Copied path from bottom of the Pages app includes labels from actionbar

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3976 
 
 
 
  Copied path from bottom of the Pages app includes labels from actionbar  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 After triple-click on path there is path copied with labels from actionbar (Chrome)Tested on Magnolia 5.3.13 and 5.4.7On Safari, Firefox works as intendedWhen you mouse-select that path ( e.g. mouse drag ) works as intended *UPD* As it was pointed by [~cedric] in the comments - this issue is caused by the Chromium bug:https://bugs.chromium.org/p/chromium/issues/detail?id=511962  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-80) Adapt pages app to Content-Connector concept

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-80 
 
 
 
  Adapt pages app to Content-Connector concept  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Espen Jervidalo Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3898) Reveal moved item in the "move" dialog

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  60  61 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3976) Copied path from bottom of the Pages app includes labels from actionbar

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3976 
 
 
 
  Copied path from bottom of the Pages app includes labels from actionbar  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  60  61 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3464) Provide a way to navigate to a node in a tree based on a path

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3464 
 
 
 
  Provide a way to navigate to a node in a tree based on a path  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  60  61 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-2542) Dynamic forms & cross-field validation

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2542 
 
 
 
  Dynamic forms & cross-field validation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  60  61 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3900) Show the root node in the "move" dialog

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  60  61 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3864) Allow multiple reorder actions with keyboard on MultiValueField

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3864 
 
 
 
  Allow multiple reorder actions with keyboard on MultiValueField  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Saigon  60  61 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-32) Fix and streamline configuration source type resolution and presentation in overview sub-app

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-32 
 
 
 
  Fix and streamline configuration source type resolution and presentation in overview sub-app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 The following issue has to be addressed- Definitions that are hot-fixed within resources-app are considered as config-based definitions => *show file action broken*This happens due to a mis-understanding of how does the notion of configuration source correlates with {{ResourceOrigins}} and with JCR *_config_* and _*resources*_ workspaces. The following logic should be used:- Anything that is served via the {{ResourceOrigin}} (this includes JCR _resources_ workspace) is treated as a file-based definition- Anything that comes from JCR _config_ workspace is treated as a JCR definition.Luckily to simplify this - MAGNOLIA-6081 brings us a new simple API which allows to ask a {{DefinitionProvider}} - which config source it initially is coming from. As a complement to this effort - we should re-purpose the *Source* column in the overview table - let it omit the information about the exact origin of the file-based definition (i.e. FS, classpath or resources workspace), they all are in the end are files. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-32) Fix and streamline configuration source type resolution and presentation in overview sub-app

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-32 
 
 
 
  Fix and streamline configuration source type resolution and presentation in overview sub-app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 The following issue has to be addressed- Definitions that are hot-fixed within resources-app are considered as config-based definitions => *show file action broken*This happens due to a mis-understanding of how does the notion of configuration source correlates with {{ResourceOrigins}} and with JCR *_config_* and _*resources*_ workspaces . The following logic should be used:- Anything that is served via the {{ResourceOrigin}} (this includes JCR _resources_ workspace) is treated as a file-based definition- Anything that comes from JCR _config_ workspace is treated as a JCR definition.Luckily to simplify this - MAGNOLIA-6081 brings us a new simple API which allows to ask a {{DefinitionProvider}} - which config source it initially is coming from. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-32) Fix and streamline configuration source type resolution and presentation in overview sub-app

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-32 
 
 
 
  Fix and streamline configuration source type resolution and presentation in overview sub-app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 The following issue has to be addressed- Definitions that are hot-fixed within resources-app are considered as config-based definitions => *show file action broken*This happens due to a mis-understanding of how does the notion of configuration source correlates with {{ResourceOrigins}} and with JCR *_config_* and _*resources*_ workspaces 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-32) Fix and streamline configuration source type resolution and presentation in overview sub-app

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-32 
 
 
 
  Fix and streamline configuration source type resolution and presentation in overview sub-app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 Definitions that are hot Fix and streamline configuration source type resolution and presentation in overview sub - fixed within resources- app  are considered as config-based definitions - Show file action broken 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-83) Find a way to customise page editor CSS

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 Find a way  how  to  brought additional css for  customise  page editor  CSS  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3981) Create a dedicated dialog-bootstrapping action for JCR import

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3981 
 
 
 
  Create a dedicated dialog-bootstrapping action for JCR import  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 11/Aug/16 5:23 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
JCR import functionality currently hijacks the OpenCreateDialogAction to bootstrap a form dialog. One saves several lines of code, but the dialog's callback is mis-preset and acts for a different purpose.  
We should create an action which would exclusively serve the purpose of JCR import and wouldn't interfere with how SaveImportDialogAction works. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (LOGTOOLS-18) Adapt log tools app view logic to Vaadin 7.6

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-18 
 
 
 
  Adapt log tools app view logic to Vaadin 7.6  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 1.0.2 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 

Created:
 

 04/Aug/16 9:45 PM 
 
 
 

Fix Versions:
 

 1.0.3 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
It looks like Grid's selection logic has changed (has been fixed) since Vaadin version 7.4 and now the LogListViewImpl view fails incorrectly: 
 

when row is selected via checkbox, the item click listener is not invoked => the action button states aren't updated.
 
 
As a solution we can easily extract a dedicated selection listener for buttons update and handle only the remaining logic in the row click listener. 
 
 
 
 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3687) Dialogs show unnecessary scrollbars in some browsers

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3687 
 
 
 
  Dialogs show unnecessary scrollbars in some browsers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Hieu Nguyen Duc Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3957) Provide human readable definition type captions

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3957 
 
 
 
  Provide human readable definition type captions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Jul/16 12:38 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Once the dependant main issue is resolved - we should provide human readable captions for app, dialog, media editor, field type registries. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (CFGUI-19) Make filter combos captions human-friendly

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-19 
 
 
 
  Make filter combos captions human-friendly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-20) Make appearance of filter combos lighter so that when they are used n conjunction with labels they form some sort of a sentence

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-20 
 
 
 
  Make appearance of filter combos lighter so that when they are used n conjunction with labels they form some sort of a sentence  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PROCRES-3) FTL and YAML files are exposed over the /resources URI2RepositoryMapping

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-3 
 
 
 
  FTL and YAML files are exposed over the /resources URI2RepositoryMapping  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-2498) Make Page Editor support IE8

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2498 
 
 
 
  Make Page Editor support IE8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PROCRES-2) Subnodes are not appended

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Processed resources /  PROCRES-2 
 
 
 
  Subnodes are not appended  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLGA-13) As a user I am able to Google Analytics Experiments API

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-13 
 
 
 
  As a user I am able to Google Analytics Experiments API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLRSSAGG-152) Investigate influence of FastRSSFeedFetcherTest on other unit tests, re-enable it.

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-152 
 
 
 
  Investigate influence of FastRSSFeedFetcherTest on other unit tests, re-enable it.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLRSSAGG-149) Feed subscriptions component does not work

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-149 
 
 
 
  Feed subscriptions component does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLGA-14) As a user I can log in into my Google account and obtain the basic analytics information without moving away from Magnolia

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Google Analytics /  MGNLGA-14 
 
 
 
  As a user I can log in into my Google account and obtain the basic analytics information without moving away from Magnolia  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLRSSAGG-148) FeedChannel value is not correctly migrated

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-148 
 
 
 
  FeedChannel value is not correctly migrated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-8) Visual changes to the filter bar

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-8 
 
 
 
  Visual changes to the filter bar  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3644) App viewport curtain is not attached when an app is closed from the server-side via AppController

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3644 
 
 
 
  App viewport curtain is not attached when an app is closed from the server-side via AppController  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Fix Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3644) App viewport curtain is not attached when an app is closed from the server-side via AppController

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3644 
 
 
 
  App viewport curtain is not attached when an app is closed from the server-side via AppController  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

Fix Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3644) App viewport curtain is not attached when an app is closed from the server-side via AppController

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3644 
 
 
 
  App viewport curtain is not attached when an app is closed from the server-side via AppController  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Basel  49  48 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3644) App viewport curtain is not attached when an app is closed from the server-side via AppController

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3644 
 
 
 
  App viewport curtain is not attached when an app is closed from the server-side via AppController  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Basel 49 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3644) App viewport curtain is not attached when an app is closed from the server-side via AppController

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3644 
 
 
 
  App viewport curtain is not attached when an app is closed from the server-side via AppController  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 App viewport  shim  curtain  is not attached when an app is closed from the server-side via AppController 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3431) Replace usages of cloner in favor of less fragile solution

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3431 
 
 
 
  Replace usages of cloner in favor of less fragile solution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3431) Replace usages of cloner in favor of less fragile solution

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3431 
 
 
 
  Replace usages of cloner in favor of less fragile solution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 Replace usages of cloner  by mutable wrapper objects  in favor of less fragile solution 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3431) Replace usages of cloner by mutable wrapper objects

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3431 
 
 
 
  Replace usages of cloner by mutable wrapper objects  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Sprint:
 
 Basel 48 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3431) Replace usages of cloner by mutable wrapper objects

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3431 
 
 
 
  Replace usages of cloner by mutable wrapper objects  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 Replace usages of cloner by  decorators  mutable wrapper objects 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3157) If the label is too long, the i18n and required sign (*) disappear

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3157 
 
 
 
  If the label is too long, the i18n and required sign (*) disappear  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.3.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] (MGNLUI-3157) If the label is too long, the i18n and required sign (*) disappear

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3157 
 
 
 
  If the label is too long, the i18n and required sign (*) disappear  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.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-3157) If the label is too long, the i18n and required sign (*) disappear

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3157 
 
 
 
  If the label is too long, the i18n and required sign (*) disappear  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 If the label is too long, the i18n and required sign (*)  disappears   disappear 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLRSSAGG-203) add https support

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-203 
 
 
 
  add https support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3157) If the label is too long, the i18n and required sign (*) disappears

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3157 
 
 
 
  If the label is too long, the i18n and required sign (*) disappears   
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-86) Video component dialog has no title

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-86 
 
 
 
  Video component dialog has no title  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3865) Refactor NameDefinition <-> DefinitionMetadata name binding mechanism

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3865 
 
 
 
  Refactor NameDefinition <-> DefinitionMetadata name binding mechanism  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Affects 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] (MGNLUI-3865) Refactor NameDefinition <-> DefinitionMetadata name binding mechanism

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3865 
 
 
 
  Refactor NameDefinition <-> DefinitionMetadata name binding mechanism  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.4.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3865) Refactor NameDefinition <-> DefinitionMetadata name binding mechanism

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3865 
 
 
 
  Refactor NameDefinition <-> DefinitionMetadata name binding mechanism  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 28/Apr/16 2:13 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Aleksandr Pchelintcev 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The algorithm in question ensures consistency of the name of the definitions to which it is important (see NamedDefinition interface).  
Currently this mechanism consists of two parts: 1) YamlConfigurationSource after producing the bean from YAML file checks whether name is set to the bean. If it is then the name is also pushed into the metadata. 2) AbstractRegistry upon DefinitionProvider registration grabs the bean from the provider and creates a wrapper provider (SwappedDefinitionProvider) which returns the same bean, but proxied (GetsNameFromMetadataWrapper) so that it always returns the definition name resolved from metadata (thanks to part 1 - metadata surely has the correct value). 
What is bad here? 
 

this is ridiculously complex. The solution is spread between two classes and is not obvious.
 

step 2) makes bold and generally wrong assumption about how provider works: the wrapper provider always returns all the same bean. But in general a DefinitionProvider does not guarantee that the 

[magnolia-dev] [JIRA] (PAGES-73) Add action to open the page in a browser tab

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-73 
 
 
 
  Add action to open the page in a browser tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Project:
 
 Magnolia  UI  pages module 
 
 
 

Key:
 
 MGNLUI PAGES - 2796 73 
 
 
 

Security:
 
 Public 
 
 
 

Component/s:
 
 page editor 
 
 
 

Affects Version/s:
 
 5.4.5 
 
 
 

Affects Version/s:
 
 5.2.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (PAGES-72) Indicate the number and type of selected elements in page editor

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-72 
 
 
 
  Indicate the number and type of selected elements in page editor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Project:
 
 Magnolia  UI  pages module 
 
 
 

Key:
 
 MGNLUI PAGES - 3691 72 
 
 
 

Security:
 
 Public 
 
 
 

Component/s:
 
 page editor 
 
 
 

Affects Version/s:
 
 5.4.3 
 
 
 

Affects Version/s:
 
 5.4.3 
 
 
 

Affects Version/s:
 
 5.3.12 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 

Fix Version/s:
 
 5.3.x 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3454) Make use of the ActionAvailability in inline editing feature

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3454 
 
 
 
  Make use of the ActionAvailability in inline editing feature  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 Improve user experience for Make use of the ActionAvailability in inline  editing  read-only config  feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2787) Get rid of MGWT from AdminCentral.

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2787 
 
 
 
  Get rid of MGWT from AdminCentral.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Summary:
 
 Re-consider usage Get rid  of MGWT  in  from  AdminCentral. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3825) Make sure decorators are respected in FieldTypeDefinitionRegistry#getByDefinition(..)

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3825 
 
 
 
  Make sure decorators are respected in FieldTypeDefinitionRegistry#getByDefinition(..)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3823) Adapt UI registries to the new dependency on ModuleRegistry

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3823 
 
 
 
  Adapt UI registries to the new dependency on ModuleRegistry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3822) Prepare UI definition registries to the introduction of the definition decorators feature

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3822 
 
 
 
  Prepare UI definition registries to the introduction of the definition decorators feature  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3824) Use I18NParentable interface duck-type check to determine whether a definition is i18n-ized

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3824 
 
 
 
  Use I18NParentable interface duck-type check to determine whether a definition is i18n-ized  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: