[magnolia-dev] [JIRA] (MGNLUI-2796) Add action to open a page preview in a separate tab

2015-12-24 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2796 
 
 
 
  Add action to open a page preview in a separate tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sang Ngo Huu 
 
 
 

Original Estimate:
 
 2d 
 
 
 

Remaining Estimate:
 
 2d 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-2796) Add action to open a page preview in a separate tab

2015-12-24 Thread JIRA (on behalf of Sang Ngo Huu) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sang Ngo Huu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2796 
 
 
 
  Add action to open a page preview in a separate tab  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sang Ngo Huu 
 
 
 

Assignee:
 
 Sang Ngo Huu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3731) Migrate legacy permissions app to security app

2015-12-24 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 5.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 security app 
 
 
 

Created:
 

 24/Dec/15 9:28 AM 
 
 
 

Labels:
 

 app 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Mikaël Geljić 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
As part of phasing out the old admininterface-legacy, we must migrate the old permissions app to a new Vaadin subapp, within the security app.

[magnolia-dev] [JIRA] (MGNLUI-3731) Migrate legacy permissions app to security app

2015-12-24 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLUI-2289) Migrate tools pages to new UI

2015-12-24 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2289 
 
 
 
  Migrate tools pages to new UI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 Migrate tools pages to new UI:* --export-- (covered by new JCR tools app)* --import-- (covered by new JCR tools app)* --jcrUtils-- (covered by new JCR tools app)* logViewer*  --  permission --  ( to security app? covered by MGNLUI-3731 )* configInfo (to about-app?)* developmentUtils 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3731) Migrate legacy permissions app to security app

2015-12-24 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Story Points:
 
 8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3731) Migrate legacy permissions app to security app

2015-12-24 Thread on behalf of Mikaël Geljić 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3731 
 
 
 
  Migrate legacy permissions app to security app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  25  24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3732) Migration of images loses ID's

2015-12-24 Thread JIRA (on behalf of Mathijn Elhorst) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mathijn Elhorst created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3732 
 
 
 
  Migration of images loses ID's  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 24/Dec/15 3:11 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Mathijn Elhorst 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
in the final test-fase of our magnolia 5 migration we've encountered a serious issue in the migration of the images. 
The images are being migrated to a new workspace, but in the proces they get a new UUID. All the internal links are being updated, so we don't see any problems at first. But the ID's between the author and the public instances do differ and here the problem starts when we start activating from the author instance. The public nodes receive ID's they don't now about. 
The simplest solution would be to reactivate all. But in our case this is a no-go as it would take weeks to complete. 
Hence, we are seeking a solution where we can simply use the same ID in the migration. We currently are investigating the Clone: {{if (!folder.hasNode(oldImage.getName())) { log.info("Creating new image {}/{}", folder.getPath(), oldImage.getName()); Node newImage = folder.getSession().getWorkspace().clone(oldImage.getSession().getWorkspace().getName(), oldImage.getPath(), folder.getPath() + "/" + oldImage.getName(), false) newImage.setProperty(JcrConstants.JCR_FROZENPRIMARYTYPE, AssetNodeTypes.Asset.NAME) //Node newImage = NodeUtil.createPath(folder, oldImage.getName(), AssetNodeTypes.Asset.NAME)}} 
but perhaps there are other possibilities to keep the same