[magnolia-dev] [JIRA] (DOCU-673) Light development cans and can'ts

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-673 
 
 
 
  Light development cans and can'ts  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 content 
 
 
 

Created:
 

 10/Feb/16 3:05 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antti Hietala 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
List typical Magnolia project tasks and show which can and cannot be done with light development. 
The goal is to set the correct expectations. A developer should be able to make an educated decision whether light development is the right approach for them. Before you board the train you want to know how far it will go. 
Examples: 
 

Template definitions 
 

Template scripts 
 

Template models 
 

App definition 
 

[magnolia-dev] [JIRA] (DOCU-673) Light development cans and can'ts

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-673 
 
 
 
  Light development cans and can'ts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 List typical Magnolia project tasks and show which can and cannot be done with light development.The goal is to set the correct expectations. A developer should be able to make an educated decision whether light development is the right approach for them. Before you board the train you want to know how far it will go.Examples:* Template definitions (/)* Template scripts (/)* Template models (x)* App definition (/)* Register a workspace (x)* Register a node type (x)* Dialog definitions (/)* Configure subscribers (x)* Configure security (x)* Configure languages (x)* Create personalization traits (x)* Translate text (/)* etc...Light development is not just MTE + YAML. Light development is a modern development approach that doesn't require Java skills or even an IDE. You can't do everything but 80% is plenty. Beside the term  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3767) Use resources (fonts, images) from core module in defaultMagnoliaLoginForm

[JIRA (on behalf of Michal Novak)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Novak updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3767 
 
 
 
  Use resources (fonts, images) from core module in defaultMagnoliaLoginForm  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Novak 
 
 
 

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-3767) Use resources (fonts, images) from core module in defaultMagnoliaLoginForm

[JIRA (on behalf of Michal Novak)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Novak created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3767 
 
 
 
  Use resources (fonts, images) from core module in defaultMagnoliaLoginForm  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Michal Novak 
 
 
 

Created:
 

 10/Feb/16 3:58 PM 
 
 
 

Fix Versions:
 

 5.5 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Michal Novak 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[magnolia-dev] [JIRA] (MGNLCACHE-128) EhCacheWrapper does not catch LockTimeOutException properly

[JIRA (on behalf of Rico Jansen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rico Jansen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-128 
 
 
 
  EhCacheWrapper does not catch LockTimeOutException properly  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 cache core 
 
 
 

Created:
 

 10/Feb/16 3:59 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Rico Jansen 
 
 
 
 
 
 
 
 
 
 
I am seeing exceptions in our monitoring system (New Relic) with regards to LockTimeOutExceptions generating error 500 pages. These are caused by pages being rendered too slow (our problem).  However I do not see those errors in the magnolia log, which I would expect. Some investigation turns up that info.magnolia.module.cache.filter.CacheFilter#doFilter catches a info.magnolia.module.cache.exception.MgnlLockTimeoutException and logs a warning in that case. 
The code that is supposed to throw that exception in info.magnolia.module.cache.ehcache.EhCacheWrapper#get is faulty.  The get() call on ehcache is outside of the try/catch instead of in it. The code inside the try/catch is just returning the result object and will never throw a LockTimeoutException. 
This means the MgnlLockTimeoutException will never be thrown. Therefore there will be no magnolia log messages. 
 
 
 
 
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3764) I18n Key generators should be consistent

[on behalf of Roman Kovařík]

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

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3764 
 
 
 
  I18n Key generators should be consistent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Documentation update required:
 
 Yes 
 
 
 

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] (MGNLCACHE-128) EhCacheWrapper does not catch LockTimeOutException properly

[JIRA (on behalf of Rico Jansen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rico Jansen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-128 
 
 
 
  EhCacheWrapper does not catch LockTimeOutException properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rico Jansen 
 
 
 
 
 
 
 
 
 
 I am seeing exceptions in our monitoring system (New Relic) with regards to LockTimeOutExceptions generating error 500 pages. These are caused by pages being rendered too slow (our problem).   However I do not see those errors in the magnolia log, which I would expect.  Some investigation turns up that {{info.magnolia.module.cache.filter.CacheFilter#doFilter}} catches a {{info.magnolia.module.cache.exception.MgnlLockTimeoutException}} and logs a warning in that case.The code that is supposed to throw that exception in {{info.magnolia.module.cache.ehcache.EhCacheWrapper#get}} is faulty. The {{get()}} call on ehcache is outside of the try/catch instead of in it.The code inside the try/catch is just returning the result object and will never throw a LockTimeoutException.This means the MgnlLockTimeoutException will never be thrown.Therefore there will be no magnolia log messages. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLCACHE-128) EhCacheWrapper does not catch LockTimeOutException properly

[JIRA (on behalf of Rico Jansen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rico Jansen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Cache Module /  MGNLCACHE-128 
 
 
 
  EhCacheWrapper does not catch LockTimeOutException properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rico Jansen 
 
 
 

Visible to:
 
 Mathijn Elhorst, Michiel Meeuwissen, Nils Breunese 
 
 
 

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] (DOCU-673) Light development cans and can'ts

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-673 
 
 
 
  Light development cans and can'ts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 List typical Magnolia project tasks and show which can and cannot be done with light development.The goal is to set the correct expectations. A developer should be able to make an educated decision whether light development is the right approach for them. Before you board the train you want to know how far it will go.Examples:* Template definitions (/)* Template scripts (/)* Template models (x)*  Dialog definitions (/) *  App definition (/)*  Register a workspace  Module descriptor  (x)* *  Register a  workspace ** Register a  node type  (x)    *  Dialog definitions (/) * Module class *  Configure subscribers (x) * Module version handler *  Configure security (x) * etc. *  Configure languages  i18n  (x)* Create personalization traits (x)*  Translate text (/)*  etc...Light development is not just MTE + YAML. Light development is a modern development approach that doesn't require Java skills or even an IDE. You can't do everything but 80% is plenty.Beside the term    Light development we also should have a section (or even a page?) explaining {{Light module}} clearly explaining its _cans and can'ts_ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22) Move applauncher from group "Dev" to "Tool"

[JIRA (on behalf of Bradley Andersen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bradley Andersen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-22 
 
 
 
  Move applauncher from group "Dev" to "Tool"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bradley Andersen 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Basel 30 
 
 
 

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] (JCRTOOLS-22) Move applauncher from group "Dev" to "Tool"

[JIRA (on behalf of Bradley Andersen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bradley Andersen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-22 
 
 
 
  Move applauncher from group "Dev" to "Tool"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bradley Andersen 
 
 
 

Labels:
 
 selected-for-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] (JCRTOOLS-22) Move applauncher from group "Dev" to "Tool"

[JIRA (on behalf of Bradley Andersen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bradley Andersen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-22 
 
 
 
  Move applauncher from group "Dev" to "Tool"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bradley Andersen 
 
 
 

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] (JCRTOOLS-22) Move applauncher from group "Dev" to "Tool"

[JIRA (on behalf of Bradley Andersen)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bradley Andersen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jcr Tools /  JCRTOOLS-22 
 
 
 
  Move applauncher from group "Dev" to "Tool"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bradley Andersen 
 
 
 

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] (NPMBUILD-6) Error when publishing item in content app

[JIRA (on behalf of Sara Garcia)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sara Garcia created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia light-module build tools /  NPMBUILD-6 
 
 
 
  Error when publishing item in content app  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Support Request 
 
 
 

Assignee:
 
 Espen Jervidalo 
 
 
 

Attachments:
 

 Screen Shot 2016-02-10 at 09.38.14.png 
 
 
 

Created:
 

 10/Feb/16 10:56 AM 
 
 
 

Environment:
 

 OSX Yosemite, Magnolia Enterprise 5.4.4 
 
 
 

Labels:
 

 content-app workspace 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Sara Garcia 
 
 
 
 
 
 
 
 
 
 
 
I've created a content app "articles", running the groovy "createAppScrip", I've given anonymous and rest user access to it, and run the REST get node tool. 
Everything seems to be working fine but when I try publishing an article I get this error below: 
"error detected: Message received from subscriber: No repository known for logical workspace name articles on magnoliaPublic8080" 
 
 
 
 
   

[magnolia-dev] [JIRA] (MGNLDEMO-144) Make the w3 validation proof: Mainly the earch result page.

[JIRA (on behalf of Christian Ringele)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Ringele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Demo Projects /  MGNLDEMO-144 
 
 
 
  Make the w3 validation proof: Mainly the earch result page.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christian Ringele 
 
 
 

Support Score:
 
 
 
 
 

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: