Well, page activation is not a resource intensive task as it just queues the pages for activation in replication agent queue. Also, the cron job is going to run in the background as a separate thread and in my opinion is a simple solution to achieve this.  

Well I did not understand your question completely. But the run time boosting is indeed supported by jcr contains function - https://helpx.adobe.com/experience-manager/kb/BoostInSearch.html

It is not available as inbuilt feature in the reporting interface but you can manually export the data to a CSV or an excel file. Get the audit data of page activity report in the JSON format - http://localhost:4502/etc/reports/auditreport/jcr:content/report.data.jsonUse any free online tool to conv...

You can create a scheduled cron job to activate the pages programmatically (see code sample for activation shared by @Kautuksahni). You can define the number of pages to activate in one run as configuration property of the job. Below are some of the example of cron jobs - https://github.com/sneakybe...

You can set the boost property in the index configuration for properties which would you like to have higher search relevancy. See the Boost and Search relevancy documentation here - `https://jackrabbit.apache.org/oak/docs/query/lucene.html#boost 

I don't now why you are creating a separate user action for activating to SOLR.  Why don't you always send content to SOLR on activation ? For your use case, why don't you create a custom menu click handler in SiteAdmin.Actions.js file and call your custom business logic of sending the content to SO...

If the issue still exist in 6.1 then I would recommend you to raise a daycare ticket to get the hotfix for 6.1. I didn't see any 6.1 version hotfix for this issue available in package share. 

I would then remove all LIKE clauses and use asterisk (*) as wild card character in contain clauses like CONTAINS(s.[jcr:title],'DEF*'). This will return for DEF and DEFbb both. 

Hi Yash, You can refer the code sample shared by @shopsinm.The default CSRF JS adds the token field in the form when the form is loaded initially. The script intercepts the submission handler of the form and sets the token attribute again in the form with the refreshed value just before the form is ...

[1] Check the documentation of the contains function. By default the search terms separated by whitespace are ANDed together. For example if you fire the following query- SELECT * FROM [nt:base] AS s where contains(s.[jcr:title],'Geometrixx Outdoors') then you get results which have "Geometrixx Outd...