Level 2

Environment specific related to component dialog (wrong dialog been shown)

Forum|Forum|3 years ago
May 31, 2022
5 replies
2009 views

Hi,
We have a component /apps/xyz/components/content/general/list/list which has multiple versions say v1 to v3

the resourceSuperType on this node (/apps/xyz/components/content/general/list/list) points to the version say (xyz/components/content/general/list/v2/list). Suppose I change the value of this property to point to v3 version (xyz/components/content/general/list/v3/list).
In our DEV environment we can see dialog of v3 component, but same does not work in QA environment. In QA environment it is showing dialog of v2 component (enough though the resourceSuperType is pointing to v3 version).
This issue is only occurring in QA environment instead of showing v3 component dialog it still shows v2 component dialog (enough though we are pointing to v2 version).
Can this issue be related to some internal issue related to resouceSuperType or there are any other causes for this kind of environment specific issue.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

SantoshSai

Community Advisor

Hi @rohitk81560102

Is v3 component inheriting v2? If yes - I think the Sling Resource Merger is doing its job. In this case - try removing sling:resourceSuperType on v2 component to break the inheritance and check - this may give you the results you are seeking.

Regards,
Santosh

Santosh Sai

R

rohitk81560102Author

Level 2

No v3 is not inheriting v2. When we are changing the version on /apps/xyz/components/content/general/list/list to point to v3 , html/htl changes are visible while authoring but dialog and design dialog it is still showing that of the v2 component.

R

rohitk81560102Author

Level 2

Checked and debugged further ns.editables object is returning config of v2 component instead of giving details of v3 version of component

R

rohitk81560102Author

Level 2

Check further cq data-config property is being populated with configuration details from v2 version instead of v3 version causing the issue. Any suggestions on how to resolve the issue?