[magnolia-dev] [JIRA] (MGNLUI-3699) JcrNodeAdapter#getJcrItem do not return VersionedNode and VersionedChildNode wrapped.

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 
The 'Save changes' button is present also for versions which causes UI tests to fail: https://jenkins.magnolia-cms.com/job/magnolia-bundle_trunk-with-selenium_profile/lastBuild/#showFailuresLink 
 
 
 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3699 
 
 
 
  JcrNodeAdapter#getJcrItem do not return VersionedNode and VersionedChildNode wrapped.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (JCRTOOLS-20) New export function creates erroneous bootstrap

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-20 
 
 
 
  New export function creates erroneous bootstrap  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Bradley Andersen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (SUGGEST-14) LightModule resources life distribution: Define a conveniant best practice

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-14 
 
 
 
  LightModule resources life distribution: Define a conveniant best practice  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Christopher Zimmermann 
 
 
 

Created:
 

 25/Jan/16 2:31 PM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Christian Ringele 
 
 
 
 
 
 
 
 
 
 
Using light module development approach for front end leaves a couple of questions open in regards of: How to use it and distribute changes on life systems. 
A main problems I see is: 
 

how to guarantie that the newest changes in light modules are distributed 100% equally trough all instances?
 

how can a customer know which node has wich state of resources loaded? (How can I be sure public2 has the same resources as public1 or public3).
 

When setting magnolia.develop=false changes in the light modules (file system) are detected, BUT the JS & CSS is still served cached. And we have no mechanism to flush the caceh on public instances (except activating something).
 
 
My suggestion: We could define a simple best practice approach: They are observed & loaded & managed on the author, and 

[magnolia-dev] [JIRA] (MGNLUI-3752) In-line edited property is not always selected after saving changes

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3752 
 
 
 
  In-line edited property is not always selected after saving changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 5.4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3755) Possible StackOverflow when DefinitionCloner tries to clone i18n proxies

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3755 
 
 
 
  Possible StackOverflow when DefinitionCloner tries to clone i18n proxies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Project:
 
 Magnolia  UI 
 
 
 

Key:
 
 MAGNOLIA MGNLUI - 6447 3755 
 
 
 

Affects Version/s:
 
 5.4.3 
 
 
 

Affects Version/s:
 
 5.4.3 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-3754) DefinitionCloner should not clone ComponentProvider and ResourceOrigin

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3754 
 
 
 
  DefinitionCloner should not clone ComponentProvider and ResourceOrigin  
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 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] (DOCU-649) Explain how to access a content app via REST api from client side

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-649 
 
 
 
  Explain how to access a content app via REST api from client side  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  5  6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 Job [magnolia-bundle_5.3.x-with-selenium_profile|https://jenkins.magnolia-cms.com/job/magnolia-bundle_5.3.x-with-selenium_profile] has a recurring failure on {{SeleniumProfileTestingUITest}} Download of the exported file doesn't seem to get started properly.It appeared when main was updated to 5.3.13-SNAPSHOT, so we had suspicion that it was related to change of content-types. Although state seems to be the same as on master, on this regard.For now, we decided to {{@Ignore}} that test, until further investigation here.Some more input:* test passed *locally*:** hosted on the mac, both on Java 6 + Jetty 6, or Java 8 + Jetty 9** upgraded selenium for latest FF** download also works with client in the VM (fetching file for assertion fails obviously)* I have a \*fast\* debug job on *jenkins*, but no luck so far: [ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest|https://jenkins.magnolia-cms.com/job/ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest/]** checks out branch {{debug-SeleniumProfileTestingUITest}}## #1 failed with same settings as 5.3.x## #2 errored with upgrade to selenium 2.49.1 (selenium upgrade seemingly couldn't run on java 6)## #3 failed on java 7## #4 errored again after attempt to use jetty9 profileUpdate:*# #8 passed on jetty9 (quick and dirty  cherry-pick  backport of Jetty 9 )  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (CFGUI-13) Relocate definitions app from forge to community

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-13 
 
 
 
  Relocate definitions app from forge to community  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 Since it is a good time to bring the app to a new level of maturity and closer to the users we need to move it from Forge to Community modules: maven:{code:xml}   info.magnolia.definitions  magnolia-definitions-app  1.0-SNAPSHOT {code}  - New   git  location : [  https://git.magnolia-cms.com/projects/MODULES/repos/definitions-app/browse ]  - New module name: _magnolia-definitions-app_UPD 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-13) Relocate definitions app from forge to community

[JIRA (on behalf of Aleksandr Pchelintcev)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aleksandr Pchelintcev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-13 
 
 
 
  Relocate definitions app from forge to community  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aleksandr Pchelintcev 
 
 
 
 
 
 
 
 
 
 Since it is a good time to bring the app to a new level of maturity and closer to the users we need to move it from Forge to Community modules: - Proposed new maven coordinates: _info   info .magnolia. definitions_:_magnolia definitions  magnolia -definitions- app_ app    1.0 - SNAPSHOT-  New git location:  _https  https ://git.magnolia-cms.com/projects/MODULES/repos/definitions-app/ browse_ browse - New module name: _magnolia-definitions-app_ UPD 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3752) In-line edited property is not always selected after saving changes

[JIRA (on behalf of Federico Grilli)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Grilli updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3752 
 
 
 
  In-line edited property is not always selected after saving changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Federico Grilli 
 
 
 

Assignee:
 
 Federico Grilli 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-536) Uploading binaries with REST

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-536 
 
 
 
  Uploading binaries with REST  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint 6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-536) Uploading binaries with REST

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-536 
 
 
 
  Uploading binaries with REST  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Assignee:
 
 Antti Hietala Ruth Stocks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 Job [magnolia-bundle_5.3.x-with-selenium_profile|https://jenkins.magnolia-cms.com/job/magnolia-bundle_5.3.x-with-selenium_profile] has a recurring failure on {{SeleniumProfileTestingUITest}} Download of the exported file doesn't seem to get started properly.It appeared when main was updated to 5.3.13-SNAPSHOT, so we had suspicion that it was related to change of content-types. Although state seems to be the same as on master, on this regard.For now, we decided to {{@Ignore}} that test, until further investigation here.Some more input:* test passed *locally*:** hosted on the mac, both on Java 6 + Jetty 6, or Java 8 + Jetty 9** upgraded selenium for latest FF** download also works with client in the VM (fetching file for assertion fails obviously)* I have a \*fast\* debug job on *jenkins*, but no luck so far: [ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest|https://jenkins.magnolia-cms.com/job/ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest/]** checks out branch {{debug-SeleniumProfileTestingUITest}}## #1 failed with same settings as 5.3.x## #2 errored with upgrade to selenium 2.49.1## #3 failed on java 7 (selenium upgrade seemingly couldn't run on java 6?)## #4 errored again after attempt to use jetty9 profileUpdate: * ##  # 8 passed on jetty9 (quick and dirty cherry-pick) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 Job [magnolia-bundle_5.3.x-with-selenium_profile|https://jenkins.magnolia-cms.com/job/magnolia-bundle_5.3.x-with-selenium_profile] has a recurring failure on {{SeleniumProfileTestingUITest}} Download of the exported file doesn't seem to get started properly.It appeared when main was updated to 5.3.13-SNAPSHOT, so we had suspicion that it was related to change of content-types. Although state seems to be the same as on master, on this regard.For now, we decided to {{@Ignore}} that test, until further investigation here.Some more input:*  I could get that  test  to pass  passed *  locally  (jetty9 / *:** hosted on the mac, both on Java 6 + Jetty 6, or Java 8 + Jetty 9**  upgraded selenium  and  for latest  FF ** download also works with client in the VM (fetching file for assertion fails obviously )  * I have a \*fast\* debug job  on *jenkins* , but no luck so far: [ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest|https://jenkins.magnolia-cms.com/job/ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest/]** checks out branch {{debug-SeleniumProfileTestingUITest}}## #1 failed with same settings as 5.3.x## #2 errored with upgrade to selenium 2.49.1## #3 failed on java 7 (selenium upgrade seemingly couldn't run on java 6?)## #4 errored again after attempt to use jetty9 profile Update:## #8 passed on jetty9 (quick and dirty cherry-pick) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 Job [magnolia-bundle_5.3.x-with-selenium_profile|https://jenkins.magnolia-cms.com/job/magnolia-bundle_5.3.x-with-selenium_profile] has a recurring failure on {{SeleniumProfileTestingUITest}} Download of the exported file doesn't seem to get started properly.It appeared when main was updated to 5.3.13-SNAPSHOT, so we had suspicion that it was related to change of content-types. Although state seems to be the same as on master, on this regard.For now, we decided to {{@Ignore}} that test, until further investigation here.Some more input:* test passed *locally*:** hosted on the mac, both on Java 6 + Jetty 6, or Java 8 + Jetty 9** upgraded selenium for latest FF** download also works with client in the VM (fetching file for assertion fails obviously)* I have a \*fast\* debug job on *jenkins*, but no luck so far: [ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest|https://jenkins.magnolia-cms.com/job/ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest/]** checks out branch {{debug-SeleniumProfileTestingUITest}}## #1 failed with same settings as 5.3.x## #2 errored with upgrade to selenium 2.49.1 ## #3 failed on java 7  (selenium upgrade seemingly couldn't run on java 6 ? )## # 3 failed on java 7## # 4 errored again after attempt to use jetty9 profileUpdate:*# #8 passed on jetty9 (quick and dirty cherry-pick) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (NPMBUILD-2) When name: @magnolia/ magnolia-build ignore it

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia light-module build tools /  NPMBUILD-2 
 
 
 
  When name: @magnolia/ magnolia-build ignore it  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 25/Jan/16 2:17 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
if name of light module in package.json is scoped to magnolia, e.g.: 

 
"name": "@magnolia/hello-magnolia",
 

 
and when project is installed (npm install), this "hello-magnolia" is placed into node_modules/@magnolia/hello-magnolia , (one folder deeper) and magnolia-build can't found it and just print "No Magnolia light modules found." 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (DOCU-606) Categorization update

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-606 
 
 
 
  Categorization update  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  5  6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-657) Clean up Certified stack on 4.5

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-657 
 
 
 
  Clean up Certified stack on 4.5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  5  6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (DOCU-574) Update Categorization doc with YAML and catfn

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-574 
 
 
 
  Update Categorization doc with YAML and catfn  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 

Sprint:
 
 Docu Sprint  5  6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (NPMBUILD-3) magnolia-build copy module into resources folder including package.json

[on behalf of Tomáš Gregovský]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomáš Gregovský created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia light-module build tools /  NPMBUILD-3 
 
 
 
  magnolia-build copy module into resources folder including package.json  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Created:
 

 25/Jan/16 2:27 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Tomáš Gregovský 
 
 
 
 
 
 
 
 
 
 
magnolia-build copy module into resources folder including package.json that one is then visible in magnolia resources app... and simply shouldn't be copied. I guess similar for some kind on readme files, etc... maybe just folders should be? or something like ignore list in magnolia-build package.json?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (DOCU-649) Explain how to access a content app via REST api from client side

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-649 
 
 
 
  Explain how to access a content app via REST api from client side  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 

Assignee:
 
 Christoph Meier Antti Hietala 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLDEMO-139) Dialog broken for some travel-demo page templates since MTK

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-139 
 
 
 
  Dialog broken for some travel-demo page templates since MTK  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Assignee:
 
 Antonín Juran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3699) JcrNodeAdapter#getJcrItem do not return VersionedNode and VersionedChildNode wrapped.

