Hi @SantoshSai  nothing but childresource helped. Adapting to resource itself .. I see many use it online the same way. I can’t seem to understand why it worked in 6.2 and not in 6.5.12 and now wondering if @childresource with adapting to resource is the right way to go although it works for me also...

@SantoshSai That did not work , the @Deleted Account, it points to the node that holds a resource type A. The component's HTML with resource type A invokes the model with @childresource and it seemed to work , without adapting to SlingHttpServletRequest. Are we sure we compulsorily need to adapt to ...

Trying with @Inject@Optional@ChildResource(name = "multi")public Resource multi; Weird this worked on 64 and fails on 6.5.12. Will update if i succeed , this will avert the boolean check as well@SantoshSai 

@SantoshSai Those paths are set in the dialog and no manipulation is done to the paths. The multi as in the original thread is referring to the root node or the multi node based on scenarios mentioned above [A] and [B]Below code is exactly that returns the root node if multi is not available or mult...

I have a workaround , testing if the node multi is with a name "multi" and passing the boolean to the html class from model,   but not super happy about it, what would you like me to test @SantoshSai 

Hi @SantoshSai , thanks for the input, it did not help. I hadn't tried it per say until you brought it out but in vain@SlingObject@Optional

All, On 64 the below logic resolved to the node multi n case of [A] or it returned empty in case of [B] but on 65 , this returns the parent node[B] if node multi is not found else it returns as in [A] that is expected. Tried @Named but didn't help. Please let me know if i am missing something  I wan...

In case it helps someone. After trial and errors, Our pipeline needed checkin of conf.modules.d.Without conf.modules.d, we ended up with issues where the service wasn't loading, no MPM Loaded error or so.Ensure the sym links are established. We ended up checking in conf, conf.d, conf.dispatcher.dVal...

@DEBAL_DAS @Deleted Account  tried renaming and it did not work, infact knocking off the nodes did not help either. We had an in place upgrade not sure if that is the cause. Moving to lower version is a challenge at the moment. But glad to know that this is an issue and i can concur. I would most li...

Hi @DEBAL_DAS Thank you for your help with this.As mentioned this is not a problem on local instance as many have noted but on higher env .Please find the links shared for more details. Assumed Rewriter is the culprit, but that solved the issue momentarily. Attached logs