[magnolia-dev] [JIRA] (MGNLUI-4225) Too big drop in image quality when using image variation and cropping

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4225  
 
 
  Too big drop in image quality when using image variation and cropping   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Using image variation and especially cropping degrades image quality more than expected. When I upload an image using the image upload dialogue in the Content editor app (but also Pages or any other content app) and any kind of  tranformation  transformation  is applied to the image stored in the DAM by Magnolia the image quality is significantly less than when I would apply the same transformation using for instance Photoshop. Especially cropping has a very degrading effect. Setting a higher quality in modules/imaging/config/generators/mte/outputFormat doesn't solve the quality loss  percieved  perceived .* Absolute worst case: cropping image in Magnolia causes quality to drop very heavily* Still bad: directly uploading an image without cropping* Much, much better: resizing with photoshop (bypassing Magnolia completely)See  [^image_quality_test.zip]  and check the quality difference.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
   

[magnolia-dev] [JIRA] (JSMODELS-8) JavascriptObjectFactory should expose HTMLEscapingAggregationState to templates

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-8  
 
 
  _javascript_ObjectFactory should expose HTMLEscapingAggregationState to templates   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Sprint: 
 Basel 101  
 

  
 
 
 
 

 
 
 

 
 
 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-38) Add more Log Tools UI tests

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-38  
 
 
  Add more Log Tools UI tests   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5 8  
 

  
 
 
 
 

 
 
 

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

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 In the pulse, there is a missing translation key in the "Messages" tab. Its in the popup when you click the "With checked do:" button:"publish.actions.delete" Happend Happened  on CE bundle 5.4.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-3816) Missing translation in Pulse "publish.actions.delete"

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Labels: 
 quickwin  
 

  
 
 
 
 

 
 
 

 
 
 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-4218) Register shortcuts in UI should be simplified

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4218  
 
 
  Register shortcuts in UI should be simplified   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Right now there is a ??MagnoliaShellViewImpl?? where we register some shortcuts for  admincetral  admincentral , but its not possible to add custom shortcuts in custom apps.We should create one place to easily add shortcut handling function to keyboardShortcutHandler.    
 

  
 
 
 
 

 
 
 

 
 
 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-4193) Conflict between jcrName and setNodeName()

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4193  
 
 
  Conflict between jcrName and setNodeName()   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 When setting names of the newly created nodes programatically there is a conflict if {{jcrName}} is also configured (e.g. you want to show your editors real name of the node, but in read only mode so that they can't change it and it is set according to predefined rules).To reproduce (in contacts app):#1 observe that upon creation of new contact, node is saved with name consisting of first letter of first name and full last name#2 in editor form add extra text field with {{name=jcrName}}#3 try to create new contact leaving newly created {{jcrName}} field empty#4 observe failure to save the dialog (btw {{save}} button stays blocked even after correcting the error. not very nice)#5 try to create new contact filling newly created {{jcrName}} field with some value (different than normally autogenerated value for contact node name)#6 observe that upon saving of the contact, value set in {{jcrName}} field is discarded and replaced with autogenerated value.Expected behavior:Either autogeneration always wins and thus it should not be required to fill such field with a valueorexistence of field (in rw mode) takes precedence over generated value and thus should not be overwritten.In RO mode on the  otherhand  other hand  (i.e. when field has set {{readOnly==true}}) it's value should be only displayed and not considered when saving the dialog at all (i.e. autogenerated node name mechanism wins).Also when saving fails, it fails with very counterproductive error:{code}info.magnolia.ui.api.action.ActionExecutionException: javax.jcr.PathNotFoundException: firstName at info.magnolia.ui.form.action.SaveFormAction.execute(SaveFormAction.java:92) at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:62){code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[magnolia-dev] [JIRA] (MGNLUI-4189) Applauncher item section open-close indication quirk

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4189  
 
 
  Applauncher item section open-close indication quirk
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Attachment: 
 windowsapplauncher.JPG  
 
 
Attachment: 
 windowsapplauncher2.JPG  
 

  
 
 
 
 

 
 
 

 
 
 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-4189) Applauncher item section open-close indication quirk

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4189  
 
 
  Applauncher item section open-close indication quirk
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.3  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 applauncher  
 
 
Created: 
 11/Apr/17 5:03 PM  
 
 
Labels: 
 to-estimate  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 It is reproducible in 5.5.3 and 5.4.12 version on Windows with both Chrome and Firefox. Basically, item section open close indication contains only triangle however it somehow shows quirky behaviour when it comes to Windows (see attached screenshots)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
   

