Some users want more fine grained control over the cron intervals. Currently the cron interval options are 1 Hour, 3 Hours, 6 Hours, 12 Hours, 1 Day and 1 Week.
For example this issue supplies a patch adding the intervals: 5,10,15, and 30 minutes.
My point is that adding shorter intervals doesn't necessarily make sense in a "poor mans cron" (link) since Drupal cron is dependent on site traffic.
My sketchy suggestion is to supply an explanatory text to /admin/config/system/cron saying something like "If you need other intervals than the ones defined below, you need to set up a real cron. Since this cron is dependent on site traffic"
Comment | File | Size | Author |
---|---|---|---|
#29 | drupal--1679660--cron-tutorial-link--29.png | 23.94 KB | rhm5000 |
#28 | drupal--1679660--cron-tutorial-link--28.patch | 1.07 KB | amontero |
#24 | 1679660-cron-tutorial-link-24.patch | 886 bytes | rhm5000 |
#19 | 1679660-cron-tutorial-link-19.patch | 843 bytes | rhm5000 |
#13 | 1679660-cron-tutorial-link-13.patch | 860 bytes | rhm5000 |
Comments
Comment #1
valthebaldSeems pretty straightforward
Comment #2
elvis2 CreditAttribution: elvis2 commentedI am wondering, maybe using batch queuing might be a better option? How would this work? Basically all the nodes that need indexing, above x threshold, the node details would be thrown into the queue table, with the callback function to handle the indexing based on queuing processing.
Comment #4
amonteroSee the notes about embedding links in translatable texts in the l() documentation:
http://api.drupal.org/api/drupal/core%21includes%21common.inc/function/l/8
Also unassigning to allow others to work on it.
Comment #5
elvis2 CreditAttribution: elvis2 commentedI apologize, somehow I managed to post to the wrong issue...
Comment #6
valthebald#1: 1679660-cron-tutorial-link.patch queued for re-testing.
Comment #7
amontero#1: 1679660-cron-tutorial-link.patch queued for re-testing.
Comment #8
amontero#4 makes it for a good novice task. Tagging.
Comment #9
billk2 CreditAttribution: billk2 commentedI've run the patch and can confirm it applies the message and link as described above.
Comment #10
amontero#4 needs to be addressed first.
Comment #11
billk2 CreditAttribution: billk2 commentedSorry, didn't spot that. I've re-rolled with translatable url for someone else to check.
I took the opportunity to add a full-stop and increased the link text to be more descriptive: 'read tutorial'.
Comment #12
amonteroReview:
* Patch applies.
* Looks as posted image.
* Could easily find and translate the string.
* Code looks OK.
I'm no native English speaker, but shouldn't the text be "read the tutorial"? Maybe docs/documentation? Aside from this, it's a clear RTBC for me.
Comment #13
rhm5000 CreditAttribution: rhm5000 commented@amontero I believe you are correct and the text should be "read the tutorial".
I have provided a patch with the correction.
Comment #15
rhm5000 CreditAttribution: rhm5000 commented#13: 1679660-cron-tutorial-link-13.patch queued for re-testing.
Comment #16
valthebaldI that was testbot glitch
Comment #17
amonteroRetested, everything looks OK.
Comment #18
alexpottGenerally we do not use the word please in help text. See #1970068: Remove all please(s) from the views UI for more discussion on this issue.
Also this seems helpful and is more of a task than a feature and should be subject to thresholds.
Comment #19
rhm5000 CreditAttribution: rhm5000 commentedPatch created with please removed.
Comment #20
rhm5000 CreditAttribution: rhm5000 commentedComment #21
valthebaldPatch in #19 changes phrasing, not only removes 'please'. What's the rationale?
Comment #22
rhm5000 CreditAttribution: rhm5000 commentedInterface text style guidelines recommend that active writing be used. Also comment #18 needed to be addressed.
Comment #23
alexpottYep "here" is not great text for a link. For accessibility it is important that link text describes the destination of the link. We can use the title attribute to add additional information but I think that is not necessary here.
How about something like this:
For more information about setting up scheduled tasks <a href="@url">read the cron tutorial on drupal.org</a>.
Comment #24
rhm5000 CreditAttribution: rhm5000 commentedI adjusted the link to make it more accessible and provided a patch.
Comment #25
rhm5000 CreditAttribution: rhm5000 commentedAlso, for the question in comment #21 of why I changed the phrasing, meant to address a concern I have over the statement telling the user to read rather than giving the user an option.
Comment #26
amonteroPatch applies cleanly and text reads exactly (copy/paste):
More information about setting up scheduled tasks can be found by reading the cron tutorial on drupal.org.
Also, links OK to d.o/cron .
Comment #27
alexpottCommitted b6f1648 and pushed to 8.x. Thanks!
Comment #28
amonteroBackport to 7.x.
Just one string addition in the backend.
Comment #29
rhm5000 CreditAttribution: rhm5000 commentedPatch applies cleanly.
Link to the cron tutorial visible and working.
Attached is a screenshot on 7.x.
Comment #30
David_Rothstein CreditAttribution: David_Rothstein commentedCommitted to 7.x - thanks! http://drupalcode.org/project/drupal.git/commit/7b029ac