I've installed webform 7x-4 with Drupal 7.22. So far I can add all the other components but when I try to add a select option I get a blank screen on Firefox and a 500 internal server error on IE 9.

I thought it might've been the webform so created a new one with only a text field and still unable to add checkbox/select option.

This is what the url looks like on Firefox.

domain.com/node/1087/webform/components/new/select?name=chek&mandatory=0&pid=0&weight=1

All I get with IE is

domain.com/node/1087/webform

Comments

lias’s picture

lias commented

Is this patch applied to the 7x-4 version and is it related?

http://drupal.org/node/1569556#comment-5987514

lias’s picture

lias commented

Was able to add select options to my webform after installing the options element module.

I don't need the functionality provided by the additional module so it would be nice if this was working in webform 7x-4.

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support
Priority: Major » Normal
Status: Active » Fixed

This usually happens when you have Token Entity module installed. It overwhelms the memory of the server and causes a WSOD when trying to render the list of tokens. This has been fixed by #1801782: Use the new token dialog to enhance UX.

agence web coheractio’s picture

agence web coheractio commented

@quicksketch.
I am facing the 500 error with Token Entity enabled. The change you mentioned in #1801782: Use the new token dialog to enhance UX applies only to 7.x.4.

Do you have a similar bug fix for 7.x.3 ?

Thanks in advance

Laurent

agence web coheractio’s picture

agence web coheractio commented

Very strange but don't know if this is related.

When I add a date component and I set its "end date" to 0, I always get the 500 error.
However I get no error when setting another value e.g. "+0 years".

Laurent

quicksketch’s picture

quicksketch
he/him
commented

Do you have a similar bug fix for 7.x.3 ?

The 3.x branch does not need the patch because 3.x does not use the new token system. Entity Token should not have an effect on the 3.x branch.

When I add a date component and I set its "end date" to 0, I always get the 500 error.

This sounds like it could be a new bug. I haven't heard of this report before. If it happens every time it'd be best to make a dedicated issue for tracking it.

agence web coheractio’s picture

agence web coheractio commented

Thanks
I've logged another issue here : Error 500 if date component "end date" is set to 0

Laurent

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