[magnolia-dev] [JIRA] (MGNLUI-4185) Pressing magnifier glass after image upload throws error

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4185  
 
 
  Pressing magnifier glass after image upload throws error   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 Pressing magnifier  glas  glass  after image upload throws error  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-123) Change the default folder for JS / CSS to just webresources

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-123  
 
 
  Change the default folder for JS / CSS to just webresources   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Right now CSS and JS files go to  seperate  separate  folders:{code}"css": "/webresources/css","js": "/webresources/js",{code}The latest examples just use a bundle.css / bundle.js in the webresources folder.{code}webresources/bundle.csswebresources/bundle.js{code}Proposal: Change the default folder for JS / CSS to just webresources.  
 

  
 
 
 
 

 
 
 

 
 
 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-4176) Create a new Vaadin extension to display inline message bubble below a component

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4176  
 
 
  Create a new Vaadin extension to display inline message bubble below a component   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 From UI design to [indicate the license status in the About app|https://wiki.magnolia-cms.com/display/UX/Reporting+status+of+and+problems+with+the+product+license#Reportingstatusofandproblemswiththeproductlicense-ShowthelicensestatusintheAboutapp]- Create a new extension to display inline message bubble named {{MessageBubble}}- Able to manipulate title, message- Support to display in 3 different styles:  helping, warning, error.Think about ability to use in general purpose: Eg: display help message, and error  mesasge  message
 

  
 
 
 
 

 
 
 

 
 
 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) Show confirmation dialog when user tries to close an app

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Show confirmation dialog when user tries to close an app   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 Show confirmation dialog when user tries to close an  ap  app  
 

  
 
 
 
 

 
 
 

 
 
 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) Show confirmation dialog to user when user tries to close an app

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Show confirmation dialog to user when user tries to close an app   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 23/Mar/17 1:40 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Currently, We can show confirmation dialogs to users within an subapp for instance attaching it to a button or similar works. However, we do not have the functionality to show to the user when one wants to close an app. Although info.magnolia.ui.api.app.App interface provides stop() method, we can't simply override it and do the trick there like subapp. The reason being that there are some listeners attached to info.magnolia.ui.api.shell.Shell and they are not interceptable in that sense.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

   

