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

Resource Type property not saving

Avatar

Avatar
Validate 10
Level 3
Manikumar
Level 3

Likes

15 likes

Total Posts

110 posts

Correct Reply

8 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 3
Manikumar
Level 3

Likes

15 likes

Total Posts

110 posts

Correct Reply

8 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
Manikumar
Level 3

13-10-2016

Hi All,

I am facing an issue with classic components which are used in touch UI framework that are included as <cq:include path="articleintro" resourceType="/apps/intel/commons/components/content/articleintro"/>

but when i am trying to edit the component and save it sling:resourceType property is not saving for that include component.

Whereas for the same component in classic UI i am able to see that property as saved.

Could you please help me understand why and where exactly this POST request for the dialog are formed and saving

 

THanks,

Mani Kumar K

Replies

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,127 likes

Total Posts

6,121 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,127 likes

Total Posts

6,121 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

14-10-2016

Can you please provide me steps to reproduce it, so that we can help you.

For how dialog saves data, please refer to this post:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

//When you submit a dialog, data in all the fields will be sent a post request to aem default servlet and from there it will be stored in nodes. This is very similar to the way a web form works, values in all the fields will be sent to the path specified in actions. 

When you open dialog, get request will be made to the current node all properties are fetched and shown on dialog.

You can see those request when you look into browser network tabs

~kautuk

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,406 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,406 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

14-10-2016

The best practice for a component is to have 2 dialog JCR branches. One for Touch Ui and the other for classic. See this article as an example: https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html.

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

582 likes

Total Posts

564 posts

Correct Reply

218 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

582 likes

Total Posts

564 posts

Correct Reply

218 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

11-03-2020

@Manikumar,

I was able to replicate your problem.

In detail, I will repeat your problem, so that the next reader understands a clearer picture.

What's Happening?

Within the Touch UI page editor, A Classic UI component, component-a, is added to the page. The component-a has a  "cq:include"  to incclude another component, component-b, to the page. Component-b is also only Classic UI. The author was able to configure component-b with Classic UI in the Touch UI page editor. All the properties configured on component-b was saved as expected (confirmed in CRX/DE) except for the sling:resourceType property. The sling:resourceType property was not saved. However, in the Classic UI page editor, the component-b is saving as expected. 

Why is the sling:resourceType not saved?

When dealing with the Touch UI page editor, I've noticed that whenever a component is included into a page via JSP or Sightly, if the component included only has Classic UI, then the problem will persist with sling:resourceType as not being saved. The included component must have Touch UI enabled.

Take Aways:

  • Touch UI Page Editor with a component that includes another component with only Classic UI enabled, the sling:resourceType does not save.
  • Touch UI Page Editor with a component that includes another component with Touch UI enabled, the sling:resourceType will be saved.
  • Classic UI Page Editor with a component that includes another component with only Classic UI enabled, the sling:resourceType will be saved. 

I hope this helps.

  •