Hello,

I have installed the module, while following the manual.
When I want to publish a content, I get a white screen with the following error:

Fatal error: Call to undefined function token_get_date_token_values() in /var/www/123.be/htdocs/sites/all/modules/scheduler-6.x-1.8/scheduler.module on line 909

Thanks for your help!

Comments

Eric-Alexander Schaefer’s picture

What version of the token module do you have installed?

webmens’s picture

The version of the Token module is 6.x-1.12

Eric-Alexander Schaefer’s picture

Status: Active » Closed (works as designed)

Your version of the token module is way too old. You really should install the latest release (6.x-1.15). 6.x-1.12 is now older than 18 months and there were several security fixes since then!

webmens’s picture

Status: Closed (works as designed) » Closed (fixed)

That was indeed the problem. Thanks for your help!

Eric-Alexander Schaefer’s picture

Status: Closed (fixed) » Fixed

Scheduler is now checking if the needed token functions are available.

http://drupal.org/cvs?commit=485764

jonathan1055’s picture

Version: 6.x-1.8 » 7.x-1.x-dev
Status: Fixed » Patch (to be ported)

This also need a D7 patch.
Just so we have things marked correctly and they do not get forgotten.

Eric-Alexander Schaefer’s picture

I guess we will have to check if this token stuff works at all.

sillygwailo’s picture

Token support looks like it'll need a refactor, since the function names are changed (and to my eyes, the approach to returning tokens is different from D6 to D7).

Eric-Alexander Schaefer’s picture

Issue tags: +token

hook_token_list() needs to be replaced by hook_token_info() and hook_token_values() needs to be replaced by hook_token(). The token data is indeed returned differently. Will dig into this tomorrow. Time to hit the hay...

Eric-Alexander Schaefer’s picture

Status: Patch (to be ported) » Closed (fixed)

Reopened #960030: Scheduler token support, which is a better fit for this port...

Vacilando’s picture

Same problem in 6.x-1.8!

Has the problem been solved in 6.x-1.x-dev?

Eric-Alexander Schaefer’s picture

Yes, it is solved in 6.x-1.x-dev. A better way to fix it is to update the token module to the latest version. You should do that anyway.

ben.bunk’s picture

It would be excellent if you could release 1.9 ASAP with a dependency for the latest token code so that this bug won't blindside people.

ben.bunk’s picture

FYI - Don't downgrade to try and fix this issue, you will find that it causes all of the content types to lose their scheduler settings.