I have created a simple content type with two date fields, both with repeating allowed. The problem is two-fold:
- When I don't set any repeat rules nothing gets saved (see http://drupal.org/node/284557).
- When I set repeat once every week, with no exceptions, I get an infinite loop failing with the error message "Fatal error: Maximum execution time of 30 seconds exceeded in [...]drupal/sites/all/modules/date/date_repeat/date_repeat_calc.inc on line 290". This seems to be related to http://drupal.org/node/274250, although I don't need to set exception dates for this to happen.
Comments
Comment #1
tobbe_s commentedI have tested beta4 now. This is what I did:
Comment #2
ronnqvist commentedConfirmed in RC 1.
1. You'll have to use the repeat functionality in order to have any date info saved at all, otherwise it throws this error:
warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in .../sites/all/modules/date/date/date_elements.inc on line 48.The workaround for this is to set it to repeat daily and set the until-value to the same date, so that it never actually gets to repeat.
2. When trying to repeat once a week the saving process takes for ever, and then it gives me the "Page not found"-page.
A workaround for this is to set "Every 7" and "Day(s)" instead of "Every" and "Week(s)".
Comment #3
karens commentedThe related problem, #284557: Error with repeat date field when non-repeating event submitted has been fixed. I can't replicate the problem with infinite loop on a weekly repeat. I need to see exactly what kind of date you're using and what options you choose. I also found a couple fixes in the repeat logic that would cause no repeats to be created with certain selections, but I can't replicate this infinite loop issue.
Comment #4
karens commentedI'm going to make an assumption that the infinite loop that I haven't been able to replicate is coming from the same problem as #292617: Date Repeat errors when Date Popup module is turned off and that fixing that problem will fix this one, too.
Marking fixed because part if this is fixed and the rest will be handled in the other issue.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.