[magnolia-dev] [JIRA] (MGNLUI-3758) Remove usages of AbstractFieldFactory's deprecated constructor

[JIRA (on behalf of Hieu Nguyen Duc)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hieu Nguyen Duc updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3758 
 
 
 
  Remove usages of AbstractFieldFactory's deprecated constructor   
 
 
 
 
 
 
 
 
 

Change By:
 
 Hieu Nguyen Duc 
 
 
 

Assignee:
 
 Ngoc Nguyenthanh Hieu Nguyen Duc 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-39) Fix 500 error when running the crawler locally

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-39 
 
 
 
  Fix 500 error when running the crawler locally  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 500 error happens the first time this URL is reached, and then works fine.  That makes the build fail, though. {code:java}[ERROR] Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.5:execute (web-crawler) on project magnolia-integration-tests: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8399/magnoliaTest/.magnolia/jcrprop/?path=/modules/site/config/site/extends=/modules/travel-demo/config/travel -> [Help 1]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-39) Fix 500 error when running the crawler locally

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Community Edition /  MGNLCE-39 
 
 
 
  Fix 500 error when running the crawler locally  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5, 5.4.7 
 
 
 

Assignee:
 
 Robert Šiška 
 
 
 

Created:
 

 04/May/16 4:57 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
500 error happens the first time this URL is reached, and then works fine. 

 

[ERROR] Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.5:execute (web-crawler) on project magnolia-integration-tests: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8399/magnoliaTest/.magnolia/jcrprop/?path=/modules/site/config/site/extends=/modules/travel-demo/config/travel -> [Help 1]
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3875) Failing tests with Java 8

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3875 
 
 
 
  Failing tests with Java 8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 When doing mvn clean test using 1.8 javaVersion in pom.xml, the following occurs:{code:java}Results :Tests in error:  SelectFieldOptionDefinitionKeyGeneratorTest.testOptionsInSelectField:103 » IllegalArgument  SelectFieldOptionDefinitionKeyGeneratorTest.testOptionsInSwitchableField:143 » IllegalArgument{code} We should try to find a fix to that, otherwise get rid of the deprecated method use, as suggested by Espen. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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ć 
 
 
 

Sprint:
 
 Saigon 41 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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ć 
 
 
 

Sprint:
 
 Saigon 41 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-153) PageEditor looks broken because component edit bars go over the navigation

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-153 
 
 
 
  PageEditor looks broken because component edit bars go over the navigation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 0.12 
 
 
 

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-2695) User can configure his timezone

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Assignee:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLSITE-58) Site module duplicates workspace listener on every restart

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Site Module /  MGNLSITE-58 
 
 
 
  Site module duplicates workspace listener on every restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-140) Wrong dialog property for tourSportstation page

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-140 
 
 
 
  Wrong dialog property for tourSportstation page  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3157) If the label is too long, the i18n and required sign (*) disappears

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3157 
 
 
 
  If the label is too long, the i18n and required sign (*) disappears   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-132) Running groovy script should not block the UI

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Groovy Module /  MGNLGROOVY-132 
 
 
 
  Running groovy script should not block the UI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Fix Version/s:
 
 2.5 
 
 
 

Fix Version/s:
 
 2.4.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] (MGNLUI-3853) If the last subapp tab title is too long it is unclickable

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3853 
 
 
 
  If the last subapp tab title is too long it is unclickable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Kromeriz 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-80) searchfn.searchPages() is not taking into account subnodes (subcomponents or subareas)

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Templating Essentials /  MTE-80 
 
 
 
  searchfn.searchPages() is not taking into account subnodes (subcomponents or subareas)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3683) Make LinkField a pure-Vaadin field, move definition handling to factory

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3683 
 
 
 
  Make LinkField a pure-Vaadin field, move definition handling to factory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel Saigon  43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3875) Failing tests with Java 8

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3875 
 
 
 
  Failing tests with Java 8  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 04/May/16 3:06 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
When doing `mvn clean test` using 1.8 `javaVersion` in pom.xml, the following occurs: 

 

Results :

