[MAGNOLIA-3652] Reactivation of node with | in name fails Created: 13/Apr/11 Updated: 27/Jul/11 Resolved: 25/Jul/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 4.4.2 |
| Fix Version/s: | 4.4.5 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Zdenek Skodik | 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 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
|
||||
| Description |
|
Usage of the vertical line, a standard ASCII character, in node names was allowed by magnolia.utf8.enabled=true. First activation attempt of such node is successful, on the second attempt it fails with NPE (attached) that it can't resolve the source at Author (the destination at Public was resolved properly during the process of removing all existing properties). So apparently an issue of en/decoding. The workaround is to get rid of the content in question for Public (either delete it directly or deactivate (!) from Author) and reactivate. |