[magnolia-dev] [JIRA] (MGNLUI-4173) Show confirmation dialog when user tries to close an app

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Show confirmation dialog when user tries to close an app   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Currently, We can show confirmation dialogs to users within an subapp for instance attaching it to a button or similar works. However, we do not have the functionality to show to the user when one wants to close an app. Although  {{  info.magnolia.ui.api.app.App }}  interface provides stop() method, we can't simply override it and do the trick there like subapp. The reason being that there are some listeners attached to  info.magnolia.ui.api.shell.Shell and they are not interceptable in that sense.  
 

  
 
 
 
 

 
 
 

 
 
 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) Show confirmation dialog when user tries to close an app

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Show confirmation dialog when user tries to close an app   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Currently, We can show confirmation dialogs to users within an subapp for instance attaching it to a button or similar works. However, we do not have the functionality to show to the user when one wants to close an app. Although {{info.magnolia.ui.api.app.App}} interface provides  #  stop() method, we can't simply override it and do the trick there like subapp. The reason being that there are some listeners attached to  {{   info.magnolia.ui.api.shell.Shell }}  and they are not interceptable in that sense.  
 

  
 
 
 
 

 
 
 

 
 
 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) Show confirmation dialog when user tries to close an ap

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4173  
 
 
  Show confirmation dialog when user tries to close an ap   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 Show confirmation dialog  to user  when user tries to close an  app  ap  
 

  
 
 
 
 

 
 
 

 
 
 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-4165) When using validators in fields outside of a dialog/tab FieldValidatorDefinitionKeyGenerator throws NPE

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4165  
 
 
  When using validators in fields outside of a dialog/tab FieldValidatorDefinitionKeyGenerator throws NPE   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Affects Version/s: 
 5.5.2  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-114) testsuite fails with error

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-114  
 
 
  testsuite fails with error   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 The testsuite fails on some machines ( ilgüns ilgün's ) for the tabcompletion test  
 

  
 
 
 
 

 
 
 

 
 
 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-4165) When using validators in fields outside of a dialog/tab FieldValidatorDefinitionKeyGenerator throws NPE

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4165  
 
 
  When using validators in fields outside of a dialog/tab FieldValidatorDefinitionKeyGenerator throws NPE   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
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-4165) When using validators in fields outside of a dialog/tab FieldValidatorDefinitionKeyGenerator throws NPE

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4165  
 
 
  When using validators in fields outside of a dialog/tab FieldValidatorDefinitionKeyGenerator throws NPE   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Assignee: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-111) mgnl build throws if no argument given

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-111  
 
 
  mgnl build throws if no argument given   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 mgnl build throws if no  agument  argument  given  
 

  
 
 
 
 

 
 
 

 
 
 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-4162) Restyle combobox and its positioning

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4162  
 
 
  Restyle combobox and its positioning   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 We've discussed this in UX. Our main aim now is to avoid that a second combobox (or any other UI element) on the right jumps horizontally if the value in the combobox changes. This has been the main feedback so far, and it's perfectly valid, and it makes sense from a visual design standpoint as well. We also still want to keep the arrow next to the value so that it remains clear that that value can be changed. One common solution in visual design - and the one we've settled with - is to *give such elements a fixed, configurable width and visually anchor the element with faint separators* on the left and the right - see part "A" in the explanations attached below. You'll also find a similar solution in the original design for selectors in the edit bar (see e.g. [^3-1 Visual design of selectors.png]). Part "B" lists the details on paddings, fonts and colors used. !Combobox in dialog footer.png! The *main design intent* is:# Every switcher in the dialog footer has a fixed width (minimum: 125px), which can be configured to be wider. We expect 125px for the language and 180px for the variant switcher to be good defaults.# The width of the actual combobox (minimum: 120px) is  independant  independent  of the width of the switcher. It should open above the value label - we've understood this is currently hard to achieve.# Switchers are bordered by a *22px high and 1px wide separators* on the left and the right*.# The *distance* between the left separator and the value, between the value and the arrow is fixed (10 px or 15 px resp.). The distance between the arrow and the right separator is _at least_ 10px.# *Values are truncated using an ellipsis* ("...") in case they don't fit within the chosen width of the combobox.Please *let us know if you plan to adapt other instances* of the combobox. We might want to slightly translate or adjust this design.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[magnolia-dev] [JIRA] (MGNLUI-3775) Design a dedicated component to handle temporary files lifecycle

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3775  
 
 
  Design a dedicated component to handle temporary files lifecycle   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Attempts to solve issues related to clean-up of temporary files produced by form fields (MGNLDAM-636 and MGNLUI-3776) via a direct subscription to app/sub-app lifecycle events turned out to be rigid and error-prone: the same field type might be used in the scope of both sub-app and app (or even outside of both of them - e.g. in Pulse which exists in AdminCentral scope) => all those cases would have to be handled separately.One possible solution to this problem is to abstract from the actual specific type of the UIContext: - design a map-like temporary file storage- create temporary files through such storage (i.e. create a mere tmp file, but map it internally to the current {{UiContext}})- provide capabilities to clean-up the storage per UiContext, so that all the apps/sub-apps could do remove tmp files related to them in an automatic way (in their {{#close()}} method or  smth  something ).- I would maybe use the {{WeakHashMap}} internally for such a component, so that the storage wouldn't prevent "dead" {{UiContext}} instances from being GC'ed in case clean-up didn't happen (e.g. that specific {{UiContext}} just doesn't do that, failed to do that or whatnot and => it's the cron job's work in such case)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (NPMCLI-99) Search for magnolia light-module packages on npm

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-99  
 
 
  Search for magnolia light-module packages on npm   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5 8  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-165) CacheEndpoint is potentially vulnerable to RCE

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  CacheEndpoint is potentially vulnerable to RCE   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 8  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLREST-73) When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-73  
 
 
  When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLREST-73) When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-73  
 
 
  When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Assignee: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLREST-73) When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-73  
 
 
  When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered.   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Sprint: 
 Basel  86  85  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-27) Create german language property files for the MTE components

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-27  
 
 
  Create german language property files for the MTE components   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-91) Move CLI "texts" into a common resource bundle file (i18n)

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-91  
 
 
  Move CLI "texts" into a common resource bundle file (i18n)   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLMAIL-66) Using Gmail as a mail client requires enabling a less secure option on your account

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Mail Module /  MGNLMAIL-66  
 
 
  Using Gmail as a mail client requires enabling a less secure option on your account   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 8  
 
 
Labels: 
 support  to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-3242) Warn on deletion of page with modified children

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3242  
 
 
  Warn on deletion of page with modified children   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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-322) Location fragment should be escaped

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-322  
 
 
  Location fragment should be escaped   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 framework tech-debt  to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLWORKFLOW-349) Deletion workflow message should not be identical to publishing changes

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-349  
 
 
  Deletion workflow message should not be identical to publishing changes   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 5  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-210) Change component variants parent node type to mgnl:componentVariants

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-210  
 
 
  Change component variants parent node type to mgnl:componentVariants   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-210) Change component variants parent node type to mgnl:componentVariants

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-210  
 
 
  Change component variants parent node type to mgnl:componentVariants   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-91) Move CLI "texts" into a common resource bundle file (i18n)

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-91  
 
 
  Move CLI "texts" into a common resource bundle file (i18n)   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 h4. IssueAt the moment, all texts addressed to CLI users are widespread among command-js-files.I propose to move these texts into one resource bundle file (most probably a json file).h4. Motivationh5. docs maintenancetbh - my first motivation was rather selfish and documentation centric. With such a  commmon  common  resource bundle file - i could read it and use with a Confluence macro. This would in the long run reduce the amount of work of maintenance of the (CLI) documentation.h5. 18nI do not expect that we will create translations for other languages in the near future - however - it doesn't hurt to make it 18n ready now - but it may hurt in future.h5. Ease of linguistic reviewDuring the NOW development we have seen that it is impossible for a linguist to make a UI text review, if the texts are hardcoded and widespread among code files. But to have the texts in one single (json) file makes it very easy for a non developer to review the text and to polish them. (Guys as Martin or Julie could do such a text review.)h4. etc.I already had a quick SKYPE call with [~robertkowalski] whether this is feasible and common practice in the CLI / NPM world too - which he confirmed.Robert also has mentioned, that at the moment many files are touched anyway. So - i18n-ization could be done additionally while fixing / improving other things. (Just make sure to have separate commits.)h4. KeysIf the ticket will be tackled - we would have to find a suitable naming convention for good keys.I could propose here some ideas - if desired - since i already was thinking about a bit.However - other guys have a lot of experience in this topic too.Basically i would expect something like$commandName.$topic, e.g. {{create-page.sucess-next-step-tip}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

[magnolia-dev] [JIRA] (MGNLCACHE-165) Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 As described in MAGNOLIA-6900, our cache endpoint is potentially vulnerable to RCE due to JSON serialisation and deserialisation. Although  the possibility of  this is  pretty less  not very probable , we had to come up with a proper solution to the problem at hand. This issue proposes to implement a custom {{java.lang.ClassLoader}} and pass it to {{com.cedarsoftware.util.io.JsonReader}} at the time of serialisation. Therefore we have the power to prevent an attack when an unwanted class is tried to be serialised by the endpoint. We simply make it configurable in JCR and user only has to populate the whitelisted classes to be serialised by the endpoint via {{info.magnolia.cache.browser.CacheBrowserAppModule}} and the custom ClassLoader is responsible to handle the rest(to check whether it should be ignored or serialised.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

[magnolia-dev] [JIRA] (MGNLCACHE-165) Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 As described inMAGNOLIA-6900, our cache endpoint is potentially vulnerable to RCE due to JSON serialisation and deserialisation. Although the possibility of this is pretty less, we had to come up with a proper solution to the problem at hand. This issue proposes to implement a custom {{java.lang.ClassLoader}} and pass it to {{com.cedarsoftware.util.io.JsonReader}} at the time of serialisation. Therefore we have the power to prevent an attack when an unwanted class is tried to be serialised by the endpoint. We simply make it configurable in JCR and user only has to populate the whitelisted classes to be serialised by the endpoint via {{info.magnolia.cache.browser.CacheBrowserAppModule}} and the custom ClassLoader is responsible to handle the rest(to check whether it should be ignored or serialised.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

   

[magnolia-dev] [JIRA] (MGNLCACHE-165) Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 As described in   
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-165) Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Sprint: 
 Basel 85  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-165) Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-165  
 
 
  Prevent potential cache REST endpoint vulnerabilities by adding custom ClassLoader   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.2  
 
 
Assignee: 
 Ilgun Ilgun  
 
 
Created: 
 27/Feb/17 2:34 PM  
 
 
Fix Versions: 
 5.5.3  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
   

[magnolia-dev] [JIRA] (NPMCLI-99) Search for magnolia light-module packages on npm

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-99  
 
 
  Search for magnolia light-module packages on npm   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Assignee: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Fix Version/s: 
 1.1.2  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Assignee: 
 Maxime Michel Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-4135) Enable reference-fields-by-name

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4135  
 
 
  Enable reference-fields-by-name
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Feature that was brought in by MGNLUI-3882 and disabled by MGNLUI-4134 for 5.5.2 need to be (re)activated for the 5.5.3 release, related to the state of DEV-441. For heads up:QA commit is already in since it fixes tests from the main ticket, only the referenced UI tickets have to be re-introduced.  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-102) Adjust SearchTemplatingFunctions to query whole workspace

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-102  
 
 
  Adjust SearchTemplatingFunctions to query whole workspace   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 Add SearchFunction Adjust SearchTemplatingFunctions  to query whole workspace  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-102) Adjust SearchTemplatingFunctions to query whole workspace

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-102  
 
 
  Adjust SearchTemplatingFunctions to query whole workspace   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 SearchTemplatingFunctions Currently, one cannot query the whole workspace by any means since we cannot pass '/' to #searchContent (String workspace, String returnItemType)  methods due to null checks.  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-102) Add SearchFunction to query whole workspace

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-102  
 
 
  Add SearchFunction to query whole workspace   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ilgun Ilgun  
 
 
Created: 
 02/Feb/17 4:04 PM  
 
 
Fix Versions: 
 1.1.2  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 SearchTemplatingFunctions#searchContent(String workspace, String returnItemType)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3777) Streamline DIN font fallbacks when webfont can't be loaded

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3777  
 
 
  Streamline DIN font fallbacks when webfont can't be loaded   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 (1) The Magnolia AdminCentral UI uses a custom web-font.(2) Following the OWASP recommendations, the caching headers are set as follow in the Apache:(https://www.owasp.org/index.php/OWASP_Application_Security_FAQ#Browser_Cache)Header merge Cache-Control no-cache env=NO_CACHEHeader merge Cache-Control no-store env=NO_STOREHeader set Pragma "no-cache"Header set Expires "Wed, 10 Jan 1970 00:00:00 GMT"(3)  Unfortunatly  Unfortunately  the IE has an issue with webfonts under these conditions:(https://connect.microsoft.com/IE/feedbackdetail/view/992569/font-face-not-working-with-internet-explorer-and-http-header-pragma-no-cache)(4) Steps-ToReproduce:- use a setup as above- use InternetExplorer- load AdminCentral page / press F5 or CTRL-F5---Request:The AdminCentral UI should have a working font fallback that allows continuing to work even when the WebFont can not be loaded. (font & icons)Looks like there is no fallback set - therefor the IE 11 decides to fallback to TimesNewRoman font and the "icons" can not be loaded.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

[magnolia-dev] [JIRA] (MGNLUI-4081) readOnly checkbox doesn't appear in JCR data

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4081  
 
 
  readOnly checkbox doesn't appear in JCR data   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Thanks to [~sfroger] in SUPPORT-6874, currently when user set field's config 'readOnly' to 'true', our 'defaultValue' is no longer used when populating its value. This issue  lead  leads  to no value saved into their JCR persistent.Expected result: Separate logic of 'defaultValue' and 'readOnly' in fields which means: 1. When a field is readOnly, make it read only from editors. 2. When user set its 'defaultValue', put that value to field's value.Grep code: {code}info.magnolia.ui.form.field.factory.AbstractFieldFactory.setPropertyDataSourceDefaultValue(Property) {...if (defaultValue != null && !definition.isReadOnly()) {property.setValue(defaultValue);}}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (MGNLUI-3882) Reference fields by name as well as by fully qualified classname

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3882  
 
 
  Reference fields by name as well as by fully qualified classname   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Documentation update 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] (MGNLDEMO-203) About Page's template is not available therefore cannot be added once deleted

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-203  
 
 
  About Page's template is not available therefore cannot be added once deleted   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 Once the template of the about page is changed, the respective template ({{travel-demo:pages/aboutDemo}}) cannot be re-selected.This is somewhat serious, as the red label (see  attachement  attachment ) on the demo frontend is only displayed when a page of the about-page-type is found.  
 

  
 
 
 
 

 
 
 

 
 
 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-3882) Reference fields by name as well as by fully qualified classname

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3882  
 
 
  Reference fields by name as well as by fully qualified classname   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Fix Version/s: 
 5.5.2  
 
 