Tests in error:
  SelectFieldOptionDefinitionKeyGeneratorTest.testOptionsInSelectField:103 » IllegalArgument
  SelectFieldOptionDefinitionKeyGeneratorTest.testOptionsInSwitchableField:143 » IllegalArgument
 

 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3875) Failing tests with Java 8

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3875 
 
 
 
  Failing tests with Java 8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 When doing  ` mvn clean test `  using 1.8  ` javaVersion `  in pom.xml, the following occurs:{code:java}Results :Tests in error:  SelectFieldOptionDefinitionKeyGeneratorTest.testOptionsInSelectField:103 » IllegalArgument  SelectFieldOptionDefinitionKeyGeneratorTest.testOptionsInSwitchableField:143 » IllegalArgument{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3590) Make bulk actions configurable in the Pulse

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3590 
 
 
 
  Make bulk actions configurable in the Pulse  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel Saigon  43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




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

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

[on behalf of Mikaël Geljić]

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

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

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

 
 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-3846) Edit bars and actions are missing in IE11 on Windows 10.1

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3846 
 
 
 
  Edit bars and actions are missing in IE11 on Windows 10.1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3590) Make bulk actions configurable in the Pulse

[on behalf of Michael Mühlebach]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Mühlebach updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3590 
 
 
 
  Make bulk actions configurable in the Pulse  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Mühlebach 
 
 
 

Sprint:
 
 Basel 43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2542) Dynamic forms & cross-field validation

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2542 
 
 
 
  Dynamic forms & cross-field validation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

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-3537) Extending SwitchableField

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3537 
 
 
 
  Extending SwitchableField  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

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-3668) MultiValueFields must react on the changes of underlying datasource

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3668 
 
 
 
  MultiValueFields must react on the changes of underlying datasource  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

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-3624) CustomMultiField components can't display help text

