Setting contentType filter's enabled data node to false makes AdminCentral
inaccessible
---------------------------------------------------------------------------------------
Key: MAGNOLIA-3325
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3325
Project: Magnolia
Issue Type: Bug
Components: core
Affects Versions: 4.3.7
Environment: Mac OS X, Java 1.6, Tomcat 6, MySQL, STK, Blossom, DMS,
PUR
Reporter: Matt Dertinger
Assignee: Philipp Bärfuss
Hi,
While trying to debug an AJAX request/response issue, we tried to disable the
{{contentType}} filter by setting {{config/server/filters/contentType/enabled}}
to {{false}}. After doing this, the markup for the Tomcat Server Error page
was displayed in the value column in AdminCentral, and we were unable to change
the value back to {{true}}. We tried to shut down and restart tomcat, but we
are unable to get to AdminCentral, the Tomcat 500 error page is displayed. We
did this on a local instance, so its not a production issue, but thought I
should report it. In addition, we were hoping there might be a workaround to
fix this issue without having to delete the repository on the local instance.
If you could provide one, it would be much appreciated.
Please let me know if you need any more information.
Thanks,
Matt
--
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]>
----------------------------------------------------------------
