Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

_charset_ is not set in request when closing dialog in Classic UI

Avatar

Avatar
Level 1
jozefp
Level 1

Likes

0 likes

Total Posts

8 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
jozefp
Level 1

Likes

0 likes

Total Posts

8 posts

Correct Reply

0 solutions
View profile
jozefp
Level 1

14-02-2017

Hello everyone,

On our project we came to obstacle with encoding problem.

We have AEM 6.2, but we are using Classic UI for page authoring. On every component, we have dialog with fieldEditLockMode set to TRUE.

When I unlock specific property, and I enter characters such as ľ š č ..... they are saved to node broken as seen on second picture.

We have found, that on closing dialog window, there is post request to server. If whole component is unlocked, perameters have every field inside, with _charset_ included, so this mistake does not occurs.

If we unlock only one property, _charset_ is not send in request and encoding is broken.

Also we set Default Parameter Encoding inside Apache Sling Request Parameter Handling configuration to UTF-8

 

Can anyone help us?

Thanks

View Entire Topic

Avatar

Avatar
Validate 25
Level 4
Kkkrish
Level 4

Likes

27 likes

Total Posts

107 posts

Correct Reply

1 solution
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile

Avatar
Validate 25
Level 4
Kkkrish
Level 4

Likes

27 likes

Total Posts

107 posts

Correct Reply

1 solution
Top badges earned
Validate 25
Validate 10
Validate 1
Boost 5
Boost 3
View profile
Kkkrish
Level 4

14-02-2017

Jozef Pa wrote...

Hello,

thanks for reply.

We are entering language specific characters, which should work anyways.

I have also tried turning off every filter, when request was called. It does not help.

One thing that would help us at this point is sending parameters along one unlocked property.

I don't think that was caused by our custom component, since I have created my own small component only with <form> that saves directly to JCR node and characters are still broken. When i add _charset_ it works. Isn't there another setting in AEM to set encoding?

 

Thanks for help

 

have a look at this post may be help you.