Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Number of days from current date that repeat rendering is supported. Default is 2000 days, and it's recommended that this value be kept. Maximum allowed value is 10000.
The settings form does not mention that this field is used when Cron is run. Especially it doesn't say that changing this number does not go into effect until the next Cron. In my case this turned out to be a major oversight as I accidentally deleted all the rows in the affected table (ya, ya, don't ask) and couldn't create repeating events.
I'd like to see: "The 'event_repeat_calendar_map' table is refreshed with this many rows from today's date on every Cron run. High values could, potentially, cause a Cron or database timeout."
I haven't looked to see if there are any other significant effects of this value, but if there are, they should be mentioned as well.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | eventrepeat_renderhelp.patch | 2.51 KB | seanbfuller |
Comments
Comment #1
seanbfuller commentedI agree that this should be called out. This patch takes you wording and makes it a bit less technical so that some end users don't just tune out. Also, note that you shouldn't be getting the full 2000 inserts each time. Large queries should only happen the first time, or if you haven't run cron for a while.
In future versions, either this method should be cleaned up or the default should be reduced.
Comment #2
nancydruI reduced the number any way. On my test/devel sites it's not uncommon for me to not run Cron for over a week - and then manually.
Thanks for the change.
Comment #3
seanbfuller commentedCommitted to both HEAD and 5.x-1.x
Comment #4
(not verified) commented