AEM 6.5.6 (upgrading from 6.5.3) can't save component dialog

extwebd96701854

09-10-2020

Hi guys,

 

I was troubleshooting an issue after upgrading to 6.5.6 from 6.5.3 and still can't figure out why so though I would ask for your help to see if someone is also experienced the issue and got a workaround or so.

 

Background:

- Issue happen after I upgrade AEM to 6.5.6 from 6.5.3

- ACS common version is 4.0.0

- Core component version is 2.8.0

 

Issue:

- When saving any component dialog (even the default one by we-retail), the value didn't get save into the page jcr:content node but it get created in /libs/cq/gui/content/editor/content, 

 

for example, if i modify this page /editor.html/content/we-retail/us/en/experience.html

then instead it saved to /content/we-retail/us/en/experience/jcr:content/...

actually it got created in /libs/cq/gui/content/editor/content/we-retail/us/en/experience

 

as a result, when open the dialog again on the page, it will show no new value.

 

What i noticed, when submitting the dialog, the POST request make to aem are different between fail and success case.

E.g

 

Wrong case:

request URL is posting to http://localhost:4602/editor.html/content/we-retail/us/en/experience.html

(the page itself which is incorrect)

 

Correct case:

request URL should posting to 

http://localhost:4602/content/we-retail/us/en/experience/_jcr_content/root/responsivegrid/text 

 

 

I got no error in error.log.

 

Any advise would be much appreciated.

 

Accepted Solutions (1)

Accepted Solutions (1)

TUmesh

12-10-2020

Hi @extwebd96701854,

It is not clear that this issue is only specific to your project or we-retail or both.

If it is only specific to your project then, first check the browser console if there is an error if yes then what is that.

As per adobe it is not recommended to use granite and coral ui in the same dialog, I have seen lots of the people make this mistake, it also causes the similar kind of issue ,that you have mentioned.

have a look of the release doc for the service pack ,that you have used to upgrade your instance, if any thing mentioned for the same.

 

Hope this will help.

Regards

Umesh Thakur