It would be nice to be able to add token to the Privacy Policy link, because it would be more features friendly to have a token saved instead of an actual link which could be invalid after a new installation.

So, this way the feature which contains the settings, won't be overridden if I change the path of the Privacy Policy page.
And of course I can create an install profile which dynamically creates a Privacy Policy page and then sets a variable with it's node id, which could be used as a token for the link.

CommentFileSizeAuthor
#4 eu_cookie_compliance-privacy_policy_link_token-2352571-4.patch1.73 KBsvenryen
#1 privacy_policy_link_token-2352571-1.patch1015 bytesyce

Comments

yce’s picture

yce commented
StatusFileSize
new privacy_policy_link_token-2352571-1.patch1015 bytes

Here, I created a patch for it :)

boobaa’s picture

boobaa
he/him
commented
Status: Active » Needs work

@yce, your patch lacks the hook_tokens() implementation which is most likely needed.

svenryen’s picture

svenryen commented

I agree with @Boobaa here. This needs more work.

svenryen’s picture

svenryen commented
StatusFileSize
new eu_cookie_compliance-privacy_policy_link_token-2352571-4.patch1.73 KB

On second thought, I don't think we need hook_tokens, since yce wants to provide token(s) in another module. I think it makes sense to add this, though it should be noted to the user in the field description that the field supports tokens. Here's a patch that adds that explanation.

  • svenryen committed f6ffeb7 on 7.x-1.x authored by yce 
    Issue #2352571 by yce, svenryen: Privacy Policy link field should accept...
svenryen’s picture

svenryen commented
Status: Needs work » Fixed

  • svenryen committed aa984ad on 7.x-2.x 
    Merge branch '7.x-1.x' into 7.x-2.x

* 7.x-1.x: (76 commits)
Fixed an...
  • svenryen committed f6ffeb7 on 7.x-2.x authored by yce
    Issue #2352571 by yce, svenryen: Privacy Policy link field should accept...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.