* Do you see the same behavior, when you close all currently opened tabs & windows, clear browser cache & cookies, open a new browser in Incognito mode?* Do you see any errors in the Console tab of Developer Tools?* Did you install any custom/third-party bundle/package, after which you started seein...

The following web servers are supported for Dispatcher:https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requirements.html#dispatcher-platforms-web-servers You can refer to the Dispatcher docs here:https://docs.adobe.com/content/help/en/experience-manager-...

dispatcher-apache2.4-xxx isn't supported on Windows. The following web servers are supported for dispatcher:https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requirements.html#dispatcher-platforms-web-servers You can download the specific dispatcher from h...

I am not able to reproduce the issue on 6.4.8.1.Are you using the same user to unlock the page, that had actually locked the same page? If not, then you would need the actual user who had locked the page, or OOTB superuser named  "admin" to unlock that page. I created a user named "testUser" and add...

Thank you for clarifying it.  You can use any HTML Parser library(eg: JSoup HTML Parser) to do that. Include that dependency in pom.xml file and then use it to read HTML content or even links on any internal page. Sample Reference code can be found here:https://mkyong.com/java/java-how-to-get-all-l...

Make the necessary change(s) in the template(s) that are used to create those pages. That would fix the JS/CSS errors on all the pages that are created using that template. I hope it helps !! 

You can write a groovy script that crawls over your /content/<site> looking for strings that start with /content. Then, use ResourceResolver to verify whether those paths exist. The following links may be helpful:a) Sample Groovy Script => https://gist.github.com/trekawek/72b3515a6641ca5f4b29b) Reso...

I doubt there is any such group OOTB. But, it's really easy to create one such group. You just have to create a group and give complete Read Access in /useradmin console. Ex: http://localhost:6440/useradminSteps to follow:1) Go to http://<host>:<port>/useradmin 2) Create a new group by clicking Edit...

Can you please enable DEBUG logging for error.log loggers and see whether you get any requests for custom servlet in error.log file?

Verify the CRUD permissions for those groups in /useradmin console.Also check their ACLs in crx, if it's specific to any node.These might help figure out the reason.