If a date component has its "end date" set to 0, viewing the webform gives a 500 error.
However I get no error when setting another value e.g. "+0 years".

Thanks in advance for your help

Laurent

Comments

quicksketch’s picture

Thanks @Laurent_, I really appreciate you opening a new issue for this problem.

I can see how we might accidentally overlook this problem, as most of the time when I don't want an end date I'll just leave the field blank. An end-date of "0"... I'm not sure what that would mean from a computer's standpoint. It could mean "0AD" I suppose, which might be where the error is occurring, since there isn't a 0AD (it goes right from 1BC to 1AD). However if you say "+0 years" that means the same thing as "today".

quicksketch’s picture

I'm having trouble reproducing this problem. It looks like our date interpretation may differ based on the version of PHP you're running. In general it looks like PHP 5.2+ should work better. The date handling in older versions of PHP is pretty shaky. Which version are you running?

Agence Web CoherActio’s picture

I am running php 5.2.13 with a memory_limit of 256M.
Perhaps we could simply prevent setting 0 as end date.

DanChadwick’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)

If this is still a problem in the lastest 7.x-4.x, please re-open.