[JIRA (on behalf of Evzen Fochr)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evzen Fochr reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3699 
 
 
 
  JcrNodeAdapter#getJcrItem do not return VersionedNode and VersionedChildNode wrapped.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evzen Fochr 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 In QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3132) Edit profile dialog: each language should be displayed in its own language, not in the current one

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3132 
 
 
 
  Edit profile dialog: each language should be displayed in its own language, not in the current one  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Fix Version/s:
 
 5.3.13 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 Backlog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3754) DefinitionCloner should not clone ComponentProvider and ResourceOrigin

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3754 
 
 
 
  DefinitionCloner should not clone ComponentProvider and ResourceOrigin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Sprint:
 
 Kromeriz 28 
 
 
 

Labels:
 
 selected-for-backlog 
 
 
 

Account:
 
 
 
 
 

Assignee:
 
 Roman Kovařík 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLFORM-275) Skip validation of empty non-mandatory field

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-275 
 
 
 
  Skip validation of empty non-mandatory field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3132) Edit profile dialog: each language should be displayed in its own language, not in the current one

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3132 
 
 
 
  Edit profile dialog: each language should be displayed in its own language, not in the current one  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Original Estimate:
 
 3d 
 
 
 

Remaining Estimate:
 
 3d 
 
 
 

Story Points:
 
 5 
 
 
 

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] (MGNLCE-21) Adjust integration + UI tests due to changes in install order of modules (stk/travel)

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-21 
 
 
 
  Adjust integration + UI tests due to changes in install order of modules (stk/travel)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 2 
 
 
 

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] (TASKMGMT-22) Newly created tasks may not be stored in proper date folder

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Task Management /  TASKMGMT-22 
 
 
 
  Newly created tasks may not be stored in proper date folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (LOGTOOLS-2) create a subApp for setting log levels

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-2 
 
 
 
  create a subApp for setting log levels  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (JCRTOOLS-20) New export function creates erroneous bootstrap

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-20 
 
 
 
  New export function creates erroneous bootstrap  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-10) Add UI tests for jcr-tools app

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-10 
 
 
 
  Add UI tests for jcr-tools app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (CFGUI-13) Relocate definitions app from forge to community

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Definitions app /  CFGUI-13 
 
 
 
  Relocate definitions app from forge to community  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLGROOVY-142) Refactor module to use Node API instead of deprecated Content API

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-142 
 
 
 
  Refactor module to use Node API instead of deprecated Content API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (JCRTOOLS-16) Allow to specify path on dumper subapp

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-16 
 
 
 
  Allow to specify path on dumper subapp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 2 3 
 
 
 

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-3727) Deleting a content node claims success on actual failure

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3727 
 
 
 
  Deleting a content node claims success on actual failure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Remaining Estimate:
 
 1m 1d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3679) CLONE - Page-editor: Notify users about broken page template, e.g. missing html head markup

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3679 
 
 
 
  CLONE - Page-editor: Notify users about broken page template, e.g. missing html head markup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Remaining Estimate:
 
 0d 0.5d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (JCRTOOLS-20) New export function creates erroneous bootstrap

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-20 
 
 
 
  New export function creates erroneous bootstrap  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3727) Deleting a content node claims success on actual failure

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3727 
 
 
 
  Deleting a content node claims success on actual failure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Remaining Estimate:
 
 0d 1m 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (LOGTOOLS-3) Create update task to remove old legacy logging-apps

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-3 
 
 
 
  Create update task to remove old legacy logging-apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 3 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (LOGTOOLS-3) Create update task to remove old legacy logging-apps

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-3 
 
 
 
  Create update task to remove old legacy logging-apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3754) DefinitionCloner should not clone ComponentProvider and ResourceOrigin

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3754 
 
 
 
  DefinitionCloner should not clone ComponentProvider and ResourceOrigin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 configuration, content app 
 
 
 

Created:
 

 25/Jan/16 9:51 AM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Roman Kovařík 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
For 

MGNLUI-3428
, we introduced info.magnolia.ui.contentapp.DefinitionCloner to workaround problems we found when cloning definitions. 
Really though, those definitions should never have been cloned in the first place. The use-case is to slightly "customize" a given configured definition and reuse it in a slightly different context (e.g reuse a workbench config in a choose dialog) 
Not only does this cause unnecessary complexity (e.g doesn't play well with 

[magnolia-dev] [JIRA] (MGNLUI-3754) DefinitionCloner should not clone ComponentProvider and ResourceOrigin

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3754 
 
 
 
  DefinitionCloner should not clone ComponentProvider and ResourceOrigin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 For MGNLUI-3428, we introduced {{info.magnolia.ui.contentapp.DefinitionCloner}} to workaround Currently causes  problems  we found when cloning definitions.Really though, those definitions should never have been cloned  in  the first place. The use  MAGNOLIA - case is to slightly "customize" a given configured definition and reuse it in a slightly different context (e.g reuse a workbench config in a choose dialog)Not only does this cause unnecessary complexity (e.g doesn't play well with proxies) 6234 ,  it's also just really unnecessary and unportable. Many usages explicitly cast to the {{Configured*}} implementation of their definition, to be able to call setter methods. This will thus obviously never work with any other implementation of the interfaces.Instead, we should introduce simple decorators for our definition _interfaces_. Let them delegate all getters to a delegatee. And in place of cloning, we could do something along  where TranslationService newly injects  these  lines:{code}diff --git a/magnolia-ui-contentapp/src/main/java/info/magnolia/ui/contentapp/movedialog/MoveDialogPresenterImpl  classes . java b/magnolia-ui-contentapp/src/main/java/info/magnolia/ui/contentapp/movedialog/MoveDialogPresenterImpl.javaindex f24d597..0ec973c 100644--- a/magnolia-ui-contentapp/src/main/java/info/magnolia/ui/contentapp/movedialog/MoveDialogPresenterImpl.java+++ b/magnolia-ui-contentapp/src/main/java/info/magnolia/ui/contentapp/movedialog/MoveDialogPresenterImpl.java@@ -222,13 +223,12 @@ public class MoveDialogPresenterImpl extends BaseDialogPresenter implements Move }  private ContentPresenterDefinition prepareTreePresenter(ContentPresenterDefinition treePresenter) {-ContentPresenterDefinition def = cloner.deepClone(treePresenter);-if (!def.getColumns().isEmpty()) {-ColumnDefinition column = def.getColumns().get(0);-def.getColumns().clear();-def.getColumns().add(column);-}-return def;+return new ContentPresenterDefinitionDecorator(treePresenter) {+@Override+public List getColumns() {+return Collections.singletonList(delegate().getColums().get(0));+}+}; }{code}(and of course using a non-anonymous class to do this would provide greater debuggability)This goes hand-in-hand with tasks related to "use interfaces everywhere" and "builders for definitions". 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLSITE-34) Harmonize SiteAwareTemplateAvailability

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-34 
 
 
 
  Harmonize SiteAwareTemplateAvailability  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3132) Edit profile dialog: each language should be displayed in its own language, not in the current one

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3132 
 
 
 
  Edit profile dialog: each language should be displayed in its own language, not in the current one  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Sprint:
 
 Saigon 28 
 
 
 

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-3679) CLONE - Page-editor: Notify users about broken page template, e.g. missing html head markup

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3679 
 
 
 
  CLONE - Page-editor: Notify users about broken page template, e.g. missing html head markup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-275) Skip validation of empty non-mandatory field

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-275 
 
 
 
  Skip validation of empty non-mandatory field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3752) In-line edited property is not always selected after saving changes

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3752 
 
 
 
  In-line edited property is not always selected after saving changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3752) In-line edited property is not always selected after saving changes

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3752 
 
 
 
  In-line edited property is not always selected after saving changes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 
 
 
 
 
 
 
 *Timebox: 1d* This should have been fixed by MGNLUI-3665, but I've just happened to stumble over a case with the just released 5.4.4 that shows that this isn't fully fixed yet.To reproduce:* Open the Configuration app.* If you double-click on a folder or _visible_ property to in-line edit it _without selecting it first_, the item is selected after saving the change. So well, so good.* But if I open "modules/google-analytics", then double click on "version", then change the name to "versions" _using in-line editing and without selecting it first_, the property is NOT selected after saving the changes.Acceptance criteria:* In the second case, the item should be both modified to "versions", but also be selected and visible (in view). All previously selected items should get deselected. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLACTIVATION-121) Prevent memory leak of temp files references at activation transporter

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-121 
 
 
 
  Prevent memory leak of temp files references at activation transporter   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-49) More sophisticated main page template

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-49 
 
 
 
  More sophisticated main page template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-63) Add PageTemplateDefinition to MTE

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-63 
 
 
 
  Add PageTemplateDefinition to MTE  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MTE-63) Add PageTemplateDefinition to MTE

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-63 
 
 
 
  Add PageTemplateDefinition to MTE  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3715) Only values for selected options should be saved when using SwitchableFieldDefinition

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3715 
 
 
 
  Only values for selected options should be saved when using SwitchableFieldDefinition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3587) New and clearer icons for nodes in trees

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3587 
 
 
 
  New and clearer icons for nodes in trees  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[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  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3727) Deleting a content node claims success on actual failure

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3727 
 
 
 
  Deleting a content node claims success on actual failure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (LOGTOOLS-3) Create update task to remove old legacy logging-apps

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-3 
 
 
 
  Create update task to remove old legacy logging-apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel  27  28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-10) Add UI tests for jcr-tools app

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-10 
 
 
 
  Add UI tests for jcr-tools app  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Reviewed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (LOGTOOLS-3) Create update task to remove old legacy logging-apps

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Log Tools /  LOGTOOLS-3 
 
 
 
  Create update task to remove old legacy logging-apps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-275) Skip validation of empty non-mandatory field

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-275 
 
 
 
  Skip validation of empty non-mandatory field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Assignee:
 
 Oanh Thai Hoang 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3636) Security App: Provide the possiblity to see what users are members of a certain group.

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3636 
 
 
 
  Security App: Provide the possiblity to see what users are members of a certain group.  
 
 
 
 
 
 
 
 
 

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] (MGNLFORM-275) Skip validation of empty non-mandatory field

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-275 
 
 
 
  Skip validation of empty non-mandatory field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Fix Version/s:
 
 2.3.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Labels:
 
 selenium  ui-tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Component/s:
 
 UI tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-22) Fix download for SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Fix download for SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Robert Šiška 
 
 
 