Fix Version/s: 
 5.5.1  
 

  
 
 
 
 

 
 
 

 
 
 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-70) Integration tests fixture module is severely broken and needs some polishing

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-70  
 
 
  Integration tests fixture module is severely broken and needs some polishing   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 Integration tests fixture module is  severly  severely  broken and needs some polishing  
 

  
 
 
 
 

 
 
 

 
 
 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-67) Add an UI test checking that there are no Definitions app problems

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-67  
 
 
  Add an UI test checking that there are no Definitions app problems   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Fix Version/s: 
 5.5.1  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCI-16) Error on Import: error message doesn't give a reason and stacktrace looks odd

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Content Importer Module /  MGNLCI-16  
 
 
  Error on Import: error message doesn't give a reason and stacktrace looks odd   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Assignee: 
 Ilgun Ilgun  
 

  
 
 
 
 

 
 
 

 
 
 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-68) Tests fixture module create /templates/components folder with wrong nodeType causing node2bean problems with template definitions

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-68  
 
 
  Tests fixture module create /templates/components folder with wrong nodeType causing node2bean problems with template definitions   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Summary: 
 Tests  fixure  fixture  module create /templates/components folder with wrong nodeType causing node2bean problems with template definitions  
 

  
 
 
 
 

 
 
 

 
 
 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-3882) Reference fields by name as well as by fully qualified classname

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ilgun Ilgun updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3882  
 
 
  Reference fields by name as well as by fully qualified classname   
 

  
 
 
 
 

 
Change By: 
 Ilgun Ilgun  
 
 
Fix Version/s: 
 5.5.1  
 

  
 
 
 
 

 
 
 

 
 
 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-3882) Reference fields by name as well as by fully qualified classname

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3882 
 
 
 
  Reference fields by name as well as by fully qualified classname  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Labels:
 
 blocked 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3882) Reference fields by name as well as by fully qualified classname

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3882 
 
 
 
  Reference fields by name as well as by fully qualified classname  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Sprint:
 
 Basel 73 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3882) Reference fields by name as well as by fully qualified classname

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3882 
 
 
 
  Reference fields by name as well as by fully qualified classname  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3922) Page delete confirmation message in dialog is not correct processed

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3922 
 
 
 
  Page delete confirmation message in dialog is not correct processed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 The message in page delete confirmation dialog is not processed. The bug  occures  occurs  at least for French and Italian users. German and English is fine. It is  reproducable  reproducible  on Demoauthor instance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCI-15) Dropping Folders under observed directory does not detect changes

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-15 
 
 
 
  Dropping Folders under observed directory does not detect changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 1.0.1 
 
 
 

Fix Version/s:
 
 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCI-15) Dropping Folders under observed directory does not detect changes

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-15 
 
 
 
  Dropping Folders under observed directory does not detect changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLPUR-172) Components and dialogs relying on legacy 18n mechanism might not be translated properly because properties file might not be found (in time)

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Public User Registration /  MGNLPUR-172 
 
 
 
  Components and dialogs relying on legacy 18n mechanism might not be translated properly because properties file might not be found (in time)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 The legacy {{messages_en.properties}} file was moved with MGNLPUR-164 making the translation unavailable for the legacy  mechansim  mechanism . We should move the file back to its original location until we have gotten rid of usages of the legacy i18n mechanism. This way we'll also be in-sync with the translations modules (which might be resolved correctly replacing the default translation with some fallback – via {{Locale.getDefault()}}).The new mechanism is capable of falling back to the legacy one, but not vice versa. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGROOVY-153) ScriptDonePollListener stays around after script is done

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-153 
 
 
 
  ScriptDonePollListener stays around after script is done  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 Maybe sort of corner case, still I'd like to report it and fix it (should be easy)To reproduce it:- execute a "long-running" groovy script (anything which takes more than 200ms :) )-- the script will send a notification and a message to pulse when done- now try to upload a big file in Assets- cancel the upload before it's done- the groovy script done  notif  notify  and message appear out of the blueThe reason should lie in the fact that we remove instances of {{ScriptDonePollListener}} from the current {{UI}} each time we run {{MgnlGroovyConsole#runAsync}} and not when the script is done at {{MgnlGroovyConsole.ScriptDonePollListener#poll}}.Vaadin's {{PollListener}} s apparently react to any polling event, no matter which component registered it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3914) HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3914 
 
 
 
  HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

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] (MGNLUI-3914) HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3914 
 
 
 
  HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.5.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLDEMO-191) Rename sportstation folder to travel-demo-multisite

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-191 
 
 
 
  Rename sportstation folder to travel-demo-multisite  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLDEMO-191) Rename sportstation folder to travel-demo-multisite

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-191 
 
 
 
  Rename sportstation folder to travel-demo-multisite  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3914) HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3914 
 
 
 
  HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3914) HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3914 
 
 
 
  HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.workbench.tree.HierarchicalJcrContainer#getParent(Object)}} tries to determine the parent of a passed root node, resulting in an unnecessary log statement (due to exception).{code}[INFO] [talledLocalContainer] 2016-06-14 19:44:40,301 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent{code}h4.  Howto  How to  reproduce# Goto security app# Edit role's "web access"# SaveSee four statements like:{code}[INFO] [talledLocalContainer] 2016-09-27 13:03:55,248 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent[INFO] [talledLocalContainer] 2016-09-27 13:03:55,255 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent[INFO] [talledLocalContainer] 2016-09-27 13:03:55,262 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@51e8122: javax.jcr.ItemNotFoundException: Root node doesn't have a parent[INFO] [talledLocalContainer] 2016-09-27 13:03:55,290 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3914) HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3914 
 
 
 
  HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.workbench.tree.HierarchicalJcrContainer#getParent(Object)}} tries to determine the parent of a passed root node, resulting in an  unnessecary  unnecessary  log statement (due to exception).{code}[INFO] [talledLocalContainer] 2016-06-14 19:44:40,301 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent{code}h4. Howto reproduce# Goto security app# Edit role's "web access"# SaveSee four statements like:{code}[INFO] [talledLocalContainer] 2016-09-27 13:03:55,248 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent[INFO] [talledLocalContainer] 2016-09-27 13:03:55,255 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent[INFO] [talledLocalContainer] 2016-09-27 13:03:55,262 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@51e8122: javax.jcr.ItemNotFoundException: Root node doesn't have a parent[INFO] [talledLocalContainer] 2016-09-27 13:03:55,290 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNodeItemId@2b88f047: javax.jcr.ItemNotFoundException: Root node doesn't have a parent{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCI-15) Dropping Folders under observed directory does not detect changes

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-15 
 
 
 
  Dropping Folders under observed directory does not detect changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 Content importer relies on {{info.magnolia.dirwatch.DirectoryWatcher}} detecting changes and it basically delegates those changes to user via Pulse. However, in case of copy pasting a folder to observed directory of Content-importer behaves wrong. The problem is being the folder identified but not the files beneath. However, when those files are changes then system is able to pickup those changes. This issue most likely to be moved to Magnolia project will touch some code there however, since the cause is observable in Content-importer, it initially got created here. On the other hand, one has to start observing the content-importer module and its communication to {{info.magnolia.dirwatch.DirectoryWatcher}} for starting point  as there might be small issue somewhere between the communication . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCI-15) Dropping Folders under observed directory does not detect changes

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-15 
 
 
 
  Dropping Folders under observed directory does not detect changes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.0 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 

Created:
 

 15/Nov/16 9:38 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
Content importer relies on info.magnolia.dirwatch.DirectoryWatcher detecting changes and it basically delegates those changes to user via Pulse. However, in case of copy pasting a folder to observed directory of Content-importer behaves wrong. The problem is being the folder identified but not the files beneath. However, when those files are changes then system is able to pickup those changes.  
This issue most likely to be moved to Magnolia project will touch some code there however, since the cause is observable in Content-importer, it initially got created here. On the other hand, one has to start observing the content-importer module and its communication to info.magnolia.dirwatch.DirectoryWatcher for starting point. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

[magnolia-dev] [JIRA] (MGNLADMLEG-60) Phase out Admin-interface Legacy

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Admininterface Legacy Module (4.x compatibility) /  MGNLADMLEG-60 
 
 
 
  Phase out Admin-interface Legacy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLADMLEG-60) Phase out Admin-interface Legacy

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Admininterface Legacy Module (4.x compatibility) /  MGNLADMLEG-60 
 
 
 
  Phase out Admin-interface Legacy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLTPLSMPL-26) Remove usages of BasicTextCodeFieldDefinition

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Samples /  MGNLTPLSMPL-26 
 
 
 
  Remove usages of BasicTextCodeFieldDefinition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 Remove  uses  usages  of BasicTextCodeFieldDefinition 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGROOVY-155) Remove usages of BasicTextCodeFieldDefinition

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-155 
 
 
 
  Remove usages of BasicTextCodeFieldDefinition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 Remove  uses  usages  of BasicTextCodeFieldDefinition 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4062) Migration from 5.3 to 5.5 causes migration diffs – Save/CancelDialogActionDefinition

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4062 
 
 
 
  Migration from 5.3 to 5.5 causes migration diffs – Save/CancelDialogActionDefinition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Story Points:
 
 5 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4063) Fix Migration diffs caused by AdminInterface-Legacy is not being installed

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4063 
 
 
 
  Fix Migration diffs caused by AdminInterface-Legacy is not being installed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Story Points:
 
 2 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4063) Fix Migration diffs caused by AdminInterface-Legacy is not being installed

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4063 
 
 
 
  Fix Migration diffs caused by AdminInterface-Legacy is not being installed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 Fix Migration diffs caused by AdminInterface -Legacy  is not being installed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4063) Fix Migration diffs caused by AdminInterface is not being installed

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4063 
 
 
 
  Fix Migration diffs caused by AdminInterface is not being installed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 

