Two things to check:1. Delete the jcrPauseInstallation folder if you see under /system/sling/installer/jcr2. Check for error in error.log when deploying your code.

You have to provide \n element to go to next line for output

Advice you to raise a daycare ticket with these logs and steps followed for upgrade

No, That's not the correct answer.umamaheswariy46147403​, I am not sure what you are trying to achieve, can you elaborate your use case ?

Can you check this particular config once, It should be checked

Did you followed these two documentations for package inclusion:-https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html https://github.com/Adobe-Marketing-Cloud/aem-core-wcm-components#include-core-components-as-subpackage-into-your-own-project-maven-build

Was this encrypted by the same publisher which is decrypting it?If you have multiple publish, make sure those are using same keys.

Your first URL goes towards selector implementation in AEM, Look at the complete guide here https://helpx.adobe.com/experience-manager/6-2/managing/using/seo-and-url-management.html

You properly would have to overlay this file  /libs/foundation/components/page/redirect.jsp or /libs/wcm/foundation/components/page/redirect.html and correct logic for your use case. Doesn't seems to be much of work.

It seems the issue with new coral resourceType, for now you can use /libs/cq/gui/components/common/tagspicker which works