Thanks for the links @Asutosh_Jena_ , your second link is the one in my original post.I've worked through the documentation but, while the code executes OK, client-side Javascript does not read the OSGi-configured service values, as the documentation suggests it should. I raised a Forum question a few weeks ago when I was working through this initially but didn't solve it. I would like to see a working example of this cookie opt out feature so that i see how a working implementation differs from...

@VaniBhemarasetty are you familiar with the AEM Sites cookie opt out feature?I can't get the client side library to work, following the Adobe documentation.I'm sure i'm missing something simple - see the comments above on this forum question.

Also, I tried setting the header as per the other web page you referenced and applied changes to the "we retail" example project. Unfortunately with the same outcome 😣. I must be missing some configuration or additional settings... My local osgi output service now configured as follows,http://localhost:4502/libs/granite/security/optout/configuration.json { "cookienames": [ "omniture_optout", "cq-opt-out" ], "headers": { "X-Do-Not-Track": "1", "DNT": "1" }, "whitelistcookienames": [ "ys-cq-sitea...

Hi @Arun_Patidar Where is JS you've pasted in above taken from? This granite.utils client library is made up of the scripts specified in /libs/clientlibs/granite/utils/js.txt, i.e.#base=source Sling.js Util.js HTTP.js I18n.js TouchIndicator.js OptOutUtil.js init.jsIf you look at /libs/clientlibs/granite/utils/source/OptOutUtil.js you'll see code (and its inline documentation) like the following (line 63 onwards) /** * Initializes this tool with an opt-out configuration. * * The following options...

Thanks for the help @Arun_Patidar.Some replies from me: @Arun_Patidar wrote:Hi,I did not implemented this, I was just refering the documents.Ok thanks for confirming. Can you check this configuration at http://localhost:4504/libs/granite/security/optout/configuration.jsonMy localhost:4502 author instance returns valid json (as you'd expect, given this comes as standard out of the box).{"cookienames": ["omniture_optout","cq-opt-out"],"headers": {},"whitelistcookienames": ["ys-cq-siteadmin-tree","...

Thanks for the reply @Arun_Patidar and for pointing out what the PID should be. Are you basing your reply on a working example - can you share that (I can't find an example of the opt out service being used by the we retail project)? Or is your suggestion based on the documentation, where I see it says, "...The following table desribes [sic] the properties that you need for either method. For an OSGi configuration, the service PID is com.adobe.granite.optout."I'm a bit confused about this point ...

@kenccwong in AEM 6.4. /libs/granite/ui/components/foundation/form/radio/radio.jsp is marked as granite:FinalArea which i think means this component should not be overlaid (?).(Stumbled upon this thread looking for explanation of why saved values are not shown (and subsequently get overwritten when 2 or more radio groups are used in a multifield).

smacdonald2008​ hi do you know if there is any Adobe official support / features/ plugins or advice on vanity urls for DAM assets? thanks