All tokens are not properly substituted after upgrading to 7.x-1.2 from 7.x-1.1. It has something to do with the pregmatch in /includes/context.inc #636.

7.x-1.1 if (preg_match_all('/%([a-zA-Z0-9%:_-]+)/us', $string, $matches)) {

7.x-1.2 if (preg_match_all('/%(%|[a-zA-Z0-9_-]+(?:\:[a-zA-Z0-9_-]+)?)/us', $string, $matches)) {

Why the change?

CommentFileSizeAuthor
#2 token-regex-1741064-2.patch621 bytesrobcarr
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

robcarr’s picture

robcarr
Primary language English
Location Perthshire, Scotland
CreditAttribution: robcarr commented

I've just traced a token substitution issue down to the change from 7.x-1.1. to 7.x-1.2.

Referencing somewhere that I've just been bitten: means components of an addressfield (eg %node:field-address:postal_code) no longer work. All that is rendered is :postal_code in this example.

Looks like it relates to #1727804: Keywords substitution doesn't work as expected... re-opened that issue, hoping not to incurr the wrath of @merlinofchaos

robcarr’s picture

robcarr
Primary language English
Location Perthshire, Scotland
CreditAttribution: robcarr commented
FileSize
token-regex-1741064-2.patch621 bytes

And the attached patch gets us back to where we were a week ago:

Dmitriy.trt’s picture

Dmitriy.trt CreditAttribution: Dmitriy.trt commented
Status: Active » Closed (duplicate)

Please, check latest patch from #1727804: Keywords substitution doesn't work as expected

Dmitriy.trt’s picture

Dmitriy.trt CreditAttribution: Dmitriy.trt commented
Issue summary: View changes

Change rule number to correct one