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.

CommentFileSizeAuthor
#1 1812372.patch518 bytesbleen

Comments

bleen’s picture

Status: Active » Fixed
StatusFileSize
new518 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.

bleen’s picture

Status: Fixed » Needs review

Status: Needs review » Needs work

The last submitted patch, 1812372.patch, failed testing.

bleen’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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

bleen’s picture

Issue summary: View changes

Updated issue summary.

bleen’s picture

Issue summary: View changes

Updated issue summary.