[JIRA (on behalf of Jan Haderka)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jan Haderka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3624 
 
 
 
  CustomMultiField components can't display help text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jan Haderka 
 
 
 

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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Labels:
 
 support  to-specify 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice to see all dates and times in either the server time zone or in a time zone of his choice*. He specifies his preferences in the user settings dialog (see below).** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.|!My profile-Profile 1.png|thumbnail!|The first tab offers fields to enter data about a user and her account.||!My profile-Preferences 1.png|thumbnail!|The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter.|*To pick a timezone*, the user has the option to:* pick the timezone as currently configured and set on the server. The server's timezone is shown.* specify a timezone of her choice.The list of timezones should be comprehensive and include major cities. A minimum set could only offer relative settings (e.g. "GMT +1h", "GMT +2h" or "UST -5h"), although that's user friendly.h4. Wireframes for revealing timezone in listsIn the List and Tree view, I suggest we continue not showing any timezone independant of the user's preferences to avoid sacrifying space for repetitive, clear information. Instead, we can reveal timezone information in a tooltip, if a user hovers or tap on a date value.|!TZ in list 1.png|thumbnail!|No timezone information shown by default.||!TZ in list 2-user chosen.png|thumbnail!|The user-chosen timezone string is revealed in a tooltip.|| Col A1 !TZ in list 3-server time.png | thumbnail!| If the user has chosen to use the server timezone instead, we might want to show an additional label "\[server time\] | " to clarify that. I'm not sure that's needed, though.| 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 TZ in list 3-server time.png 
 
 
 

Attachment:
 
 TZ in list 2-user chosen.png 
 
 
 

Attachment:
 
 TZ in list 1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice to see all dates and times in either the server time zone or in a time zone of his choice*. He specifies his preferences in the user settings dialog (see below).** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.|!My profile-Profile 1.png|thumbnail!|The first tab offers fields to enter data about a user and her account.||!My profile-Preferences 1.png|thumbnail!|The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter.|*To pick a timezone*, the user has the option to:* pick the timezone as currently configured and set on the server. The server's timezone is shown.* specify a timezone of her choice.The list of timezones should be comprehensive and include major cities. A minimum set could only offer relative settings (e.g. "GMT +1h", "GMT +2h" or "UST -5h"), although that's user friendly.h4. Wireframes for revealing timezone in listsIn the List and Tree view, I suggest we continue not showing any timezone independant of the user's preferences to avoid sacrifying space for repetitive, clear information. Instead, we can reveal timezone information in a tooltip, if a user hovers or tap on a date value.| Col A1 !TZ in list 1.png | thumbnail!| No timezone information shown by default.|| Col A1 !TZ in list 2-user chosen.png | thumbnail!| The user-chosen timezone string is revealed in a tooltip.||Col A1|If the user has chosen to use the server timezone instead, we might want to show an additional label "\[server time\]|" to clarify that. I'm not sure that's needed, though.| 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice to see all dates and times in either the server time zone or in a time zone of his choice*. He specifies his preferences in the user settings dialog (see below).** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.|!My profile-Profile 1.png|thumbnail!|The first tab offers fields to enter data about a user and her account.||!My profile-Preferences 1.png|thumbnail!|The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter.|*To pick a timezone*, the user has the option to:* pick the timezone as currently configured and set on the server. The server's timezone is shown.* specify a timezone of her choice.The list of timezones should be comprehensive and include major cities. A minimum set could only offer relative settings (e.g. "GMT +1h", "GMT +2h" or "UST -5h"), although that's user friendly. h4. Wireframes for revealing timezone in listsIn the List and Tree view, I suggest we continue not showing any timezone independant of the user's preferences to avoid sacrifying space for repetitive, clear information. Instead, we can reveal timezone information in a tooltip, if a user hovers or tap on a date value.|Col A1|No timezone information shown by default.||Col A1|The user-chosen timezone string is revealed in a tooltip.||Col A1|If the user has chosen to use the server timezone instead, we might want to show an additional label "\[server time\]|" to clarify that. I'm not sure that's needed, though.| 
 
 
 
 
 
 
 
 
 
 
 
 

[magnolia-dev] [JIRA] (MGNLUI-3777) Streamline font fallbacks when webfont can't be loaded

[on behalf of Mikaël Geljić]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3777 
 
 
 
  Streamline font fallbacks when webfont can't be loaded  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Summary:
 
 Provide reasonable Streamline font  fallbacks when  default  webfont can't be loaded  by browser 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice to see all dates and times in either the server time zone or in a time zone of his choice*. He specifies his preferences in the user settings dialog (see below).** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.The first tab offers fields to enter data about a user and her account.!My profile-Profile 1.png|thumbnail!The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter.!My profile-Preferences 1.png|thumbnail! *To pick a timezone*, the user has the option to:* pick the timezone as currently configured and set on the server. The server's timezone is shown.* specify a timezone of her choice.The list of timezones should be comprehensive and include major cities. A minimum set could only offer relative settings (e.g. "GMT +1h", "GMT +2h" or "UST -5h"), although that's user friendly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice to see all dates and times in either the server time zone or in a time zone of his choice*. He specifies his preferences in the user settings dialog (see below).** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers. |!My profile-Profile 1.png|thumbnail!| The first tab offers fields to enter data about a user and her account. |  | !My profile- Profile Preferences  1.png|thumbnail!  | The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter. !My profile-Preferences 1.png | thumbnail! *To pick a timezone*, the user has the option to:* pick the timezone as currently configured and set on the server. The server's timezone is shown.* specify a timezone of her choice.The list of timezones should be comprehensive and include major cities. A minimum set could only offer relative settings (e.g. "GMT +1h", "GMT +2h" or "UST -5h"), although that's user friendly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice to see all dates and times in either the server time zone or in a time zone of his choice*. He specifies his preferences in the user settings dialog  (see below) .** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.The first tab offers fields to enter data about a user and her account.!My profile-Profile 1.png|thumbnail!The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter.!My profile-Preferences 1.png|thumbnail! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice *  to see all dates and times in either the server time zone or in a time zone of his choice * . He  picks that timezone  specifies his preferences  in the user settings  dialog .** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.The first tab offers fields to enter data about a user and her account.!My profile-Profile 1.png|thumbnail!The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter.!My profile-Preferences 1.png|thumbnail! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice* to see all dates and times in either the server time zone or in a time zone of his choice. He picks that timezone in the user settings.** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers.The first tab offers fields to enter data about a user and her account.!My profile-Profile 1.png|thumbnail!The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter. !My profile-Preferences 1.png|thumbnail! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 My profile-Preferences 1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 My profile-Settings 1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice* to see all dates and times in either the server time zone or in a time zone of his choice. He picks that timezone in the user settings.** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4. Wireframe for editing a user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers. The first tab offers fields to enter data about a user and her account.!My profile-Profile 1.png|thumbnail!The second tab allows a user to pick her preferences related to the language (used mostly by the UI, but could also be referenced elsewhere) and date and time. We'll add the timezone preferences to the latter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Attachment:
 
 My profile-Settings 1.png 
 
 
 

Attachment:
 
 My profile-Profile 1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice* to see all dates and times in either the server time zone or in a time zone of his choice. He picks that timezone in the user settings.** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings. h4. Edit user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this *concept for handling timezones*:* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice* to see all dates and times in either the server time zone or in a time zone of his choice. He picks that timezone in the user settings.** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings.h4.  Edit  Wireframe for editing a  user's profileWe need to *add a preference setting to pick the timezone* we want dates and times to appear in. While doing so, we also clean up the dialog and group all settings it offers. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this  *  concept  for handling timezones* :* Dates and times are *stored in a clearly defined timezone on the server*. There's a fallback timezone, in case that timezone is not set.* In AdminCentral, an *editor has the choice* to see all dates and times in either the server time zone or in a time zone of his choice. He picks that timezone in the user settings.** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice should be up to site developer/customer/partner*. He should have the possibility and no obstacles, to show dates and times:** in the timezone as they are stored on the server** in a hard-coded timezone defined for the site (e.g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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: 

[magnolia-dev] [JIRA] (MGNLUI-2695) User can configure his timezone

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-2695 
 
 
 
  User can configure his timezone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 User can configure How dates and times are shown in a UI depend on the context they are shown in.I suggest we follow this concept:* Dates and times are *stored in a clearly defined  timezone  on the server*. There's a fallback timezone,  in  case that timezone is not set.* In AdminCentral, an *editor has the choice* to see all dates and times in either the server time zone or in a time zone of  his  choice. He picks that timezone in the  user  profile  settings .  This ** In all *editorial or admin apps* such as Pages, Categories, Security, the timezone used is the one set by the user.** In all development or technical apps such as JCR tools, *whenever we show or dump raw data such as nodes* in the JCR config tree, the timezone used is the one of the server.* *On the actual website, the choice  should be  reflected in displayed dates  up to site developer/customer/partner*. He should have the possibility and no obstacles ,  see MGNLUI  to show dates and times:** in the timezone as they are stored on the server** in a hard - 2694 coded timezone defined for the site (e . g. a car hiring company in central europe hard codes the timezone to CET).** in the timezone guessed from the location a visitor surfs from or derived from browser settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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




For list details, see: 

[magnolia-dev] [JIRA] (MGNLDEMO-160) Separate i18n UI messages and template messages in Travel-Demo (and elsewhere?)

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-160 
 
 
 
  Separate i18n UI messages and template messages in Travel-Demo (and elsewhere?)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Project:
 
 Language Bundles Magnolia Demo Projects 
 
 
 

Key:
 
 LANG MGNLDEMO - 50 160 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3874) Firing ContentChangeEvent on the root node logs warning

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3874 
 
 
 
  Firing ContentChangeEvent on the root node logs warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Fix Version/s:
 
 5.4.7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3874) Firing ContentChangeEvent on the root node logs warning

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3874 
 
 
 
  Firing ContentChangeEvent on the root node logs warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 We can go to the next dialog when chaining dialogs and the related item doesn't have to be saved into JCR yet. This results into two problems:# The content change event is triggered after closing each dialog.# The tree is trying to select the item which doesn't exist yet. This results in a bug when adding a node at the root level since it tries to expand JCR root node (instead of the child which isn't saved yet) which is not part of the container. {code}  Found after integration of PAGES 2016 - 61 04-29 09:43:21,969 WARN  agnolia . ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNewNodeItemId@303012d2: javax.jcr.ItemNotFoundException: Root node doesn't have a parent{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3874) Firing ContentChangeEvent on the root node logs warning

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3874 
 
 
 
  Firing ContentChangeEvent on the root node logs warning  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Roman Kovařík 
 
 
 

Components:
 

 framework 
 
 
 

Created:
 

 04/May/16 8:17 AM 
 
 
 

Fix Versions:
 

 5.4.7 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Roman Kovařík 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
We can go to the next dialog when chaining dialogs and the related item doesn't have to be saved into JCR yet. This results into two problems: 
 

The content change event is triggered after closing each dialog.
 

The tree is trying to select the item which doesn't exist yet. This results in a bug when adding a node at the root level since it tries to expand JCR root node (instead of the child which isn't saved yet) which is not part of the container.
 

[magnolia-dev] [JIRA] (MGNLUI-3874) Firing ContentChangeEvent on the root node logs warning

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3874 
 
 
 
  Firing ContentChangeEvent on the root node logs warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

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-3874) Firing ContentChangeEvent on the root node logs warning

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3874 
 
 
 
  Firing ContentChangeEvent on the root node logs warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Sprint:
 
 Kromeriz 42 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-733) Add action to publish cameras and makers on the correspondent apps

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-733 
 
 
 
  Add action to publish cameras and makers on the correspondent apps  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Christoph Meier 
 
 
 

Created:
 

 04/May/16 8:08 AM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Christoph Meier 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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