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.In admin/config/system/cron there should be explanation that when cron is never run, system administrator should setup crontab. Cron url with cron key is the minimum information, complete cron line with wget command is even better.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | drupal--issue-1117780--add-cron-url-in-config-page-D7.patch | 1.31 KB | amontero |
| #4 | 1117780-4.patch | 946 bytes | amontero |
| #3 | cron.png | 37.34 KB | naxoc |
| #3 | 1117780-3.patch | 649 bytes | naxoc |
Comments
Comment #1
Dave ReidIsn't that information already provided or linked to d.org documentation on admin/reports/status?
Comment #2
ogi CreditAttribution: ogi commentedStatus doesn't imply actions or configuration. It's very convenient to have Run cron action in status page but I don't think it conceptually fits there.
Configuring cron implies just that: (1) setting how often Drupal calls cron hooks or (2) telling Drupal that cron is called by other means like crontab. IMHO
admin/config/system/cronfails miserably at (2). There's some unclear Never and non-existant guidance what to do if cron frequency is not set. And the cron url is status page is not exactly useful guidance.Comment #3
naxoc CreditAttribution: naxoc commentedI agree that having the url on that page makes sense. Putting a wget command in there would make less sense IMO - people run cron in all kinds of ways. I like to use curl and so on.
Patch puts the link on the admin/config/system/cron page:
Comment #4
amonteroFully agree.
Reroll, cron key moved from config to state recently:
#1821530: Move cron key from configuration to state system
Comment #5
Cameron Tod CreditAttribution: Cameron Tod commentedLooks great to me. It would be great if there was some way of not duplicating the string in system.install and here, but I think the potential complication of that is not worth it.
Comment #6
webchickMakes sense to me!
Committed and pushed to 8.x. Thanks.
Comment #7
amonteroBackport candidate to 7.x? The UI string is already present.
Comment #8
michaelmol CreditAttribution: michaelmol commentedPatch applied, looks clean and functional.
Comment #9
xjmComment #10
David_Rothstein CreditAttribution: David_Rothstein commentedSure, why not...
Committed to 7.x - thanks! http://drupalcode.org/project/drupal.git/commit/ef10c14
Comment #11
David_Rothstein CreditAttribution: David_Rothstein commentedPhantom "7.18 release notes" tag appeared to get added but not really... trying again.
Comment #12
David_Rothstein CreditAttribution: David_Rothstein commentedDrupal 7.18 was a security release only, so this issue is now scheduled for Drupal 7.19 instead.
Fixing tags accordingly.
Comment #14
David_Rothstein CreditAttribution: David_Rothstein commentedDrupal 7.19 was a security release only, so this issue is now scheduled for Drupal 7.20 instead.
Fixing tags accordingly.
Comment #15
David_Rothstein CreditAttribution: David_Rothstein commentedDrupal 7.20 was a security release only, so this issue is now scheduled for Drupal 7.21 instead. For real this time... I think :)
Fixing tags accordingly.
Comment #16
David_Rothstein CreditAttribution: David_Rothstein commentedFixing tags since Drupal 7.21 only contained a fix to deal with fallout from the Drupal 7.20 security release. Hopefully this is really the last time I do this and this will be released in Drupal 7.22 for real :)