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

2017-06-19 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Original Estimate: 
 0.25d  
 
 
Remaining Estimate: 
 0.25d  
 

  
 
 
 
 

 
 
 

 
 
 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-4225) Too big drop in image quality when using image variation and cropping

2017-06-19 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Component/s: 
 image provider  
 

  
 
 
 
 

 
 
 

 
 
 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-4225) Too big drop in image quality when using image variation and cropping

2017-06-19 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Issue Type: 
 Bug Task  
 

  
 
 
 
 

 
 
 

 
 
 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-4225) Too big drop in image quality when using image variation and cropping

2017-06-19 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Labels: 
 support  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-151) Change 'repository' property name of DefaultSubscription to 'workspace'

2017-05-14 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-151  
 
 
  Change 'repository' property name of DefaultSubscription to 'workspace'   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 subscription-config-guide.png  
 
 
Created: 
 15/May/17 5:53 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Currently subscription configuration point using the name 'repository' in place of 'workspace' config (reference to attached image for detail) that is confusing and error prone to customer. Please change it accordingly.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLACTIVATION-151) Change 'repository' property name of DefaultSubscription to 'workspace'

2017-05-14 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-151  
 
 
  Change 'repository' property name of DefaultSubscription to 'workspace'   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Attachment: 
 subscription-config-guide.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLACTIVATION-151) Change 'repository' property name of DefaultSubscription to 'workspace'

2017-05-14 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-151  
 
 
  Change 'repository' property name of DefaultSubscription to 'workspace'   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Currently subscription configuration point using the name 'repository' in place of 'workspace' config (reference to attached image for detail) that is confusing and error prone to customer. Please change it accordingly.   !subscription-config-guide.png|thumbnail!
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLGS-132) Problem when generating sitemap from browser

2017-05-09 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Google Sitemap Module /  MGNLGS-132  
 
 
  Problem when generating sitemap from browser   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2017-04-26 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-852  
 
 
  Cannot create a workspace with a name starting with a digit using Derby   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Currently we cannot make 'srcset' image attribute effective even using 'source view editor' in our CKEditor.By supporting extra plugin 'imageresponsive' we hope this could work.Steps:open Tour app and open any tour for editing, edit its body using below source, switch back and forth in 'source' view and 'srcset' attribute will disappear. Note that the data still saved into JCR and after saving we still able to use it in our front-end page.Sample code:{ source code }  srcset="http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 1x, http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 2x" />  { source code }  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Currently we cannot make 'srcset' image attribute effective even using 'source view editor' in our CKEditor.By supporting extra plugin 'imageresponsive' we hope this could work.Steps:open Tour app and open any tour for editing, edit its body using below source, switch back and forth in 'source' view and 'srcset' attribute will disappear. Note that the data still saved into JCR and after saving we still able to use it in our front-end page.Sample code:{source}  srcset="http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 1x, http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 2x" />  {source}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list 

[magnolia-dev] [JIRA] (MGNLUI-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Fix Version/s: 
 5.4.12  
 
 
Fix Version/s: 
 5.5.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Affects Version/s: 
 5.5.2  
 
 
Affects Version/s: 
 5.4.11  
 

  
 
 
 
 

 
 
 

 
 
 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-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Currently we cannot make 'srcset' image attribute effective even using 'source view editor' in our CKEditor.By supporting extra plugin 'imageresponsive' we hope this could work.Steps:open Tour app and open any tour for editing, edit its body using below source, switch back and forth in 'source' view and 'srcset' attribute will disappear. Note that the data still saved into JCR and after saving we still able to use it in our front-end page.Sample code:{source}  srcset="http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 1x, http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 2x" />  {source}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




For list 

[magnolia-dev] [JIRA] (MGNLUI-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-4178) Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective

2017-03-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4178  
 
 
  Support ckeditor extra plugin imageresponsive and make 'srcset' image attribute effective   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 vaadin integration  
 
 
Created: 
 28/Mar/17 10:19 AM  
 
 
Fix Versions: 
 5.4.12, 5.5.3  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Currently we cannot make 'srcset' image attribute effective even using 'source view editor' in our CKEditor. By supporting extra plugin 'imageresponsive' we hope this could work. Steps: open Tour app and open any tour for editing, edit its body using below source, switch back and forth in 'source' view and 'srcset' attribute will disappear. Note that the data still saved into JCR and after saving we still able to use it in our front-end page. Sample code: {source}  srcset="http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed-6.jpg 1x, http://streaming1.danviet.vn/upload/1-2017/images/2017-03-27/14906333904788-unnamed--6-.jpg 2x" /> {source}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (MGNLUI-1951) Queries should use JCR 2.0 bind variable mechanism

2017-03-22 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-1951  
 
 
  Queries should use JCR 2.0 bind variable mechanism   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-4003) CKEditor errors

