[magnolia-dev] [JIRA] (BUILD-253) Magnolia upgrade (5.3 > 5.4) doesn't work - and login credentials for Nexus

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Build /  BUILD-253 
 
 
 
  Magnolia upgrade (5.3 > 5.4) doesn't work - and login credentials for Nexus  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

Reporter:
 
 Felix Romer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-756) Definition app module page

[JIRA (on behalf of Ruth Stocks)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Stocks updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-756 
 
 
 
  Definition app module page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ruth Stocks 
 
 
 

Assignee:
 
 Ruth Stocks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-818) Document Content Importer Module

[JIRA (on behalf of Ruth Stocks)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Stocks updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-818 
 
 
 
  Document Content Importer Module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ruth Stocks 
 
 
 

Assignee:
 
 Ruth Stocks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-756) Definition app module page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-756 
 
 
 
  Definition app module page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 Create the Definition app docs. I propose 2 pages:- _*Module page*_; can be very small, mainly containing the typical installing instructions- _*App page*_ - which will be the main taks.The *app page* should explain:- The meaning of the app- - It shows only definition items which belong to a registry-- The displayed items may be decorated, the app shows the decorated state (to be checked e.g. with [~apchelintcev] or just by testing it)--- etc. pp-  How it can help a developer, why it is useful, that  it will be replacement for the (JCR based) configuration app in many but not in all aspects- etc. ppAn important note - to repeat it again:When does it make sense to use the definition app instead of the  (JCR based) configuration app, and when not.Since we have a bunch of links to the (JCR based) configuration app, some of them also must be aligned / changed. However, for this we may want to create another, related ticket. A would do the task in the following order:  - create the Definition app Module page (on DOCS55)  - create the Definition app App page (on DOCS55)  - Copy the (JCR based) configuration app (and its module page, if there is one) to DOCS55 (and lock the originals)- Go to DOCS and check the pages which are linked to the https://documentation.magnolia-cms.com/display/DOCS/Configuration+app ... then let's see how to proceed.-- We may move / copy all these pages then to DOCS55 and link them accordingly (some may link to Configuration app, others may link to Definition app).How to test / check the definition app?The 5.5-SNAPSHOT bundles do contain the Definition app, check https://documentation.magnolia-cms.com/display/DOCS55/Release+notes+for+Magnolia+Core+5.5 and download one of the SNAPSHOT bundles there 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (DOCU-756) Definition app module page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-756 
 
 
 
  Definition app module page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 Create the Definition app  module  docs. I propose 2 pages:- _*Module  page *_; can be very small, mainly containing the typical installing instructions- _*App page*_ - which will be the main taks . Explain some "concepts" The *app page* should explain :-  when and for what using  The meaning of  the  Definitions  app-  when to use  How it can help a developer, why it is useful, that  it will be replacement for  the ( old  JCR based) configuration app  in many but not in all aspects  - etc. pp  Note:  An important note -  The Definition app has  to  replace  repeat it again:When does it make sense to use  the  definition app instead of  the ( old  JCR based) configuration app,  however it can only read but never write data! If you have to write data, you must use another tool; in some cases it has to be the Resources app  and when not . Add some screenshots, etc. ppProbably Since  we  also  have  to change  a bunch of  links  pointing  to the  (JCR based)  configuration app  on many pages; to , some of them also must  be  defined  aligned  /  decides later on  changed. However ,  once  for this  we  know what the definition app all can or cannot  may want to create another, related ticket .  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: 

[magnolia-dev] [JIRA] (DOCU-756) Definition app module page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-756 
 
 
 
  Definition app module page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 Create the Definition app module page.Explain some "concepts":- when and for what using the Definitions app- when to use the (old JCR based) configuration app Note:- The Definition app has to replace the the (old JCR based) configuration app, however it can only read but never write data! If you have to write data, you must use another tool; in some cases it has to be the Resources app. Add some screenshots, etc. ppProbably we also have to change links pointing to the configuration app on many pages; to be defined / decides later on, once we know what the definition app all can or cannot. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (YAMLEXT-2) Normalization of the Syntax

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Zimmermann updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Yaml extensions /  YAMLEXT-2 
 
 
 
  Normalization of the Syntax  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christopher Zimmermann 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-758) Update Theme page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-758 
 
 
 
  Update Theme page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 Themes can be defined with YAML.That's why https://documentation.magnolia-cms.com/display/DOCS/Theme requires an update. A few things worth to mention:- There will be 2 ways to configure themes:-- the old way under {{sites/config/themes}}-- the new way:  id: config:/modules//themes/; path resources:{{/themes/.yaml}}- The themes app will be removed because it can only display configured by the new way! Instead people must use the definition app to view the theme. To edit a theme they may use the resources app. See MGNLSITE-48 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles as all legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can add {{adminInterface-legacy}} back manually to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing  all  some of  leftovers from {{adminInterface-legacy}}  (see related issues for other modules doing their part)  and eventually remove the module itself. In the current 5.5.-SNAPSHOT EE pro bundle the following references to old {{admininterface}} have been found{code}config workspace---/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/ui-admincentral/templates/deleted@i18nBasename/modules/jcr-browser-app/apps/jcr-browser/subApps@extends value must change to /modules/ui-admincentral/apps/configuration/subApps/modules/adminInterfaceuserroles workspace---// found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’/security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/security-base/acl_uri/00//from forum module/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0// found by searching in JCR app for '*admininterface*'//from resources module/resources-base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03//from templating samples module/editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0// all other workspaces seem to contain no reference to admininterface{code} More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely. Subtasks will be created for that if needed.   
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles ,  as all  the  legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can  manually  add {{adminInterface-legacy}} back  manually  to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing some of  the  leftovers from {{adminInterface-legacy}} (see related issues for other modules doing their part) and eventually remove  the  {{adminInterface-legacy}}  module itself. In the current  {{  5.5.-SNAPSHOT EE pro bundle }}  the following references to old {{admininterface}} have been found{code}config workspace---/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/ui-admincentral/templates/deleted@i18nBasename/modules/jcr-browser-app/apps/jcr-browser/subApps@extends value must change to /modules/ui-admincentral/apps/configuration/subApps/modules/adminInterfaceuserroles workspace---// found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’/security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/security-base/acl_uri/00//from forum module/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0// found by searching in JCR app for '*admininterface*'//from resources module/resources-base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03//from templating samples module/editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0// all other workspaces seem to contain no reference to admininterface{code} More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely. Subtasks will be created for that if needed.   
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles, as all the legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can manually add {{adminInterface-legacy}} back to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing some of the leftovers from {{adminInterface-legacy}} (see related issues for other modules doing their part) and eventually remove {{adminInterface-legacy}} module itself. In the current {{5.5.-SNAPSHOT EE pro bundle}} the following references to old {{admininterface}} have been found{code}config workspace---/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/ui-admincentral/templates/deleted@i18nBasename/modules/jcr-browser-app/apps/jcr-browser/subApps@extends value must change to /modules/ui-admincentral/apps/configuration/subApps/modules/adminInterfaceuserroles workspace---// found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’/security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/security-base/acl_uri/00//from forum module/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0// found by searching in JCR app for '*admininterface*'//from resources module/resources-base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03//from templating samples module/editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0// all other workspaces seem to contain no reference to admininterface{code} More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely. Subtasks will be created for that if needed. TO INVESTIGATE FURTHER legacy messages.properties in {{ui-admincentral}}. Can they be removed?    
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (CFGUI-5) Prepare the definitions app for inclusion in product

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-5 
 
 
 
  Prepare the definitions app for inclusion in product  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

Release notes required:
 
 Yes 
 
 
 

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] (MGNLCI-10) Task list actions are untranslated.

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-10 
 
 
 
  Task list actions are untranslated.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Attachment:
 
 Screen Shot 2016-09-27 at 17.02.47.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] (MGNLCI-9) There must be a way to delete or archive an import task

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-9 
 
 
 
  There must be a way to delete or archive an import task  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Attachment:
 
 Screen Shot 2016-09-27 at 16.52.17.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] (MGNLCI-11) The import directory shouldn't have to be a subdirectory of the resources directory

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-11 
 
 
 
  The import directory shouldn't have to be a subdirectory of the resources directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 The import directory shouldn't have to be a subdirectory of the resources directory . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-11) The import directory shouldn't have to be a subdirectory of the resources directory.

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-11 
 
 
 
  The import directory shouldn't have to be a subdirectory of the resources directory.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 The import directory  shouldnt  shouldn't  have to be a subdirectory of the resources directory. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] Re: Is Microsoft server 2016 compatible with Mangnolia?

