<experienceFragmentsIndex-3-custom-1 jcr:primaryType="oak:QueryIndexDefinition" async="[async,nrt]" compatVersion="{Long}2" evaluatePathRestrictions="{Boolean}true" includedPaths="[/content/experience-fragments]" queryPaths="[/content/experience-fr...

Hey Lokesh,   That doesn't work....I get even more errors like: "jackrabbit-filter: Node '/oak:index/experienceFragmentsIndex-3-custom-1/aggregates/cq:Page' is not contained in any of the filter rules" and "jackrabbit-filter: Node '/oak:index/experienceFragmentsIndex-3-custom-1/aggregates/cq:Page/in...

I am trying to add a couple of fields to experienceFragmentsIndex-3 .. I did all of the instructions and didn't even change the code I got from dev server on cloud:     <experienceFragmentsIndex-3-custom-1         jcr:primaryType="oak:QueryIndexDefinition"         async="[async,nrt]"         compat...

We noticed that when we have advanced networking turned on, calls to Magento fail sometimes. When we turn off advanced networking, everything is fast and always resolves, but then we turn on and we get timeouts. We are making assumptions from an outside point. Maybe they can help.   Just to let you ...

yes mklink does work. I have done both wsl and mklink. making symlinks with wsl was a little easier then mklink....but I just created a symlink using mklink and everything was great. The only issue was I had to use git commands to upload as gitkraken was giving me issues

yeah I am using that, but would still like to use acs commons as it is nicer for the user lol.

we are using 5.3.0

nope can't run or view any reports, even the ones out of box. I get a 404 for http://www.adobe.com/consulting/acs-aem-commons/wcmmode does that have anything to do with it?

in production I am seeing: http://www.adobe.com/consulting/acs-aem-commons/wcmmode cannot be resolved  

I get the same issue when I try to edit any of the report for example   /editor.html/var/acs-commons/reports/sample-page-report.html that gives me it too, so I can't even build it. Locally I can build it just fine