[MAGNOLIA-3529] magnolia.utf8.enabled=true -> AccessDeniedException when Activating Created: 26/Jan/11 Updated: 28/Jan/11 Resolved: 28/Jan/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Sven Damm | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When I set magnolia.utf8.enabled to true, I cannot activate anymore. What am I doing wrong? 2011-01-26 10:54:47,539 WARN info.magnolia.module.templating.RenderingFilter : Resource not found: [/tinext-magnolia-frisbee/twitter/images] |
| Comments |
| Comment by Zdenek Skodik [ 26/Jan/11 ] |
|
It's a known utf8 encoding bug which is fixed in ongoing Magnolia CMS 4.4.2 ( |
| Comment by Zdenek Skodik [ 28/Jan/11 ] |
|
I'm closing this since Magnolia CMS 4.4.2 was released already. |