Deprecate the dfp_tag:url token [#1812372]

There is no reason for this token to exist given that the same (and more) can be accomplished using existing tokens. Below are some examples. Lets assume that we are on a node page with a canonical URL of mysite.com/node/23 and an aliased url of mysite.com/path/to/content

[dfp_tag:url_parts:2] -> node/23
[current-page:url:args:value:0]/[current-page:url:args:value:1] -> node/23
[current-page:url:unaliased:args:value:0]/[current-page:url:unaliased:args:value:1]  -> path/to

The existing tokens are much more flexible.

Comment	File	Size	Author
#1	1812372.patch	518 bytes	bleen

Comments

Comment #1

bleen commented 14 October 2012 at 14:24

Status:

Active

» Fixed

Status	File	Size
new	1812372.patch	518 bytes

This patch tells people this token is deprecated ... I dont want to remove it completely because some sites may already be using the token and while I could use an update hook to simply replace the dart token with its current-page equivalent but this would not work for any dfp tags that have been exported using features.