Closed (fixed)
Project:
Form Builder
Version:
7.x-1.x-dev
Component:
Webform Itegration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Feb 2012 at 10:03 UTC
Updated:
2 Jul 2015 at 20:34 UTC
Jump to comment: Most recent
Comments
Comment #1
pluginguin commentedI found a way around my problem.
It seems as if when I start the form by adding an emailadres in the form settings section, the fields I create in the form elements section reman visible after saving.
The problem is still there though... but no longer an issue for me.
Comment #2
pluginguin commentedComment #3
quicksketchCould you try using the latest dev releases of both Form Builder and Webform? I've done some pretty major overhauling in both versions that should correct this problem.
Comment #4
pluginguin commentedEhm...
two questions:
1. I don't see a dev version of webform...?
2. How do I update from a released version to a dev version without first deinstalling everything?
Regards,
Pluginguin
Comment #5
pluginguin commentedUpdated to formbuilder dev version... no change in behavior of forms.
Comment #6
quicksketchSo could you recap how you're getting this problem? I think I might not be understanding the problem.
To reproduce(?):
- Create a new webform node.
- Rather than adding fields to the form, click on the Webform -> Emails tab and add an e-mail configuration.
- Then what?
Comment #7
pluginguin commentedWhen I create a new form and start by adding elements to the form and then save the form, nothing gets saved.
When I create a new form and start by setting up things in the form settings-page first, save those and then add elements to the form. The elements remain after saving.
Comment #8
BoogieBug commentedConfirm the reproduction as procedure described in #7 and subscribe for update.
Note that I'm using version 7.x-1.0 (8 Mar)
Comment #9
quicksketchI couldn't reproduce this form on the "webform" content type, but found that I have the described problem when creating content types that are webform-enabled (such as a "page" content type). Are you experiencing this on the "webform" type also, or did I find a different problem?
Comment #10
pluginguin commentedNo, it is on webform enabled pages. Did not mention that. Thanks Quicksketch!
Comment #11
jeremymcminn commentedIm still getting this issue on content types with webform enabled - is there a fix for it?
Comment #12
emptyvoid commentedI'm getting the following error with with a fresh install of form builder dev and webform dev (3.x)
Should I be using a different branch for D7? Maybe 4-alpha (shutters in chair).
Comment #13
emptyvoid commentedRunning xdebug on the code in question and I have determined that the $node object is totally empty. This of course causes the whole function to fail horribly.
Because the function is called via ajax the end user doesn't see a response. I do get the error back via ajax and it is visible when I run firebug.
I'll trace the method and see what is causing the $node object to not be referenced correctly.
Comment #14
emptyvoid commentedThe following is the trace stack of methods in each files that is called to render the form elements in the form builder. In my case none of the form element types renders the edit form to modify properties.
Comment #15
emptyvoid commentedBingo!
/modules/form_builder/modules/webform/form_builder_webform.components.inc
Line: 1056
Instead of creating a empty object with no definition why not load the target parent node object?
From reviewing the descriptor for the function I can't see any reference to the parent node nor the webform instance. So how can you bind the component to the target webform or parent node?
Comment #16
emptyvoid commentedFurther tracing the issue I determined that the core webform components method does not load the referenced node.
Should I post this as an issue to webform too?
/webform/includes/webform.components.inc
line: 346 (current code)
Added a validation routine to check for the existence of a valid node object, if not load it from the component reference.
BOOM now it works.
Comment #17
emptyvoid commentedChanging to be more accurate.
Comment #18
emptyvoid commentedUmm, yeah the code above only enables the first component added to the webform to actually work.. Add any others and.. (pffffttttt) no workie. :(
Comment #19
quicksketch@emptyvoid: I can't reproduce the problem at all. The latest versions of both Webform 3.x and 4.x seem to work with Form Builder for me.
Comment #20
guictx commentedI'm on Webforms 7.x-3.x-dev and Form Builder 7.x-1.1 and although everything seems to be working fine - I can save changes to the form - I get the error message in #12 a lot.
Comment #21
torotil commentedThe notice has been fixed with the commit http://cgit.drupalcode.org/form_builder/commit/?id=3d904dfd6e36862f76710... about two years ago.