Created:
 

 02/Nov/16 1:09 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Ilgun Ilgun 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
While investigating the failures of 5.3 to 5.5, It turns out that there was an error made while removing adminInterface-legacy. Currently a fresh install and migrated instance of 5.3 would have diffs due to 5.3 bundle is having STK installed therefore admininterface-legacy is installed. Some of the migration tasks in info.magnolia.ui.admincentral.setup.for5_5.RemoveAdmininterfaceLegacyTask shouldn't be depending upon if admininterface-legacy is installed or not. This ticket aims to clear those migration diffs and move those tasks to proper places so that in any case these nodes which cause the diff would be removed. 
 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-4063) Fix Migration diffs caused by AdminInterface is not being installed

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4063 
 
 
 
  Fix Migration diffs caused by AdminInterface is not being installed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-4062) Migration from 5.3 to 5.5 causes migration diffs – Save/CancelDialogActionDefinition

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4062 
 
 
 
  Migration from 5.3 to 5.5 causes migration diffs – Save/CancelDialogActionDefinition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLREST-62) Add possibility to put context attributes to the rest response in command endpoint

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-62 
 
 
 
  Add possibility to put context attributes to the rest response in command endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 [~ilgun] -> As far as I could grasp when I was working on MGNLBACKUP-105, the behaviour is as follows;* Command itself it returning false -> { {{  Success : true  }} }  * Command returning true -> no effect I'd expect to have success : false but no it will still return  success { {{Success : true  }} }  * Command throwing exceptions -> Finally we get a  success  { {{Success  : false }} }  with exception message in the response entity.Therefore the success message relies on the command throwing exceptions or not.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCI-8) Pulse task list should display name of file to import

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-8 
 
 
 
  Pulse task list should display name of file to import   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Sprint:
 
 Basel  68  67 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-60 
 
 
 
  Remove "too many open files" startup check - if possible thanks to H2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCE-61) Remove "too many open files" startup check - if possible thanks to H2

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-61 
 
 
 
  Remove "too many open files" startup check - if possible thanks to H2  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 

Created:
 

 17/Oct/16 2:43 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christopher Zimmermann 
 
 
 
 
 
 
 
 
 
 
One benefit of switching to H2 is that it opens less file handles than Derby. 
After switching to H2, test if the problems due to too many open files are reduced ENOUGH, so that we can remove the check and restriction on Magnolia startup. 
Reason: It is a hurdle for evaluators and new developers to have to change the system settings for handling open files, so it would be an improvement if we could remove this check. See "too many open files" at https://documentation.magnolia-cms.com/display/DOCS/_Known+issues 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-60 
 
 
 
  Remove "too many open files" startup check - if possible thanks to H2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Assignee:
 
 Ilgun Ilgun 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-60 
 
 
 
  Remove "too many open files" startup check - if possible thanks to H2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLSITE-72) Add required configurationSourceType while adding theme by SiteModule

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-72 
 
 
 
  Add required configurationSourceType while adding theme by SiteModule  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 Group Add required configurationSourceType while adding theme  by  definition source does not work  SiteModule 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-72) Group by definition source does not work

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-72 
 
 
 
  Group by definition source does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLSITE-72) Group by definition source does not work

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-72 
 
 
 
  Group by definition source does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Project:
 
 Magnolia  Site Module 
 
 
 

Key:
 
 MAGNOLIA MGNLSITE - 6811 72 
 
 
 

Security:
 
 Public 
 
 
 

Affects Version/s:
 
 1.1 
 
 
 

Affects Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLSITE-72) Group by definition source does not work

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-72 
 
 
 
  Group by definition source does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Affects Version/s:
 
 1.0.9 
 
 
 

Affects Version/s:
 
 1.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLTPLSMPL-25) Remove references to adminInterface-legacy

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Samples /  MGNLTPLSMPL-25 
 
 
 
  Remove references to adminInterface-legacy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Status:
 
 pre-integration QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLCE-48) Switch default bundle db to H2

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-48 
 
 
 
  Switch default bundle db to H2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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