I can reproduce this with both sly or div tags, it generates malformed structure, probably because 'editor' also uses <span> tags internally - <sly data-sly-unwrap="${true}" data-sly-element="${'span'}">    TEST    </sly><span    // missing closing brace    TEST    </span>You should open a bug for t...

you would still be able to create a page without using cq:conf property on root because you are directly pointing to your template path be it anywhere in the repo but for a true 'context aware' setup, you'd need this propertycheck - Apache Sling :: Apache Sling Context-Aware Configuration AEM /conf ...

the logs say  'org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /bin/solr/push/pages not found'Is this servlet active/registered in console?Check this for 'java.lang.IllegalArgumentException: width or height <= 0'Issue while uploading multiple assets inside DAM

Could you share more details about your use case? What do you mean by "extract all contents of AEM"? Does that include code/content/configuration/assets?Do you have an idea about the size of the existing repository?Do you want to perform this task one time vs periodically?Does this use case involve ...

I just tested with just these two configurations pointing to 'we-retail' on a random root page and I was able to create a page and it worked fine.Could you share relevant screenshots?If you use only single template then you would get only one option as template to create a page from within siteadmin...

try this --type=cq:Pagep.limit=-1group.p.or=truegroup.1_path=/content/we-retail/us/en/products/mengroup.2_path=/content/wknd/property=jcr:content/sling:resourceTypeproperty.1_value=wknd/components/structure/pageproperty.2_value=weretail/components/structure/pageOR(  /jcr:root/content/we-retail/us/en...

Check if this helps - Is it possible to hide or show a field(s) in a dialog based on a dropdown selection in another dialog?

Did you apply 'cq:conf' property on the root page pointing to your /conf/<site> path ?Another thing, if you've multiple templates in /conf then use a regex  /conf/<site>/settings/wcm/templates/* for cq:allowedTemplatesIs that template active/enabled?

you don't have to delete/unmount /dev/xvda1, you just need to clear the files under it so that you can create more space that AEM would be able to utilize for building package.from where did you delete the packages; /crx/packmgr or within  /tmp (/dev/xvda1) ?If you're not allowed to delete /tmp file...

/tmp is the shared space for all apps running on that m/c hence in your case even 7.8 GB wasn't enough/was occupied by other apps and not available to AEM.You may allocate a dedicated temp space to AEM via '-Djava.io.tmpdir=</path/to/tmpdir>' in the start script or otherwise clean /tmp as and when r...