May 10, 2020
Estimated Post Reading Time ~

TouchUI Page Properties encoding issue with AEM 6.2 CFP3

While implementing a new website based on AEM 6.2 CFP3 for a customer, we faced the following problem:

When editing page properties right from “Sites” > “View Properties”, the encoding of special characters got lost/wrong. When editing the same page from via “Edit” > “Page Properties”, everything worked well.

This resulted in corrupt data:

The reason for this problem: In the “View Properties” dialog, the _charset_ property is missing which is required by AEM to determine the proper encoding of the submitted form data.

There is an easy fix for this:

By adding a hidden field named “_charset_” to the page properties dialog with the value “utf-8”, the problem is solved:

<charset
  jcr:primaryType="nt:unstructured"
  sling:resourceType="granite/ui/components/foundation/form/hidden"
  cq-msm-lockable="_charset_"
  ignoreData="{Boolean}true"
  fieldLabel="Charset"
  name="_charset_"
  value="utf-8"/>


By aem4beginner

No comments:

Post a Comment

If you have any doubts or questions, please let us know.