2017-03-15 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4003  
 
 
  CKEditor errors   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-3640) "Jump to next error" causes NullPointerException when on "Show all" tab

2017-03-15 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3640  
 
 
  "Jump to next error" causes NullPointerException when on "Show all" tab   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-107) As a user I can filter in lists and trees per column (in the header) so that I can search more specifically

2017-03-03 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-107  
 
 
  As a user I can filter in lists and trees per column (in the header) so that I can search more specifically   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-107) As a user I can filter in lists and trees per column (in the header) so that I can search more specifically

2017-03-03 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-107  
 
 
  As a user I can filter in lists and trees per column (in the header) so that I can search more specifically   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Affects Version/s: 
 5.5.2  
 
 
Affects Version/s: 
 5.4.11  
 

  
 
 
 
 

 
 
 

 
 
 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-86) RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded

2017-02-27 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-86  
 
 
  RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Issue Type: 
 Task Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-86) RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded

2017-02-27 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia REST Framework /  MGNLREST-86  
 
 
  RESTEasy 3.0.19.Final has issue, RESTEasy dependency should be upgraded   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-4102) Wrongly replacing of html links in i18n messages

2017-02-23 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4102  
 
 
  Wrongly replacing of html links in i18n messages   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Created according to SUPPORT-6926, please reference to linked ticket for detail description and discussion.If you want to render a i18n message which contains a html link, the link will be replaced by __.It is reproducible on demoauthor instance. Open the groovy console and execute the following statement.{noformat}info.magnolia.objectfactory.Components.getComponent(info.magnolia.i18nsystem.TranslationService.class).translate(new info.magnolia.i18nsystem.FixedLocaleProvider(Locale.ENGLISH), ["pages.noAvailableTemplatesAlert.createTemplateLink"] as String[]) {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 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, 

[magnolia-dev] [JIRA] (MGNLACTIVATION-140) Problem with order when nodetypes are not the same

2017-02-23 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-140  
 
 
  Problem with order when nodetypes are not the same   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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] (PROCRES-8) Module does not work anymore with 5.4.10

2017-01-24 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Processed resources /  PROCRES-8  
 
 
  Module does not work anymore with 5.4.10   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 
 
Environment: 
 Magnolia EE 5.4.10Jackrabbit 2.8Mysql 6 (InnoDB)Apache Tomcat 7.0Oracle Java 1.7Linux  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-145) Publishing config:modules broke public instances

2017-01-24 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jarkko Mantysaari created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-145  
 
 
  Publishing config:modules broke public instances   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Jan/17 10:06 AM  
 
 
Environment: 
 Linux RHEL  H2 Database  Oracle Java 1.8  Apache Tomcat 8.0  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jarkko Mantysaari  
 

  
 
 
 
 

 
 Please refer to bug description and comments in SUPPORT-7161 for more detail. For short: 
 
We have a user who has permission on Configuration app and his module (any module) only, note that he don't have permission on other modules, configuration or server. 
He made a minor change on his /modules/xyz@abc='changed' 
He published his /modules node include sub-nodes. 
After restarting public instance, all configs gone and the instance started from scratch. 

Expected result: Either the publish gets rejected (node contains unpermitted subnodes) or only the allowed module is published.

[magnolia-dev] [JIRA] (EXTIDX-20) Search singular and plural words in French

2017-01-20 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 External indexing and search engine services /  EXTIDX-20  
 
 
  Search singular and plural words in French   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Issue Type: 
 Support Request Improvement  
 

  
 
 
 
 

 
 
 

 
 
 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-3602) info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition is not i18n aware

2017-01-12 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3602  
 
 
  info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition is not i18n aware   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 The info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition is not i18n enabled  https://documentation.magnolia-cms.com/display/DOCS/DAM+upload+field This is reproducable on our demoauthor instance.If I insert the value "true" for i18n parameter (i18n: true) the binary information (binaryData, extension, filename…) is always saved on same node (binaryNodeName: import). In oldest version (Magnolia 5.3.x) the information was saved on a different node: binaryNodeName + language; ex. import_enform:tabs:name: tabUploadlabel: Uploadfields:name: uploadclass: info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinitionlabel: Upload assetbinaryNodeName: importi18n: trueeditFileName: true  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-4117) Loosing part or whole view port in tree view of page app

2017-01-11 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4117  
 
 
  Loosing part or whole view port in tree view of page app   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 When browsing and editing pages using Magnolia page app, user / we encountered a minor issue with tree view that need us to scroll down to update its UI.Steps to reproduce , in some browsers you need to do it a bit quicker, sometimes it worked, sometimes it didn't :Open page app then open 2 or more pages for editing.Switch to page 1 tab, then close it, we will be redirected to tree view.Switch to page 2 tab, then close it, you will see that we lost part or whole of the tree view as below image.Scroll your mouse so that view port get updated and the tree display correctly again. !Screen Shot 2017-01-11 at 4.33.25 PM.png|thumbnail!  We can even right click on the remaining part of the page and the view port response with proper context menu, but right click on the missing part didn't get any response. !Screen Shot 2017-01-11 at 4.56.14 PM.png|thumbnail!
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-4117) Loosing part or whole view port in tree view of page app

2017-01-11 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4117  
 
 
  Loosing part or whole view port in tree view of page app   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 When browsing and editing pages using Magnolia page app, user  /  we encountered a minor issue with tree view that need us to scroll down to update its UI.Steps to reproduce:Open page app then open 2 or more pages for editing.Switch to page 1 tab, then close it, we will be redirected to tree view.Switch to page 2 tab, then close it, you will see that we lost part or whole of the tree view as below image.Scroll your mouse so that view port get updated and the tree display correctly again. !Screen Shot 2017-01-11 at 4.33.25 PM.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 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-4117) Loosing part or whole view port in tree view of page app

2017-01-11 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4117  
 
 
  Loosing part or whole view port in tree view of page app   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Attachment: 
 Screen Shot 2017-01-11 at 4.56.14 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4117) Loosing part or whole view port in tree view of page app

2017-01-11 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4117  
 
 
  Loosing part or whole view port in tree view of page app   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Attachment: 
 Screen Shot 2017-01-11 at 4.33.25 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   




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

[magnolia-dev] [JIRA] (MGNLUI-4117) Loosing part or whole view port in tree view of page app

2017-01-11 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4117  
 
 
  Loosing part or whole view port in tree view of page app   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 When browsing and editing pages using Magnolia page app, user we encountered a minor issue with tree view that need us to scroll down to update its UI.Steps to reproduce:Open page app then open 2 or more pages for editing.Switch to page 1 tab, then close it, we will be redirected to tree view.Switch to page 2 tab, then close it, you will see that we lost part or whole of the tree view as below image.Scroll your mouse so that view port get updated and the tree display correctly again.  !Screen Shot 2017-01-11 at 4.33.25 PM.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 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-4117) Loosing part or whole view port in tree view of page app

2017-01-11 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4117  
 
 
  Loosing part or whole view port in tree view of page app   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5, 5.4.10, 5.4.4  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pages app, tree/list  
 
 
Created: 
 11/Jan/17 10:42 AM  
 
 
Environment: 
 Windows + MacOSX  JDK 8  Chrome + Firefox  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Viet Nguyen  
 

  
 
 
 
 

 
 When browsing and editing pages using Magnolia page app, user we encountered a minor issue with tree view that need us to scroll down to update its UI. Steps to reproduce: Open page app then open 2 or more pages for editing. Switch to page 1 tab, then close it, we will be redirected to tree view. Switch to page 2 tab, then close it, you will see that we lost part or whole of the tree view as below image. Scroll your mouse so that view port get updated and the tree display correctly again.

[magnolia-dev] [JIRA] (MGNLACTIVATION-139) Wrong nodes order after publishing

2017-01-03 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-139  
 
 
  Wrong nodes order after publishing   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Wrong nodes order after publishing in multiple nodetypes content app.Steps to reproduce:Open asset app and create a structure as below: !activation-ordering-author.png|thumbnail! Publish it to public instance, then the '0' folder has been dropped to the bottom: !activation-ordering-public.png|thumbnail!Thanks to [~mchruscielewski] for your provided info:{quote}In ActivationCommand, method protected List getOrderingInfo(Content node) builds list of siblings in correct order for reordering after publication, but it will work only if siblings are of the same type. As we can have multiple node types in one content app (like I have here), it cause order problem I experienced.Please consult somebody if this is expected behaviour, and maybe document it somewhere?My workaround was to extend activationCommand class and change this sibling type check, to accept all my custom node types.{quote}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLACTIVATION-139) Wrong nodes order after publishing

