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

2016-10-31 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 Aleksandr Pchelintcev Philip Mundt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-10-25 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
DefinitionsAppUITest#showConfigActionOpensCorrectFileInConfigurationApp() fails due to broken Show in Configuration app action. 
 
 
 
 
 
 
 
 
 
 Definitions app /  CFGUI-50 
 
 
 
  Build unique url fragment in content connector  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In 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] (CFGUI-50) Build unique url fragment in content connector

2016-10-25 Thread JIRA (on behalf of Aleksandr Pchelintcev) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Assignee:
 
 Cedric Reichenbach Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-10-25 Thread JIRA (on behalf of Philip Mundt) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

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

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

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 Cedric Reichenbach 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

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

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

Change By:
 
 Cedric Reichenbach 
 
 
 
 
 
 
 
 
 
 Currently, the fragment consists of the definition's path itself and the selected path within the definition.  -  However, since a definition's path is not unique, there may be collisions. For instance, templating has two definitions with the same path {{/modules/templating/templates/plaintext}}; one of type renderer and one of type template. Including their type in the fragment would avoid this particular collision. - In general, two items should have the same path fragment exactly when1. Their corresponding DefinitionProviderIds are "{{#equals}}"2. They point to the same sub-path inside their corresponding definition 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

2016-10-13 Thread JIRA (on behalf of Cedric Reichenbach) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cedric Reichenbach created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 13/Oct/16 2:39 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Cedric Reichenbach 
 
 
 
 
 
 
 
 
 
 
Currently, the fragment consists of the definition's path itself and the selected path within the definition. However, since a definition's path is not unique, there may be collisions. For instance, templating has two definitions with the same path /modules/templating/templates/plaintext; one of type renderer and one of type template. Including their type in the fragment would avoid this particular collision. 
In general, two items should have the same path fragment exactly when 
1. Their corresponding DefinitionProviderIds are "#equals" 2. They point to the same sub-path inside their corresponding definition 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment