No clue. Editing a database with an admin tool, bypassing the module is always risky. You should be prepared to investigate the errors with a debugger in a development environment. Otherwise, I don't see any other way to repair the damage.
I'm having the same issue. This message when I view Content: "Notice: Undefined index: phone in webform_component_include() (line 4414 of ...sites/all/modules/webform/webform.module). Were you able to resolve this issue? How? Thanks. Debra
I found a solution. I located the form and fields that were the likely cause of the problem (additional error messages were appearing on the form page and two of the fields were, in fact, "undefined". Deleted those. Problem solved.
@Debra - this would be caused by enabling a module which adds the "phone" component type, using that in a webform, and then disabling and/or uninstalling the module.
Comments
Comment #1
danchadwick commentedNo clue. Editing a database with an admin tool, bypassing the module is always risky. You should be prepared to investigate the errors with a debugger in a development environment. Otherwise, I don't see any other way to repair the damage.
Comment #3
Debra G commentedI'm having the same issue. This message when I view Content: "Notice: Undefined index: phone in webform_component_include() (line 4414 of ...sites/all/modules/webform/webform.module). Were you able to resolve this issue? How? Thanks. Debra
Comment #4
Debra G commentedI found a solution. I located the form and fields that were the likely cause of the problem (additional error messages were appearing on the form page and two of the fields were, in fact, "undefined". Deleted those. Problem solved.
Comment #5
danchadwick commented@Debra - this would be caused by enabling a module which adds the "phone" component type, using that in a webform, and then disabling and/or uninstalling the module.
Comment #6
Debra G commentedDan. Thanks for your explanation which will help me debug in the future. All the best!