2017-01-03 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-139  
 
 
  Wrong nodes order after publishing   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 
 
Affects Version/s: 
 5.5  
 
 
Affects Version/s: 
 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] (MGNLACTIVATION-139) Wrong nodes order after publishing

2017-01-03 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-139  
 
 
  Wrong nodes order after publishing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 activation-ordering-author.png, activation-ordering-public.png  
 
 
Created: 
 04/Jan/17 7:55 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Viet Nguyen  
 

  
 
 
 
 

 
 Wrong nodes order after publishing in multiple nodetypes content app. Steps to reproduce: Open asset app and create a structure as below:   Publish it to public instance, then the '0' folder has been dropped to the bottom:
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4084) Tree scroll position is not properly maintained in Firefox

2016-12-28 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4084  
 
 
  Tree scroll position is not properly maintained in Firefox   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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-3602) info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition is not i18n aware

2016-12-26 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Viet Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3602  
 
 
  info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition is not i18n aware   
 

  
 
 
 
 

 
Change By: 
 Viet Nguyen  
 
 
Affects Version/s: 
 5.5  
 
 
Affects Version/s: 
 5.4.10  
 

  
 
 
 
 

 
 
 

 
 
 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-4102) Wrongly replacing of html links in i18n messages

2016-12-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4102 
 
 
 
  Wrongly replacing of html links in i18n messages  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.10, 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 19/Dec/16 4:10 AM 
 
 
 

Environment:
 

 Repository: Jackrabbit 2.8  Database: Mysql 6 (InnoDB)  Application server: Apache Tomcat 7.0  Java version: Oracle Java 1.7  Operating system: Linux 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 
Created according to SUPPORT-6926, please reference to linked ticket for detail description and discussion.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (MGNLUI-4081) Separate logic of 'defaultValue' and 'readOnly' in fields

2016-11-16 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4081 
 
 
 
  Separate logic of 'defaultValue' and 'readOnly' in fields  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 

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-4081) Separate logic of 'defaultValue' and 'readOnly' in fields

2016-11-16 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4081 
 
 
 
  Separate logic of 'defaultValue' and 'readOnly' in fields  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5, 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 forms 
 
 
 

Created:
 

 17/Nov/16 5:18 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Thanks to Soisik Froger 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 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:  

 

info.magnolia.ui.form.field.factory.AbstractFieldFactory.setPropertyDataSourceDefaultValue(Property) {
...

[magnolia-dev] [JIRA] (MGNLUI-3275) Redesign upload field (button, text) in a way it fits for every language

2016-11-08 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3275 
 
 
 
  Redesign upload field (button, text) in a way it fits for every language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 In the upload field currently its button and its description sometimes overlap depending on the amount of the text. The width of the button is "controlled" by the amount of text; and the text has a "position: absolute". Current design/layout makes it nearly impossible to find settings which fit for every language.We should find a solution which is NOT (or much less) depending on the amount of text. * Please also consider i18n for these labels. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3275) Redesign upload field (button, text) in a way it fits for every language

2016-11-08 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3275 
 
 
 
  Redesign upload field (button, text) in a way it fits for every language  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 

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-4069) Provide an easy way to set root path for 'Link to DAM document' in Rich text field CKEditor

2016-11-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4069 
 
 
 
  Provide an easy way to set root path for 'Link to DAM document' in Rich text field CKEditor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 - How to reproduce: Open 'Tours' detail sub-app, in rich text editor 'body' field we have 'Link to DAM document' in our CKEditor 'extraPlugins' which always open up a choose dialog using built-in link to root folder of 'dam' workspace. Please refer to attached image  !LinkToDamDocument.png|thumbnail!  for more detail.- Expectation: have a configuration point to set rootPath for this link.- Even better: have a configuration point to add any new button with links to different workspaces and rootPaths.- Please note that as a customer, rootPath and workspace name could be miss configured which mean customer can generate kind of workspace not found or item not found exception or even NPE in case these fields are left blank. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4069) Provide an easy way to set root path for 'Link to DAM document' in Rich text field CKEditor

2016-11-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4069 
 
 
 
  Provide an easy way to set root path for 'Link to DAM document' in Rich text field CKEditor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Attachment:
 
 LinkToDamDocument.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4069) Provide an easy way to set root path for 'Link to DAM document' in Rich text field CKEditor

2016-11-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4069 
 
 
 
  Provide an easy way to set root path for 'Link to DAM document' in Rich text field CKEditor  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 vaadin integration 
 
 
 

Created:
 

 07/Nov/16 8:22 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 

How to reproduce: Open 'Tours' detail sub-app, in rich text editor 'body' field we have 'Link to DAM document' in our CKEditor 'extraPlugins' which always open up a choose dialog using built-in link to root folder of 'dam' workspace. Please refer to attached image for more detail.
 

Expectation: have a configuration point to set rootPath for this link.

[magnolia-dev] [JIRA] (MGNLRSSAGG-209) The servlet should not give error 500 on non existing feeds.

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia RSS Aggregator Module /  MGNLRSSAGG-209 
 
 
 
  The servlet should not give error 500 on non existing feeds.   
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 

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-4036) Impossible to set descending ordering within the contentConnector using defaultOrder

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4036 
 
 
 
  Impossible to set descending ordering within the contentConnector using defaultOrder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 According to Tobias Szczepanski in this support ticket we are NOT able to set descending order in our JCR content app list view SUPPORT-6749 due to hard-coded return value of this function:{code}info.magnolia.ui.workbench.container.AbstractJcrContainer.getDefaultOrderBy(String) :: return new OrderBy(property, true);{code} Could it possible to have an easy way for user just to configure content app to apply correct ordering? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4036) Impossible to set descending ordering within the contentConnector using defaultOrder

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4036 
 
 
 
  Impossible to set descending ordering within the contentConnector using defaultOrder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Original Estimate:
 
 1h 
 
 
 

Remaining Estimate:
 
 1h 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4036) Impossible to set descending ordering within the contentConnector using defaultOrder

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4036 
 
 
 
  Impossible to set descending ordering within the contentConnector using defaultOrder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 11:22 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
According to Tobias Szczepanski in this support ticket we are NOT able to set descending order in our JCR content app list view SUPPORT-6749 due to hard-coded return value of this function: 

 

info.magnolia.ui.workbench.container.AbstractJcrContainer.getDefaultOrderBy(String) :: return new OrderBy(property, true);

[magnolia-dev] [JIRA] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 

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] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Comment:
 
 A comment with security level 'Magnolia International' was removed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Support Score:
 
 
 
 
 

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] (DOCU-852) Cannot create a workspace with a name starting with a digit using Derby

2016-10-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-852 
 
 
 
  Cannot create a workspace with a name starting with a digit using Derby  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 5.4.9 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 18/Oct/16 8:29 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
Thanks to Nils Breunese for his issue reporting, user would not able to name his Derby workspace name starting with a number as described in SUPPORT-6750. Could you please consider add this information somewhere in our setup or trouble shooting section. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[magnolia-dev] [JIRA] (MGNLUI-4034) Support i18n for 'New Component' in area of page editor

2016-10-17 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4034 
 
 
 
  Support i18n for 'New Component' in area of page editor  
 
 
 
 
 
 
 
 
 
 
Support customer to easily change/update 'New component' i18n key in area of our page editor. Please reference to linked Support 6746 issue for more detail. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Attachment:
 
 newComponent.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4034) Support i18n for 'New Component' in area of page editor

2016-10-17 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4034 
 
 
 
  Support i18n for 'New Component' in area of page editor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Comment:
 
 Support customer to easily change/update 'New component' i18n key in area of our page editor. Please reference to linked Support 6746 issue for more detail. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4034) Support i18n for 'New Component' in area of page editor

2016-10-17 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4034 
 
 
 
  Support i18n for 'New Component' in area of page editor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 Support customer to easily change/update 'New component' i18n key in area of our page editor. Please reference to linked Support 6746 issue for more detail. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4034) Support i18n for 'New Component' in area of page editor

2016-10-17 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4034 
 
 
 
  Support i18n for 'New Component' in area of page editor  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 page editor 
 
 
 

Created:
 

 17/Oct/16 11:53 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3983) Drop legacy font-face formats

2016-10-12 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3983 
 
 
 
  Drop legacy font-face formats  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3983) Drop legacy font-face formats

2016-10-12 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3983 
 
 
 
  Drop legacy font-face formats  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (EXTIDX-20) Search singular and plural words in French

2016-09-30 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 External indexing and search engine services /  EXTIDX-20 
 
 
 
  Search singular and plural words in French  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 

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-3983) Drop legacy font-face formats

