[MAGNOLIA-3325] Setting contentType filter's enabled data node to false makes AdminCentral inaccessible Created: 16/Oct/10  Updated: 02/Dec/13  Resolved: 02/Dec/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.3.7
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Matt Dertinger Assignee: Philipp Bärfuss
Resolution: Won't Fix Votes: 0
Labels: configuration, filter
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X, Java 1.6, Tomcat 6, MySQL, STK, Blossom, DMS, PUR


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Visible to:
Addam Wassel, Yun Qian

 Description   

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



 Comments   
Comment by Jan Haderka [ 17/Oct/10 ]

Hi Matt,
unfortunately, not really true to its name, ContentTypeFilter does more then just setting the content type. Disabling it means there is no longer aggregation state in the context which as you have found out blows the AdminCentral.
To recover from this (and other similar problems) without having to delete your repo, please look at http://wiki.magnolia-cms.com/display/WIKI/How+to+repair+broken+configuration
or at http://wiki.magnolia-cms.com/display/WIKI/Groovy+Rescue+Servlet
Please note that the GroovyRescueServlet might not be usable if you have not installed Groovy module on your instance previously.

Comment by Matt Dertinger [ 18/Oct/10 ]

Jan,

Thank you for your help. GroovyRescueServlet is true to its name!

– Matt

Comment by Magnolia International [ 17/Dec/10 ]

Should we forbid this specific filter to be disabled ?

Generated at Mon Feb 12 03:45:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.