@hptarora,Is your this your own custom basic search component? 

@MikolajBudaSii,Can you show us the location off the script, please? Provide the JCR path.

Your dispatcher.any configuration looks correct. The best way to pinpoint the underlying cause of this issue will be to debug this. Enable your Apache web server and dispatcher logs, try the configurations below. At the same time, in your AEM development environment tail /crx-quickstart/logs/error.l...

Just make sure you press on the "BUILD" button and not "INSTALL" on prod 

@SupportMember,I had a similar issue like this in the past with my personal project. The problem here is that you have multiple cached directories for http://localhost:4503/us/en. When you check your cached directories, you may the long path, /content/we-retail/us/ca/* AND (possibly) /us/ca/*.Your c...

Of course it does not work. You will need to create this custom servlet which will return in response a JSON with data-score and data-team... however, a second thought, your JavaScript should be able to access the Document Object Model, so you should be able to call something like document.getElemen...

@s1101v,Building your own custom one, I suggest you reverse engineer the ACS Redirect Manager, understand why did they decide to design this redirect manage. Then execute your own. (you should also try to set it up on your local publisher + dispatcher, see how it works).I think their ACS Redirect Ma...

The out of the box should be working as expected.

Which AEM instance version are you using?

@AEMnewbie,There are 2 tactics that I see that are common while validating Touch UI dialogues in AEM; a front-end way and a back-end way. I prefer the front-end way, as logic in the front-end will highlight the input field that is not valid, and also not allow the content authors to save the dialogu...