It was possible to migrate version history with CRX2[1]. I haven't tried importing it into AEM6 though![1] http://docs.adobe.com/docs/en/crx/2-3/deploying/upgrading.html#Exporting%20the%20Version%20History

Hi,there is a similar thread here[1]First your question about URL parameters, your analytics scripts will run in the browser and send any data to GA from there, so the request reaching the server should not be required. Unless you are doing some processing server side? There are two ways you can han...

If it is for analytics, then what product are you using for analytics? The suggestions above would be for caching vanity url's with arguments. The reason you would want to do this is I have seen cases where parameters were not cached, and a retailer had a big release/offer which brought down the ser...

Hi,vanity urls can be cached and as you say using ignoreurlparam would allow you to cache a url with parameters, so no reason why it can't. Best to test this to make sure it behaves as you want it to. What is your use case for doing this?Regards,Opkar

Hi,with the arguments at the end of the vanity url, this page would not be cached by dispatcher, is this intended? Would the page really need to be generated with each request.Regards,Opkar

Hi Mahesh,no problem I have been through a few posting and they all describe the same procedure[1], [2],[3]How long are you giving for AEM/MongoDB to initalise? What hardware are you using? From the articles, it appears even with a SSD, the initialisation can take over 5 minutes, with others report...

Hi Mahesh,you have to edit the start script and add your parameters [1]. After AEM installs, changes to the start script have to be done manually, you can find details on the start script here[2]Regards,Opkar[1] http://www.netcentric.biz/blog/2015/01/adobe-experience-manager-6-with-a-mongodb-setup.h...

Hi,according to [1] mongodb 3.5 is not supported, only 3.0 or 2.6. Contact daycare to find out when it will be supported.Regards,Opkar[1]https://docs.adobe.com/docs/en/aem/6-1/deploy/technical-requirements.html

Hi,In the past what we have done is to disable the design mode for content authors and define allowed components for each parsys in the template[1]. In this way, even though the component is in the sidekick(we removed all unnecessary components), it can't be added to the parsys. Regards,Opkar[1] htt...

Hi,this was raised recently, the question was answered here [1]. Please raise a daycare ticket for your issue.Regards,Opkar[1] http://stackoverflow.com/questions/31288476/vanity-urls-dispatcher-cache-invalidation-adobe-aem-cq