Hi Shehjad,I faced a similar problem,  it is resolved by setting the correct JDK version / JAVA_HOME.  the AEM 6.x version needs a minimum of Java 8 in its environment/path.Please set those and the SIGHTLY issue should be resolved. thanksVenkat

                I would like to customize start/end of OOTB CQ5 user form component to start with certain custom components pre-populated when the 'form' component is drag/dropped on to the page. I currently have an over-laid /apps/foundation/components/form elements with start/end/actions customize...

regarding the note: the observed behaviour is that for every <cq:includeClientLib>  the code checks if CQURLInfo is output, if not that include will output it. So, if enter the JS above in end of page the CQURLInfo might already have been printout out.

@edubey :Thanks for the response !Would appreciate it , if you could please list the said parts of CQ that use the data of CQURLInfo.  So that based on functionality we are using / not,  we could decide whether to empty it or not.

The daycare support folks came back saying that it is not possible to turn off the CQURLInfo in 5.5.Now, how are the developers supposed to use the <cq:includeClientLib ..>  tag, if there is no protection from XSS attacks ?I was expecting like a hotfix to turn this feature off.   If anyone has a bet...

   Hi, We are developing a new set of templates off the foundation page components. On the view source we see the CQURLInfo object print a set of URL related info as is obtained from the input URL.This opens it for XSS attacks.  We would like to turn it off. I believe there is a config option in 5.6...

Hi, I have been trying to upgrade CQ 5.5 to AEM 6.1 in place using the steps in http://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html#par_title_1963308877I step 4 ,  migration from CRX2 to OAK completes successfully,  however when I start the service with the following command  java -jar aem-qui...

@Sham, There have not been any replication issues it the current CQ 5.5 instance after the upgrade from 5.4.Also, above error on "crx:replicate" being already present is not the same as the issue mentioned in the helpx link you have given.The AEM6.1 migration seems to want to write a newer privilege...

I am facing an issue when upgrading from CQ5.5 to AEM 6.1 . I have already deleted the index files and am able to regenerate them when I run the migrate command . java -Xmx4096m -XX:MaxPermSize=2048M -jar aem-quickstart-6.1.0.jar -v -x crx2oak -xargs -- -o migrate However, I see the following error ...

I am facing a similar issue when upgrading from CQ5.5 to AEM 6.1 . I have already deleted the index files and am able to regenerate them when I run the migrate command . java -Xmx4096m -XX:MaxPermSize=2048M -jar aem-quickstart-6.1.0.jar -v -x crx2oak -xargs -- -o migrate However, I see the following...