Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Cool! I'm glad to hear there is interest! I've been kind of ignoring this module because I thought nobody was using it.
Yes, I will upgrade it to 5.0. It may not happen for a couple more weeks, because I have other modules that are in more demand. But I do use CronPlus on a couple of my own sites and had intended to upgrade it if only for that reason. Now that I know there's interest outside of my own use, I'll see if I can't get it higher in the priority queue.
Out of curiosity, are you currently using CronPlus under an earlier Drupal version, or are you just considering starting to use it?
By the way, if you're a coder and would like to take a crack at the upgrade, I'd be glad to review your patch and commit if it passes testing. Just let me know if you're going to do this, so we don't duplicate efforts.
I'm currently building a 4.7 site, but want to make sure the module I use are going [to] be available in Drupal 5.0 in a few months time when I upgrade.
I've got to upgrade my FeedParser package to v5.0 yet, hence the few months time line.
A good decision, to plan ahead. :-)
The CronPlus module is not terribly complex, so it won't be hard to convert. It's just not my highest priority at this particular moment because I have a lot more users for Links Package (already converted, but still being debugged) and for image_import (which will be a bear to convert, unfortunately).
I don't see any problem with committing to get CronPlus upgraded by the end of March, though. If you wish, I'll be glad to notify you when I have a beta version ready, and you can help test it. Your timeline is similar to my own...I have one site that uses CronPlus, and am planning to upgrade that site in April or May.
Thanks again for your interest in CronPlus. I was beginning to fear I'd written it only for myself. :-)
Great work, "darthsteven"! Thanks to your help, I've just released the first official Drupal 5.x version of this module. It should be showing up on drupal.org shortly. I really appreciate your patch contrib. I found only one bug, specifically that the "view cronplus logs" link no longer worked. That's been fixed. As far as I know, the module is good to go.
Again, thanks for the patch! I've added you to the module credits.
At first wanted to thank for your work - i'm very much surprised, that so there are not enough responses about the module!
Probably because of my not so good knowledge of php or the English, but I don't understood in accuracy that means each of parameters $now, $last_cron and $last_this.
Can you show some examples how correctly to define function module_cronplus_daily which should be carried out each five hours, for example?
$now uniquely identifies the current cronplus instance.
It's the timestamp of when that particular cron run started.
$last_cron is the value that $now took on the last cron run.
$last_this is the value that $now took the last time that this particular hook was invoked.
So, for example, say it was 1970-01-02 05:00:00 UTC and cron was set to run every hour, then, cronplus would call:
hook_cronplus_hourly(104400, 100800, 100800)
then at: 1970-01-03 00:00:00 UTC we'd get:
hook_cronplus_hourly(172800, 169200, 169200)
hook_cronplus_daily(172800, 169200, 86400)
If you want to make something run every 5 hours, I'd guess the best way would be to increment a counter every hour (hook_cronplus_hourly) and then check to see if it was greater than 5.
Comments
Comment #1
syscrusher commentedCool! I'm glad to hear there is interest! I've been kind of ignoring this module because I thought nobody was using it.
Yes, I will upgrade it to 5.0. It may not happen for a couple more weeks, because I have other modules that are in more demand. But I do use CronPlus on a couple of my own sites and had intended to upgrade it if only for that reason. Now that I know there's interest outside of my own use, I'll see if I can't get it higher in the priority queue.
Out of curiosity, are you currently using CronPlus under an earlier Drupal version, or are you just considering starting to use it?
Syscrusher
Comment #2
syscrusher commentedBy the way, if you're a coder and would like to take a crack at the upgrade, I'd be glad to review your patch and commit if it passes testing. Just let me know if you're going to do this, so we don't duplicate efforts.
Syscrusher
Comment #3
buddaI'm currently building a 4.7 site, but want to make sure the module I use are going ot be available in Drupal 5.0 in a few months time when I upgrade.
I've got to upgrade my FeedParser package to v5.0 yet, hence the few months time line.
Comment #4
syscrusher commentedA good decision, to plan ahead. :-)
The CronPlus module is not terribly complex, so it won't be hard to convert. It's just not my highest priority at this particular moment because I have a lot more users for Links Package (already converted, but still being debugged) and for image_import (which will be a bear to convert, unfortunately).
I don't see any problem with committing to get CronPlus upgraded by the end of March, though. If you wish, I'll be glad to notify you when I have a beta version ready, and you can help test it. Your timeline is similar to my own...I have one site that uses CronPlus, and am planning to upgrade that site in April or May.
Thanks again for your interest in CronPlus. I was beginning to fear I'd written it only for myself. :-)
Kind regards,
Syscrusher
Comment #5
rlbravo commentedI´m also using that module. I should say it´s great! Thanks!
Comment #6
steven jones commentedI've ported the module to 5.x, and tidied the code up a little.
This is my first patch, so go easy on me :-)
Clearly you'll need to add a cronplus.info file too!
Comment #7
syscrusher commentedGreat work, "darthsteven"! Thanks to your help, I've just released the first official Drupal 5.x version of this module. It should be showing up on drupal.org shortly. I really appreciate your patch contrib. I found only one bug, specifically that the "view cronplus logs" link no longer worked. That's been fixed. As far as I know, the module is good to go.
Again, thanks for the patch! I've added you to the module credits.
Syscrusher
Comment #8
Libra commentedAt first wanted to thank for your work - i'm very much surprised, that so there are not enough responses about the module!
Probably because of my not so good knowledge of php or the English, but I don't understood in accuracy that means each of parameters $now, $last_cron and $last_this.
Can you show some examples how correctly to define function module_cronplus_daily which should be carried out each five hours, for example?
Comment #9
steven jones commented$now uniquely identifies the current cronplus instance.
It's the timestamp of when that particular cron run started.
$last_cron is the value that $now took on the last cron run.
$last_this is the value that $now took the last time that this particular hook was invoked.
So, for example, say it was 1970-01-02 05:00:00 UTC and cron was set to run every hour, then, cronplus would call:
hook_cronplus_hourly(104400, 100800, 100800)
then at: 1970-01-03 00:00:00 UTC we'd get:
hook_cronplus_hourly(172800, 169200, 169200)
hook_cronplus_daily(172800, 169200, 86400)
If you want to make something run every 5 hours, I'd guess the best way would be to increment a counter every hour (hook_cronplus_hourly) and then check to see if it was greater than 5.
Hope that helps.
Comment #10
Libra commentedHi darthsteven! Thanks for a prompt reply and examples! Now I have understood logic of work of hook_cronplus function :-)
Comment #11
(not verified) commented