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"

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

valthebald’s picture

Title: Explain the cons of the cron system » Add link to cron tutorial on drupal.org
Status: Active » Needs review
FileSize
856 bytes

Seems pretty straightforward

elvis2’s picture

I 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.

Status: Needs review » Needs work

The last submitted patch, 1679660-cron-tutorial-link.patch, failed testing.

amontero’s picture

Assigned: bagvendt » Unassigned

See 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.

elvis2’s picture

I apologize, somehow I managed to post to the wrong issue...

valthebald’s picture

Status: Needs work » Needs review

#1: 1679660-cron-tutorial-link.patch queued for re-testing.

amontero’s picture

#1: 1679660-cron-tutorial-link.patch queued for re-testing.

amontero’s picture

Status: Needs review » Needs work
Issue tags: +Novice

#4 makes it for a good novice task. Tagging.

billk2’s picture

Status: Needs work » Reviewed & tested by the community

I've run the patch and can confirm it applies the message and link as described above.

amontero’s picture

Status: Reviewed & tested by the community » Needs work

#4 needs to be addressed first.

billk2’s picture

Status: Needs work » Needs review
FileSize
8.77 KB
856 bytes

Sorry, 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'.

amontero’s picture

Review:
* 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.

rhm5000’s picture

@amontero I believe you are correct and the text should be "read the tutorial".

I have provided a patch with the correction.

Status: Needs review » Needs work
Issue tags: -Novice

The last submitted patch, 1679660-cron-tutorial-link-13.patch, failed testing.

rhm5000’s picture

Status: Needs work » Needs review
Issue tags: +Novice
valthebald’s picture

Status: Needs review » Reviewed & tested by the community

I that was testbot glitch

amontero’s picture

Retested, everything looks OK.

alexpott’s picture

Category: feature » task
Status: Reviewed & tested by the community » Needs work

Generally 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.

rhm5000’s picture

Patch created with please removed.

rhm5000’s picture

Status: Needs work » Needs review
valthebald’s picture

Patch in #19 changes phrasing, not only removes 'please'. What's the rationale?

rhm5000’s picture

Interface text style guidelines recommend that active writing be used. Also comment #18 needed to be addressed.

alexpott’s picture

Status: Needs review » Needs work

Yep "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>.

rhm5000’s picture

Status: Needs work » Needs review
FileSize
886 bytes

I adjusted the link to make it more accessible and provided a patch.

rhm5000’s picture

Also, 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.

amontero’s picture

Status: Needs review » Reviewed & tested by the community

Patch 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 .

alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Committed b6f1648 and pushed to 8.x. Thanks!

amontero’s picture

Version: 8.x-dev » 7.x-dev
Status: Fixed » Needs review
FileSize
1.07 KB

Backport to 7.x.
Just one string addition in the backend.

rhm5000’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
23.94 KB

Patch applies cleanly.
Link to the cron tutorial visible and working.

Attached is a screenshot on 7.x.

David_Rothstein’s picture

Issue summary: View changes
Status: Reviewed & tested by the community » Fixed
Issue tags: +7.25 release notes

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.