If the same code works fine in local but not in another environment, then its most likely environment configurations. Check the library versions are same, core components, ACS commons/tools versions, as applicable. Check that your "service user" has appropriate permissions and compare the lib. versi...

How are components A & B related to each other?  Are they siblings or parent-child?  Do you observe this in author or publish?Did you write "code/media queries" to show component B in "medium" breakpoint?Please share the screenshots/video/gif and media queries code for same.

do you see it configured under  '/system/console/jcrresolver ' ? test it to make sure that it works fineIf it doesn't work on prod-publish server then you'd need to fix it If it works fine on prod-publish server and not on dispatcher then apache redirects rules could be an issueshare the appropriate...

Check this -- CQ development patterns – Sling ResourceResolver and JCR sessions | Things on a content management system  Update (2018-10-26): 5th rule: Adapting a ResourceResolver to a session object does not create a new session!When you have an already open ResourceResolver, adapting it to a Sessi...

Login to the server on which you've deleted the page using -  http://<servername>/siteadmin#/content**This link uses "siteadmin#" and not "sites.html"Revert in case you still face issues.

Probably, you're checking the same in TOUCH UI. Open http://localhost:4502/siteadmin#/content  -- this would enable CLASSIC UI. Then follow the links shared by Arun/Vishu. You'd see the "deleted" page under the selected parent page with an option to recover.

If you want to proceed with this approach, then try -P "profile1,profile2" within quotes

check if the login page configurations are fine. You could even compare/package the default ACLs and move it to this instance to rule out permission issues while upgrading.

You'd need to invoke these profiles individually from CI/CD tool jenkins/bamboo or similar. Configure multiple build-targets in that job and pick a different profile for each target.

You can create pages programmatically based on the design of your app. In your migration script, you could build the intelligence to define content-to-component/template mappings based on your use case(s). I assume that you mean assets (js/css/images etc.) with this statement and not the actual cont...