Is this behavior observed in only this component or in all custom TOUCH UI components. Are you seeing any browser errors?This should not be occurring.

The standard way in AEM to expose data in the JCR to other 3rd party destinations is use of Content Services. From the docs:  "AEM Content Services output to destinations other than AEM pages, of content below page level (assets, fragments), in formats including but not limited to HTML, specifically...

You identified the way -- Session session = resourceResolver.adaptTo(Session.class);session.getUserID();more details -- session - AEM - get current UserId - Stack Overflow

Looks like an upgrade error. Please file a ticket with customer support as you may need a hotfix.

See Versioned ClientLibs YOu can comment at that URL too for questions why its not working.

Why are you not using AEM Responsive Grid system? No need to modify divs when using the Responsive Grid to line up components in a column format.

AEM Support out of the Responsive Grid component that lets you place your components into columns.Or you can use a custom TOUCH UI Grid component - as pointed out by Gaurav. To learn how to use the out of the box Responsive Grid component - go through the entire weekend tutorial - Getting Started wi...

Seems like there could be an issue setting up SOLR and Indexing. I recommend that you watch this GEMS session where they cover this use case -- Solr as an Oak index for AEM

Can you show the JCR Queries you are using. Aslo - we are running a session on AEM Queries in 30 mins. Scott's Digital Community: [Webinar | February ] Ask the AEM Community Expert: Best practice to query JCR data using Que…

As mentioned in this thread - Gaurav and Veena - can reproduce this issue and asked you to open a support ticket so this issue can be fixed. Thanks