Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedWhat version of the token module do you have installed?
Comment #2
webmens CreditAttribution: webmens commentedThe version of the Token module is 6.x-1.12
Comment #3
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedYour 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!
Comment #4
webmens CreditAttribution: webmens commentedThat was indeed the problem. Thanks for your help!
Comment #5
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedScheduler is now checking if the needed token functions are available.
http://drupal.org/cvs?commit=485764
Comment #6
jonathan1055 CreditAttribution: jonathan1055 commentedThis also need a D7 patch.
Just so we have things marked correctly and they do not get forgotten.
Comment #7
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedI guess we will have to check if this token stuff works at all.
Comment #8
sillygwailoToken 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).
Comment #9
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedhook_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...
Comment #10
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedReopened #960030: Scheduler token support, which is a better fit for this port...
Comment #11
Vacilando CreditAttribution: Vacilando commentedSame problem in 6.x-1.8!
Has the problem been solved in 6.x-1.x-dev?
Comment #12
Eric-Alexander Schaefer CreditAttribution: Eric-Alexander Schaefer commentedYes, 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.
Comment #13
ben.bunk CreditAttribution: ben.bunk commentedIt 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.
Comment #14
ben.bunk CreditAttribution: ben.bunk commentedFYI - 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.