Why don't you use the component report for this use case ?You can customize this report to show only the page activation date which be added as a new column and may be show page path instead of the page link.  http://localhost:4502/etc/reports/compreport.htmlhttp://localhost:4502/crx/de/libs/cq/repo...

Create a new use function and pass the navigation link path to it. The function will return the active class name if the navigation link path is a substring of current page path otherwise it will return blank. Then you can use the active class name returned by the function on the respective navigati...

Did you add the caching rule for this URL in the dispatcher configuration file ?Please see the following doc -  https://docs.adobe.com/docs/en/dispatcher/disp-config.html#par_146_44_0010SPECIFYING THE DOCUMENTS TO CACHEThe /rules property controls which documents are cached according to the document...

I have made few tweaks in the code to output the markup as you desired. Please download the attached file and rename the extension to zip. Thanks,Kunal 

The default OOTB selection field does not store the label of the dropdown along with the value so I do no think you can get the label when you retrieve the value of the field from node.However, you can add the mapping of the label and value in the i18n data dictionary and use the dictionary to rende...

If you want to try this with SQL 2 then the following query should work- SELECT * FROM [cq:PageContent] AS parent INNER JOIN [nt:unstructured] AS child ON ISDESCENDANTNODE(child,parent) WHERE ISDESCENDANTNODE(parent,[FROM_WHICH_CONTENT_PATH]) AND child.[sling:resourceType]='COMPONENTPATH' AND parent...

For this use case you can use data-sly-include for recursive calls and set the request attributes(for limit and the current level) before making the nested call. And when you render the links just make sure to check the current level reached with the limit. Attached is the sample code which you can ...

Installing packages on new AEM instance is not the right upgrade path to follow. Any particular reason why you did not follow the recommended in-place upgrade  ?

We did see the same exception when we upgraded to 6.1 instance with lower case function.  We raised a support ticket with day care and it was acknowledged as a bug by the support team. As a workaround we had to use the SQL2 version of the query in our code on 6.1. 

Check the below blog post-http://www.wemblog.com/2013/03/how-to-cache-error-page-in-cq.html