I don't know if this is a Token issue or an issue with Custom Formatters, but Custom Formatters for Dates seemed to break around the same time I updated Token. There are others that are seeing the same thing - see http://drupal.org/node/1511830

There's been no change to CF, so I think it's at least worth looking into whether or not the latest Token changes are causing CF to fail here. If not, please forgive the intrusion; regardless, thank you for all the work on this terrific module!

Comments

ronny89’s picture

ronny89 commented

does it only happen to you when using CF?
i don't get any field-date-token after upgrading both Token and Date module without ever having used CF.

bcobin’s picture

bcobin commented

Thanks for asking, @ronny89 - CF is the only place I'm using date tokens. When you say you "don't get any field-date-token" after upgrading, are you saying that date tokens are behaving properly for you or do you mean what you're saying literally - that you're seeing the token text rather than the expected values?

If it's the latter, that's what I'm seeing - the token text instead of the expected values. Unfortunately, this is on a live site, so I can't test it extensively.

See http://drupal.org/node/1530042 and http://drupal.org/node/1511830 for more information - this may be Entity, Date or some combination thereof.

Thanks for responding!

ronny89’s picture

ronny89 commented

none of these, in my case i use tokens in pathauto.

for example,
[node:workbench-access-sections]/[node:field_date]/[node:title]
would generate
museum/foo-bar-opening

so yes, i mean it literally: i don't get any date-token at all.

i already stumbled across several issues who may relate to this and am afraid that there are several causes. at least i have no clue where to start. i will probably try downgrading Date and Token modules at first.

sonar_un’s picture

sonar_un commented

I am getting the same problem. The date tokens were working before the last update.

I am now using the -dev verisons of Date, Token and Entity and the issue still exists.

Poking around drupal.org revealed some people were having the same issue; however, I don't see much discussion on the subject.

ronny89’s picture

ronny89 commented
Status: Active » Closed (fixed)

some update fixed this.