Looks like you have migrated the content with CRX2OAK with versioning flag to false. I was running into the same issue, you can create a groovy script that removes the mix:versionable (this will remove the jcr:baseVersion ), after saving add again the mix:versionable  value.

You can simply do http://localhost:4502/etc/tags/geometrixx.4.json (in JSON) or http://localhost:4502/etc/tags/geometrixx.feed.xml in XML feedAfter, there are many converters online to transform XML/JSON to CSV

Hello Everyone,My name is Adolfo, I'm AEM/CQ5 Technical Consultant for almost 6 years and almost 16 as a developer in many web technologies.Glad to be here and excited to learn new things.ThanksAdolfo

AEM 6.1 SP2 resolve the issue by updating  /etc/clientlibs/granite/jquery/granite/csrf/source/csrf.js  Thanks Adolfo

Hi Scott! I found that my installation script uses the old AEM 6.1 startup file and I was starting AEM 6.2 with that! I replaced and restarted and now the SP1 installation goes well!Sorry for that!Thanks

Hi,Do anyone has encountered issues installing the SP1 for AEM 6.2, just released last week!I followed the procedure in the release notes and I get :org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /etc/cloudsettings/default/...

Instead, use a Lucene Non Root Index under /content/michigan-lsa/ and add the properties that are refer in your query, also think to optimize your query try to use slingResouceType instead of cq:temple. You can debug your query and the index using ACS Toolsselect [jcr:path], [jcr:score], * from [cq:...

Use lucene base indexes, you can create a non-root index under /content/abc/oak:index for the property jcr:title, should work and speed up your query.For that you should have the latest hotfix for AEM 6 (OAK 1.0.11)https://helpx.adobe.com/experience-manager/kb/aem6-available-hotfixes.html (the fix c...