This is still a relevant topic for AEM Forms. I'm guessing not that many people use it because its pretty evident. When the guideContainer is loaded, the common clientlib gets loaded, adding reset and overrides for things like inputs, buttons and containers, which is ok, if you only have AEM forms o...

Its been a while since the answer was given... Are there any restrictions of contexthub to target a layout container / parsys ?I have components such as accordions or tabs that when targetted, content in the embedded inner layout container disappears and cannot have variations. It doesn't matter if ...

Not that I'm aware. Code in geolocation store do not allow reverse geolocation if ContextHub UI is not available. So publish server will not do reverse geolocation. Any segment done with this properties are not going to work on publish unless you extend this store or create your own.

How did you get this code? Any sources we can check? OR just reading the source code?

You need to implement you own geolocation store if you want to get this information. Geolocation store from context hub will only do reverse geocoding when context hub ui is enabled (authoring edit/preview) and not in publish mode. I'm guessing this is due to licensing issues. If you check the jcr n...

Solution for me so far is to build a custom store based on the geolocalization one. There is a constraint in the reverse geolocation to the context hub ui. Not sure why. but its there. not configurable as far as I could read in the code.The summit toy store keeps coming as a reference, but that is c...

If you are talking about say, using columns 4-10 instead of 1-6, you can achieve this if you are using AEM 6.3 or newer as grid offset functionality is not available before that. You just have to go to layouting mode and drag the left blue dot to the column you want the component to begin, and then ...

Sure.So steps I took to solve this issue:1. Override libs/cq/xssprotection/config.xml to include my data attributes: This will allow context html to render them. 2. To avoid RTE editor to strip them, I have disabled xss filtering for both dialog and inplace editor by adding the property to the text ...

So, for anyone who has the same issue, the RTE editor strips the data attributes because the xssFiltering is enabled at dialog level. I used the xssDisableFiltering in my text node of my dialog and that did the trick.

For some reason this is not working for <a> tags in aem 6.4. Any other ideas?