After upgrading from a 2.9 webform there was a whitescreen (WSOD) on a form node.
Nowever accesssing edit path directly worked and so worked other subpathes (submissions, ...)

Finally deleting the date field led to successfully display the form again.

Adding a date field back again worked also.

So there's something with upgrading datefields that created illegal data to make drupal/webform crash?
I was even unable to echo in hook_init on that case.

Any idea on that?

Comments

quicksketch’s picture

quicksketch
he/him
commented

Thanks for the report. I'll have to look into what might be causing this, though such upgrade problems are notorious for being hard to track down. If you have any ideas on what might differ between your old date field and the new one, that might help figure this all out.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Fixed

I think I accidentally ran into this issue while working on #767812: Add relative date support to start and end years. It should also be fixed by that patch, though it was an unintended side-fix. Basically I was experiencing this problem in either of these situations: 1) Date API was not installed at all 2) Date API was installed but no timezone was set.

Webform should now be properly falling back to no timezone handling if Date API is not installed.

quicksketch’s picture

quicksketch
he/him
commented
Version: 6.x-3.x-dev » 6.x-3.0-beta5

Assigning version this problem exists in. Right now you'll have to use CVS, the dev version, or apply the patch in #767812: Add relative date support to start and end years.

Status: Fixed » Closed (fixed)

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