Have you tried recompiling the JSPs? - http://localhost:4502/system/console/slingjsp 

In CQ 5.x you can rebuild indexes but for that you will have to shut down the instance and restart it. And for big repositories the rebuilding time can be many hours and sometimes it may go beyond a day. In such a scenario, you should optimize your indexing configuration in such a way to index only ...

The CRX repository of CQ 5.4 has multiple workspaces for versioned nodes and regular content nodes. And for each workspace you will see Lucene indexes created in different locations. Check the below link[1] to see the list of indexes and which is what. [1] http://www.wemblog.com/2011/09/which-index-...

Could you please share the component node structure in CRX ? 

Thanks JK. The OAK issue link was really very helpful. The problem was in the cq-social-commons-pkg-1.5.151.zip package. There was one workflow model xml in the package which was having hardcoded jcr:uuid value. I removed that jcr:uuid manually from the XML and reinstalled the package successfully. ...

Followed the upgrade instructions provided here - https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html#par_title_1690331669. We are upgrading from v1.3 and the exception is thrown if we install 1.7 package - cq-socialcommunities-pkg-1.7.197.zip

Hi, We did an inplace upgrade on existing 5.6.1 author instance to 6.1.  We followed all the steps as mentioned in the instructions, however we saw that during the upgrade few of the Adobe social communites package were not installed. And then when the upgrade was finished we checked that many OSGI ...

Adobe consulting team have shared this tool http://adobe-consulting-services.github.io/acs-aem-commons/features/query-packager.html which allows you to create packages based on the filters which are queried dynamically.  You can use this tool with SQL2/XPATH query which queries only the modified con...

Check this example here - https://helpx.adobe.com/experience-manager/using/creating-link-rewrite.html. You need to implement your logic in startElement() method. 

You can configure dispatcher to ignore query params in this case. See "IGNORING URL PARAMETERS" section in the following documentation-  https://docs.adobe.com/docs/en/dispatcher/disp-config.html