How do I debug cq:dialog issues?

Avatar

Avatar
Springboard
Level 3
jkpanera
Level 3

Likes

18 likes

Total Posts

107 posts

Correct reply

2 solutions
Top badges earned
Springboard
Establish
Validate 10
Validate 1
Ignite 5
View profile

Avatar
Springboard
Level 3
jkpanera
Level 3

Likes

18 likes

Total Posts

107 posts

Correct reply

2 solutions
Top badges earned
Springboard
Establish
Validate 10
Validate 1
Ignite 5
View profile
jkpanera
Level 3

13-02-2020

Hi guys,

 

I have an issue where a cq:dialog is persisting the information correctly, but when the authoring page loads the information is not populated back into the dialog.

 

I can troubleshoot issues in my Java code using printlns and the debugger. I can troubleshoot issues in HTL by writing values into the HTML.

 

But how do I troubleshoot issues with the cq:dialog?

 

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 1
Level 2
Nadine_Hamzeh
Level 2

Likes

2 likes

Total Posts

6 posts

Correct reply

5 solutions
Top badges earned
Boost 1
Affirm 5
Affirm 3
Affirm 1
View profile

Avatar
Boost 1
Level 2
Nadine_Hamzeh
Level 2

Likes

2 likes

Total Posts

6 posts

Correct reply

5 solutions
Top badges earned
Boost 1
Affirm 5
Affirm 3
Affirm 1
View profile
Nadine_Hamzeh
Level 2

15-02-2020

Try upgrading your core components [1].  Make sure the version you're upgrading to is compatible with your AEM version.

 

[1] https://docs.adobe.com/content/help/en/experience-manager-core-components/using/versions.html

Answers (1)

Answers (1)

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

14-02-2020

Check if there are any errors in the browser console when loading the page

Also, check error.log for any errors

 

There might be some js errors causing the issue.