[Jan Haderka (via Magnolia Forums)]

2014 or newer should work just fine. Basically anything that JackRabbit 
supports will work.

HTH,
Jan

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=74d87ca6-4679-47ae-8856-508cdb11b30d



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] Is Microsoft server 2016 compatible with Mangnolia?

[Amol Gaikwad (via Magnolia Forums)]

Does Magnolia EE 5.3.8 support Microsoft SQL Server 2014 and later editions? 
For other databases we can see Oracle 10g Enterprise Edition and later, but for 
MS SQL Server it is only Microsoft SQL Server 2012.Pls help[.Thanks

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=74d87ca6-4679-47ae-8856-508cdb11b30d



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 Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 27/Sep/16 4:11 PM 
 
 
 

Fix Versions:
 

 5.3.2 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 
Remove unused references to adminInterface-legacy found in userroles workspace 

 

/editor/acl_config/03
/developer/acl_config/01
/editor/acl_config/00
/developer/acl_config/00
/editor/acl_config/0
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles as all legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can add {{adminInterface-legacy}} back manually to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing all leftovers from {{adminInterface-legacy}} and eventually remove the module itself. In the current 5.5.-SNAPSHOT EE pro bundle the following references to old {{admininterface}} have been found{code}config workspace---/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/ui-admincentral/templates/deleted@i18nBasename/modules/jcr-browser-app/apps/jcr-browser/subApps@extends value must change to /modules/ui-admincentral/apps/configuration/subApps/modules/adminInterfaceuserroles workspace---// found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’/security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/ forum_ALL security - admin base /acl_uri/ 0 00   / /from forum module/ forum_ALL- user admin /acl_uri/0/forum_ALL- moderator user /acl_uri/0/ security forum_ALL - base moderator /acl_uri/ 00 0 // found by searching in JCR app for '*admininterface*'/ /from resources  module/resources -base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03  / /from templating samples module/ editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0// all other workspaces seem to contain no reference to admininterface{code} More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely.  A subtask  Subtasks  will be created for that  if needed .       
 
 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (CFGUI-43) Make use of new querying capabilities of registry

[JIRA (on behalf of Cedric Reichenbach)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cedric Reichenbach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cedric Reichenbach 
 
 
 

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] (MGNLUI-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

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] (MGNLFORUM-293) Remove dependency on admininterface-legacy

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Forum Module /  MGNLFORUM-293 
 
 
 
  Remove dependency on admininterface-legacy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Summary:
 
 Remove  Forum and Admin  dependency on admininterface - Legacy from the bundle legacy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles as all legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can add {{adminInterface-legacy}} back manually to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing all leftovers from {{adminInterface-legacy}} and eventually remove the module itself. In the current 5.5.-SNAPSHOT EE pro bundle the following references to old {{admininterface}} have been found{code}config workspace---/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/ui-admincentral/templates/deleted@i18nBasename  /modules/ jcr-browser-app/apps/jcr-browser/subApps@extends value must change to /modules/ui-admincentral/apps/configuration/subApps/modules/ adminInterfaceuserroles workspace---// found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’/security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0/security-base/acl_uri/00// found by searching in JCR app for '*admininterface*'/resources-base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03/editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0// all other workspaces seem to contain no reference to admininterface{code} More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely. A subtask will be created for that.       
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
  

[magnolia-dev] [JIRA] (MGNLCI-3) Log at startup including the path of the watched directory

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-3 
 
 
 
  Log at startup including the path of the watched directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Sprint:
 
 Basel 63 
 
 
 

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] (MGNLCI-6) Only detect files with an .xml suffix

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Content Importer Module /  MGNLCI-6 
 
 
 
  Only detect files with an .xml suffix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Sprint:
 
 Basel 63 
 
 
 

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-3480) Sorting in content apps only works for JCR properties

[JIRA (on behalf of Mercedes Iruela)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mercedes Iruela updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3480 
 
 
 
  Sorting in content apps only works for JCR properties  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mercedes Iruela 
 
 
 

Component/s:
 
 tree/list 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 {{info.magnolia.ui.workbench.tree.HierarchicalJcrContainer#getParent(Object)}} tries to determine the parent of a passed root node, resulting in an unnessecary 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] (MGNLUI-3914) HierarchicalJcrContainer#getParent(Object) tries to determine parent of root node resulting in log messages

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Philip Mundt 
 
 
 

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

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Philip Mundt 
 
 
 

Affects Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (MGNLDEMO-186) Remove Clicky icon from demo

[JIRA (on behalf of Ilgun Ilgun)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ilgun Ilgun updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-186 
 
 
 
  Remove Clicky icon from demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ilgun Ilgun 
 
 
 

Summary:
 
 remove Remove  Clicky icon from demo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-60) RESTEasy dependency should be upgraded to latest.

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia REST Framework /  MGNLREST-60 
 
 
 
  RESTEasy dependency should be upgraded to latest.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Assignee:
 
 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] (MGNLUI-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles as all legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can add {{adminInterface-legacy}} back manually to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing all leftovers from {{adminInterface-legacy}} and eventually remove the module itself. In the current  5.5.-SNAPSHOT  EE pro bundle the following references to old  {{  admininterface }}  have been found{code}config workspace---/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/ui-admincentral/templates/deleted@i18nBasename/modules/adminInterfaceuserroles workspace---// found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’/security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0/security-base/acl_uri/00// found by searching in JCR app for '*admininterface*'/resources-base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03/editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0 // all other workspaces seem to contain no reference to admininterface {code} More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely. A subtask will be created for that.   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLCACHE-145) Cache key generators provided via X-Magnolia-Cache header has to be registered

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-145 
 
 
 
  Cache key generators provided via X-Magnolia-Cache header has to be registered  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

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] (MGNLUI-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 With Magnolia 5.5 {{adminInterface-legacy}} will be removed entirely from the bundles as all legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can add {{adminInterface-legacy}} back manually to their web apps in case they still need it.{{ui-admincentral}} MVH will take care of removing all leftovers from {{adminInterface-legacy}} and eventually remove the module itself. In the current EE pro bundle the following references to old admininterface have been found{code} * config workspace * --- -- /server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j  /modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools /modules/ui-admincentral/templates/deleted@i18nBasename   /modules/adminInterface *user roles userroles  workspace * ---   //  found with  select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’ )  --    /security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0/security-base/acl_uri/00 // found by searching in JCR app for '*admininterface*'/resources-base/acl_config/02/resources-base/acl_config/01/resources-base/acl_config/03/editor/acl_config/03/developer/acl_config/01/editor/acl_config/00/developer/acl_config/00/editor/acl_config/0 {code}  More references in module descriptors—- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AMODULES%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3APLATFORM%20ext%3Axml%20admininterface- https://git.magnolia-cms.com/plugins/servlet/search?q=project%3AENTERPRISE%20%20ext%3Axml%20admininterfaceSome of the above should be removable safely. A subtask will be created for that.    
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLCACHE-145) Cache key generators provided via X-Magnolia-Cache header has to be registered

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-145 
 
 
 
  Cache key generators provided via X-Magnolia-Cache header has to be registered  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Release notes required:
 
 Yes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCACHE-145) Cache key generators provided via X-Magnolia-Cache header has to be registered

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Reopened: to be reverted. 
 
 
 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-145 
 
 
 
  Cache key generators provided via X-Magnolia-Cache header has to be registered  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed 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] (MGNLCACHE-94) Use the Apache HttpComponents instead of the Commons HttpClient

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-94 
 
 
 
  Use the Apache HttpComponents instead of the Commons HttpClient  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

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] (MGNLCACHE-147) Cache filter is not triggered for forwards

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-147 
 
 
 
  Cache filter is not triggered for forwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Sprint:
 
 Kromeriz 63 
 
 
 

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-4027) Remove adminInterface-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove adminInterface-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Summary:
 
 Remove  admin  adminInterface -legacy module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Remove admin-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Remove admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Summary:
 
 Add remove tasks for Remove  admin-legacy module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Add remove tasks for admin-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Add remove tasks for admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Release notes required:
 
 Yes 
 
 
 

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] (MGNLDEMO-186) remove Clicky icon from demo

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-186 
 
 
 
  remove Clicky icon from demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 
 
 
 
 
 
 
 https://demopublic.magnolia-cms.com/ same as travel demo on 5.5-snapshot has  an  entry in Tools > marketing tags which adds clicky  snipet  snippet  in to pages, but first line of this code is  no need becasue  not needed because  its only displaying  the  clicky logo on page (see screenshot).  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Add remove tasks for admin-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Add remove tasks for admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 tbd With Magnolia 5 . 5 {{adminInterface-legacy}} will be removed entirely from the bundles as all legacy apps (except for {{DevTools}}?) have been converted to the new Vaadin-based UI. Customers can add {{adminInterface-legacy}} back manually to their web apps in case they still need it.  {{ui-admincentral}} MVH will take care of removing all leftovers from {{adminInterface-legacy}} and eventually remove the module itself. In the current EE pro bundle the following references to old admininterface have been found{code}*config workspace*-/server/i18n/authoringLegacy/server/filters/servlets/AdminTreeServlet/server/filters/servlets/DialogServlet/server/filters/servlets/PageServlet/modules/ui-admincentral/apps/websiteJcrBrowser/modules/ui-admincentral/apps/logViewer/modules/ui-admincentral/apps/configInfo/modules/ui-admincentral/apps/export/modules/ui-admincentral/apps/import/modules/ui-admincentral/apps/jcrQueryUtils/modules/ui-admincentral/apps/devTools/modules/ui-admincentral/apps/permissions/modules/ui-admincentral/apps/log4j/modules/ui-admincentral/config/appLauncherLayout/groups/dev/apps/devTools/modules/adminInterface*user roles workspace*  // select * from [nt:base] as n where n.path like '%/.magnolia/pages/%’)--  /security-base/acl_uri/02/security-base/acl_uri/03/security-base/acl_uri/04/security-base/acl_uri/05/security-base/acl_uri/06/security-base/acl_uri/07/security-base/acl_uri/08/forum_ALL-admin/acl_uri/0/forum_ALL-user/acl_uri/0/forum_ALL-moderator/acl_uri/0/security-base/acl_uri/00{code}    
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLWORKFLOW-338) Update jbpm to 6.4

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-338 
 
 
 
  Update jbpm to 6.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Espen Jervidalo 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-186) remove Clicky icon from demo

[JIRA (on behalf of Philip Mundt)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Mundt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-186 
 
 
 
  remove Clicky icon from demo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philip Mundt 
 
 
 

Fix Version/s:
 
 0.15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Add remove tasks for admin-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Add remove tasks for admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Project:
 
 Magnolia  Admininterface Legacy Module (4.x compatibility)  UI 
 
 
 

Key:
 
 MGNLADMLEG MGNLUI - 69 4027 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4027) Add remove tasks for admin-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Add remove tasks for admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

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] (MGNLUI-4027) Add remove tasks for admin-legacy module.

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-4027 
 
 
 
  Add remove tasks for admin-legacy module.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Component/s:
 
 admincentral 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLWORKFLOW-338) Update jbpm to 6.4

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Espen Jervidalo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Workflow Module /  MGNLWORKFLOW-338 
 
 
 
  Update jbpm to 6.4  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 27/Sep/16 11:30 AM 
 
 
 

Fix Versions:
 

 5.6 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Espen Jervidalo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Attachment:
 
 pages.patch 
 
 
 

Attachment:
 
 DetailLocation.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (PAGES-93) Reflect Authoring locale in Pages app's location fragment

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-93 
 
 
 
  Reflect Authoring locale in Pages app's location fragment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Patch included:
 
 Yes 
 
 
 

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] (PAGES-90) Open-in-tab button does not open correct url

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 

Fix Version/s:
 
 5.4.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

[magnolia-dev] [JIRA] (CFGUI-43) Make use of new querying capabilities of registry

[JIRA (on behalf of Cedric Reichenbach)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cedric Reichenbach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-43 
 
 
 
  Make use of new querying capabilities of registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cedric Reichenbach 
 
 
 

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] (PAGES-90) Open-in-tab button does not open correct url

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Aleksandr Pchelintcev 
 
 
 

Fix Version/s:
 
 5.4.10 
 
 
 

Fix Version/s:
 
 5.4.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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