CODEWITHSUNDEEP
adobeaem
aneesh sharma
aneesh sharma

Reputation: 3

Adobe CQ: Make two <cq:include> with same path editable

I have two "cq:include" in same jsp with same path and I need to make both of them editable. But currently only one of them is editable.

If I change anything in one component that shows on second. But the second one itself is not editable. My requirement is to make both the components editable while keeping the include path same.

Code:

<cq:include path ="abc" resourceType="xyz"/>
<cq:include path ="abc" resourceType="xyz"/> # This one is not editable.

Upvotes: 0

Views: 1624

Answers (3)

Brenn
Brenn

Reputation: 1384

The way the authoring system works it hooks per location so if you want to have it authored in two different places those two different places should NOT be on the same page. This is just good usability as it can be very confusing.

INSTEAD, I suggest the first one on the page add an attribute to the slingRequest noting that it has been placed on the page and future instances with the same path put a message on the screen saying that it is edited elsewhere. Without knowing more details it's hard to suggest the best usability for this scenario.

Update: If you MUST do this, here is a work around.
Step 1: define a convention for naming 2 properties. e.g. realTitle (String) and realTitleLastUpdated (date/time). These will be page-level properties, making it easy to access and check them using pageProperties. Though you can do this through a subnode as well but that gets more complicated.

Step 2: For the components that must all be simulateously editable, allow them to create their own nodes. Then, on load in the EDIT environment, check the property realTitle and the lastUpdated time stored in realTitleLastUpdated

If the last edit of your component's title, e.g. jcr:lastModified is newer than realTitleLastUpdated, change the local value of title (e.g. jcr:title) to the value of the realTitle property and update the realTitleLastUpdated time to reflect the time in jcr:lastModified on your component.

If the opposite is true - realTitleLastUpdated is of a time newer than the last modification of the local component, then update the jcr:title of the component and the times to match.

Obviously if the last update times match, do nothing.

It's a bit of a run around, but this will keep everything in sync.

I realized that you may not realize that you probably need to save the state. I believe you can do this (among other ways) using resource.getResourceResolver().adaptTo(Session.class).save()

I've done this before but it's been a while. Let me know if you have issues, I'm working from memory.

Upvotes: 0

Ronnie
Ronnie

Reputation: 302

Well, if you don't want author to bother about editing both the components, then you should use javascript/jquery and onChange() of one of the component, modify the value of another component as well.

Upvotes: 0

rakhi4110
rakhi4110

Reputation: 9281

Having two components with the same resource type would create only a single node at the given path. Hence, any change you make in one of the component would be reflecting in both of them, as both the components would be reading from the same node.

This is also the reason for not being able to edit the second component. Try providing different paths for different components like shown below.

<cq:include path="abc" resourceType="xyz" />
<cq:include path="abc_0" resourceType="xyz" />

Similar questions have been asked here and here

Upvotes: 1

Related Questions