Closed (fixed)
Project:
Token
Version:
6.x-1.15
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Oct 2010 at 21:30 UTC
Updated:
14 Nov 2010 at 20:20 UTC
Jump to comment: Most recent file
If the -raw version of a token is supposed to be the unprocessed version of that string, shouldn't 'current-page-path' be the one that has check_plain() ran against it rather than 'current-page-path-raw'? I.e. should these lines:
$alias = drupal_get_path_alias($_GET['q']);
$values['current-page-path'] = $alias;
$values['current-page-path-raw'] = check_plain($alias);
instead say:
$alias = drupal_get_path_alias($_GET['q']);
$values['current-page-path'] = check_plain($alias);
$values['current-page-path-raw'] = $alias;
??
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | token-n957934-2.patch | 909 bytes | damienmckenna |
| #1 | token-n957934.patch | 883 bytes | damienmckenna |
Comments
Comment #1
damienmckennaHere's a patch that corrects the issue.
Comment #2
damienmckennaUpdated patch that makes the -raw vs non-raw code slightly more consistent with how it should be.
Comment #3
dave reidWell dang me. Fixed in CVS.
http://drupal.org/cvs?commit=444768