[MAGNOLIA-2046] Wrong filter configuration completely breaks Magnolia Created: 06/Feb/08 Updated: 02/Dec/13 Resolved: 06/Aug/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.5.4 |
| Fix Version/s: | 3.6.2, 3.6.3 |
| Type: | Task | Priority: | Critical |
| Reporter: | Vivian Steller | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
If you accidentally configure the filter chain wrongly in Magnolia you can easily break the complete instance and prevent it from starting up again. E.g. consider the following scenario: See the exception attached. |
| Comments |
| Comment by Magnolia International [ 07/Feb/08 ] |
|
This is also the case for i18nSupport ! |
| Comment by Jan Haderka [ 06/Aug/08 ] |
|
r17219 |