-
Bug
-
Resolution: Fixed
-
Neutral
-
4.3.7
-
None
-
None
Target instance should be notified of the utf settings of the author so it can process content properly on activation or in the very least fail with more meaningful message the with permission check on non existent path. The problem occurs even when activating page that doesn't actually contain any special characters
Acceptance criteria
- is duplicated by
-
MGNLXAA-23 UTF-8 enabled encoding breaks activation process
- Closed
- is related to
-
MAGNOLIA-3490 Activation fails with utf8 support enabled on both author and public instances.
- Closed