Created:
 

 25/Jan/16 11:40 AM 
 
 
 

Fix Versions:
 

 5.3.13 
 
 
 

Labels:
 

 selenium 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Mikaël Geljić 
 
 
 
 
 
 
 
 
 
 
Job magnolia-bundle_5.3.x-with-selenium_profile has a recurring failure on SeleniumProfileTestingUITest  
Download of the exported file doesn't seem to get started properly. 
It appeared when main was updated to 5.3.13-SNAPSHOT, so we had suspicion that it was related to change of content-types. Although state seems to be the same as on master, on this regard. 
For now, we decided to @Ignore that test, until further investigation here. 
Some more input: 
 

I could get that test to pass locally (jetty9 / upgraded selenium and FF)
 

I have a *fast* debug job, but no luck so far: ce-5.3.x-selenium-DEBUG-SeleniumProfileTestingUITest 

[magnolia-dev] [JIRA] (MGNLDEMO-139) Dialog broken for some travel-demo page templates since MTK

[on behalf of Antonín Juran]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonín Juran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-139 
 
 
 
  Dialog broken for some travel-demo page templates since MTK  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonín Juran 
 
 
 

Fix Version/s:
 
 0.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCE-22) Investigate download failure in SeleniumProfileTestingUITest

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-22 
 
 
 
  Investigate download failure in SeleniumProfileTestingUITest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Summary:
 
 Fix Investigate  download  for  failure in  SeleniumProfileTestingUITest 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-275) Skip validation of empty non-mandatory field

[JIRA (on behalf of Oanh Thai Hoang)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oanh Thai Hoang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Form Module /  MGNLFORM-275 
 
 
 
  Skip validation of empty non-mandatory field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oanh Thai Hoang 
 
 
 

Original Estimate:
 
 3d 
 
 
 

Remaining Estimate:
 
 3d 
 
 
 

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: