[
http://jira.magnolia-cms.com/browse/MGNLGROOVY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MGNLGROOVY-36:
-------------------------------------
Summary: Groovy rescue servlet does not work when config:/server is
gone (was: Groovy rescue servlet does not work anymore)
Description:
After installation as per
http://documentation.magnolia-cms.com/modules/groovy.html#RegistertheGroovyRescueServlet,
no matter what command is typed, one gets the response html printed _in_ the
console. (see screenshot)
To reproduce this, delete or rename {{config:/server}}, configure the rescue
servlet, and restart.
Using {{RescueSecuritySupport}} (for instance by setting the
{{info.magnolia.cms.security.SecuritySupport=info.magnolia.cms.security.RescueSecuritySupport}}
property) could help, if it wasn't for MAGNOLIA-3561.
To fix this issue, the rescue servlet could set this property or component
itself, so users don't have to modify their properties.
was:
After installation as per
http://documentation.magnolia-cms.com/modules/groovy.html#RegistertheGroovyRescueServlet,
no matter what command is typed, one gets the response html printed _in_ the
console. (see screenshot)
Note: to reproduce this, I reproduced a customer's problem, by deleting the
{{config:/server}} node, so this might be vaguely related.
> Groovy rescue servlet does not work when config:/server is gone
> ---------------------------------------------------------------
>
> Key: MGNLGROOVY-36
> URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-36
> Project: Magnolia Groovy Module
> Issue Type: Bug
> Components: console
> Affects Versions: 1.1.1
> Reporter: Grégory Joseph
> Assignee: Federico Grilli
> Fix For: 1.1.2
>
> Attachments: Screen shot 2011-02-23 at 14.33.45.png
>
>
> After installation as per
> http://documentation.magnolia-cms.com/modules/groovy.html#RegistertheGroovyRescueServlet,
> no matter what command is typed, one gets the response html printed _in_ the
> console. (see screenshot)
> To reproduce this, delete or rename {{config:/server}}, configure the rescue
> servlet, and restart.
> Using {{RescueSecuritySupport}} (for instance by setting the
> {{info.magnolia.cms.security.SecuritySupport=info.magnolia.cms.security.RescueSecuritySupport}}
> property) could help, if it wasn't for MAGNOLIA-3561.
> To fix this issue, the rescue servlet could set this property or component
> itself, so users don't have to modify their properties.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
