@Raghu_Adobe  This cookie is set based on if the visitor support cookies or not. This cookie was named from "check" to "at_check" in earlier versions of at.jsDetails of all the Experience Cloud and Target cookies can be found here: https://experienceleague.adobe.com/docs/core-services/interface/ec-c...

@infinityskyline  I would suggest to go with a clientlib (categories cq.authoring.dialog) where you would be able to get the current page and add your filter logic as needed. An example below:http://experience-aem.blogspot.com/2016/04/aem-62-touch-ui-path-browser-filter-for-autocomplete-and-picker-r...

@viragp64924055  Seems like you've not set the Options in the ACS instance (Administration > Application Settings > Options)TNT_TenantName: name of the Adobe Target tenant. This value corresponds to the name of the Adobe Target Client/ Clientcode.You can find more details here:https://experienceleag...

@mr-smith  It would be recommended to use Dynamic Media components (like Generic DM component, 360 Video, Interactive, Smart Crop, 3D) instead of directly adding the DM media url. You would also get other configuration options like selection of viewer, image/ viewer preset, modifiers, breakpoints, s...

For content blocks, you would see an options toolbar like this, you would be able to change text color.The change in color doesn't show up in Preview though. The other option would be to duplicate 'Link to Mirror Page' content block, make sure 'Depends on Format' is selected and add color on a tag a...

There would be one constraint with cq:decoration tag is that the this property won’t let the component editable as wrapping elements are mandatory to open a dialog in the edit mode.

@scarrington1990  Try selecting the link text and you would see all the formatting options on the right side under Component Settings as below:Click on the color box next to Link Color and you get the color palette with all the options to change color. 

@Casal0x  Please refer to this article for various options: http://www.sgaemsolutions.com/2017/11/useful-properties-of-component-in-aem-63_4.htmlYou can also refer to this discussion for further understanding: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/removing-wrapper...

@larry19  Your issue looks similar to one mentioned here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-filter-access-an-asset-url-with-the-requestdispatcher/qaq-p/231148There's probably a DAM Asset filter that is taking precedence.Try using Felix Servlet Filter (th...

@Shwetha1994 - Since the vanity URLs are working in the author/ publish instance, it's not an issue related to selectors. Basically, dispatcher level additional configurtions has to be done for new vanity URLs to be picked up. This is explained here: https://experienceleague.adobe.com/docs/experienc...