Are you able to login into system console. If so,1. Do you see any bundles not in active state. If so, please make them active2. Open http://localhost:4502/system/console/configMgr/org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet and ensure rooth path is /crx/repository

Can you explain the steps with which you are trying to install AEM. Default local aem install documentation is at [1] [1] - https://docs.adobe.com/content/help/en/experience-manager-64/deploying/deploying/deploy.html#default-local-install

Very good question, I am not aware of any straightforward methods unless you do something like a user action mock using script. May be this should be posted to Ideas area as a RFE

Yes

Hi,Adobe documentation captures all the scenarios for AEM upgrade. Please refer to it at [1]. On a high level, the changes are1. Upgrading the AEM instance - you can do either in-place upgrade or fresh install approach based on your content size and 2. Upgrade your artefacts by compiling against 6.5...

Can you please check whether you have included [1] on the page. If you have global.jsp defined, you may be missing that. Can you check and confirm. [1] - <sly data-sly-include="/libs/wcm/core/components/init/init.jsp" data-sly-unwrap/> 

Hi @jkpanera , There is already a sling health check for active bundles. If there are any inactive bundles other than mentioned in the InactiveBundlesHealthCheck configuration, it will show up the status there. You can see the JMX for the same at [1]. You can access the healthcheck at [2] or that as...

great stats

Hi,I am unable to replicate the issue with core component 2.8.0 text component on 6.5.5. Can you please share a screenshot of the markup coming up.

Cool, thats one step forward. Are you loading the launch script in the head itself ? Does it have any attributes like async, defer etc?