2016-08-15 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3983 
 
 
 
  Drop legacy font-face formats  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 

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] (DOCU-748) Update Google Sitemap Module user guide

2016-06-16 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-748 
 
 
 
  Update Google Sitemap Module user guide  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Support Request 
 
 
 

Affects Versions:
 

 mid term 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 17/Jun/16 4:55 AM 
 
 
 

Fix Versions:
 

 mid term 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
When user "set a bunch of pages to be hidden from the sitemap.xml file (those are functional pages not content pages) and published the sitemap in the app, the sitemap on the publish servers still show up unwanted urls. This issue happen because currently we are storing "mgnl:googleSiteMapHide=true" in our 'website' workspace which means (s)he will have also to publish his/her affected pages along with sitemap updated info. This cause SUPPORT-6194 happen. Would better if we also update our documentation about this.

[magnolia-dev] [JIRA] (MGNLWORKFLOW-305) As a publisher I should be able to take control of an "InProgress" workitem

2016-06-14 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-305 
 
 
 
  As a publisher I should be able to take control of an "InProgress" workitem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Support Score:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-03-19 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

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

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-03-19 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

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

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-03-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 1.0.3 
 
 
 

Assignee:
 
 Robert Šiška 
 
 
 

Components:
 

 French 
 
 
 

Created:
 

 18/Mar/16 5:09 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 
 
 
 
 
 
 
 
 

MGNLINRS-105
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

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

2016-03-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Viet Nguyen 
 
 
 

Summary:
 
 Wrong  French  delete information message shown when  remove  removing  an item 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-03-18 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

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

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

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLFORM-273) Improve 'ContactEmail' editor

2015-12-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-273 
 
 
 
  Improve 'ContactEmail' editor   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 2.2.14 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 formContactEmailEditor.png, formContactEmailRichTextSourceView.png 
 
 
 

Components:
 

 field 
 
 
 

Created:
 

 07/Dec/15 6:52 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 

Currently we have 2 edit mode for email 'html' and 'text'. 
 

However

[magnolia-dev] [JIRA] (MGNLFORM-273) Improve 'ContactEmail' editor

2015-12-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-273 
 
 
 
  Improve 'ContactEmail' editor   
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Labels:
 
 CKEditor Form 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-3516) DialogMigrationTask did not properly migrate tabs with extends property and some override items

2015-08-10 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3516 
 
 
 
  DialogMigrationTask did not properly migrate tabs with extends property and some override items  
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Attachment:
 
 magnolia_ui-dialog-migration.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3516) DialogMigrationTask did not properly migrate tabs with extends property and some override items

2015-08-10 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3516 
 
 
 
  DialogMigrationTask did not properly migrate tabs with extends property and some override items  
 
 
 
 
 
 
 
 
 
 
 

Updated patch file with some updates to support extends from relative path as well as support partially re-run the migration task (not throw exception when the node already exist).
 
 
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Attachment:
 
 magnolia_ui_dialog.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3516) DialogMigrationTask did not properly migrate tabs with extends property and some override items

2015-08-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3516 
 
 
 
  DialogMigrationTask did not properly migrate tabs with extends property and some override items  
 
 
 
 
 
 
 
 
 
 
 

Attached patch file is an approach.
 
 
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Attachment:
 
 magnolia_ui-dialog-migration.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3516) DialogMigrationTask did not properly migrate tabs with extends property and some override items

2015-08-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3516 
 
 
 
  DialogMigrationTask did not properly migrate tabs with extends property and some override items  
 
 
 
 
 
 
 
 
 
 
In this case, 'tabMobile' was migrated with solely 'extends' property, its 'navTitleMobile' sub node was missed. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Viet Nguyen 
 
 
 

Attachment:
 
 ScreenShot2015-08-07at10.34.21AM.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com

[magnolia-dev] [JIRA] (MGNLUI-3516) DialogMigrationTask did not properly migrate tabs with extends property and some override items

2015-08-06 Thread JIRA (on behalf of Viet Nguyen) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viet Nguyen created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3516 
 
 
 
  DialogMigrationTask did not properly migrate tabs with extends property and some override items  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.3.10 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 07/Aug/15 5:46 AM 
 
 
 

Labels:
 

 affect-vn-project 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Viet Nguyen 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 

During migration process from 4.5.24 to 5.3.10, we experienced that DialogMigrationTask did not properly migrate tabs with extends property and some override items. It omitted override items then the migrated version missed all those data.
 

Refer to attached patch as an approach.