[MAGNOLIA-2794] Register some sort of RecoveryFilter for when the filter chain is not correctly configured Created: 17/Jun/09 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
Currently, if no filter chain is available, we end up with ugly NPEs. If the /server/filters node is not available at all, we could for instance instanciate rootFilter as some sort of filter that lets Magnolia start and give the user a chance to fix the installation. Another issue is that activation is obviously broken if the filter configuration is broken. The following scenario needs to be taken into account:
TODO - there are related issues, link and/or fix them ! |
| Comments |
| Comment by Jan Haderka [ 04/Dec/13 ] |
|
while technically not possible, this should be switchable, otherwise you might end up with this emergency measure becoming accessible on public instance that comes up automatically while recovering from some disaster in data centre giving access to the instance to just about anyone, so probably you would keep it switched off on production environment, enabling the option only in case you actually screwed up some config change. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |