Change rootPath of the pathbrowser depending on the context where the component is added

[Peter_Puzanovs]

Have requirement: when component with pathfield in the dialog is dropped on site A, the pathfield rootPath should become /path/to/site/A

When the same component is dropped on site B, the pathfield rootPath should become /path/to/site/B

How would one achieve this in AEM with minimalistic amount of changes?

Regards,

Peter

[Nupur_Jain]

Hi,

Is it Touch UI dialog or classic UI?

[Peter_Puzanovs]

Good question, sorry should have mentioned it before,

Touch UI AEM 6.3

[lasling]

I don't believe there is a clean code solution to this simply because of what the UI outputs for the data attributes.

What may be a better idea to consider is overlay your current component with a new one and only change the dialog.  This way you can give the component a different group and a different root path very cleanly.  On site A you allow component 1, on site B you allow component 2.  Simple and clean.

[Peter_Puzanovs]

Thank you for your reply,

Problem is that we promote re-use of the same component across quite a lot of sites. Now, having to overlay components does not feel like a clean/right solution to this problem.

Regards,

Peter

[lasling · Accepted solution]

I totally understand your hesitation with it, and if it was more than just overlaying the dialog I would agree it's probably not a good approach, but the view/business logic stays the same between components.  You're either going to have to maintain JavaScript to customize, or use OOTB functionality to overlay only the dialog. 

[lasling]

I found some posts on doing this in Classic UI, but nothing in Touch UI

CQ Dialog - Generate dynamic rootPath with ExtJS Plugin | 6D Labs

extjs - How to configure a rootPath in CQ Dialog depending on current page - Stack Overflow

[viveksachdeva]

You can take a look at my comment on this Re: How to add multiple rootPath in Coral 3 Pathfield