Hi, I am using drupal 6.20, and I am usign webform, webform conditional, form builder, and form builder web UI (all of this modules are enabled).

What its happening is the next:

When I disable "form builder web UI", I can use webform in its normal use. And I can create conditional rules in its field components for changing its visibility depends the values of other fields.

But when I enable "form builder web UI" I can use drag and drop interface (it´s cool! and easier!) but I can´t see the conditional rules for visibility.

Has anyone the same problem than me? is there any solution?

Thank you!

Comments

quicksketch’s picture

Category: bug » feature
Priority: Critical » Normal

Toning down the title a bit. This is not implemented yet.

pebels’s picture

Ok, sorry.

But I think may be a bug report with normal priority instead critical.

Because I dont know why I am losing a functionality (webform conditional) when I enable "form builder web ui". Really I don´t lose the functionality, because if I disabled "FBWUI" and I create rules, and after that I enable "FBWUI" these rules work. The problem is that I can`t see the conditional rules.

I thought it could be by the theme, but when I tested it wasn't.

Sorry of all ways.

Thanks!

danny englander’s picture

I just experienced this same issue after I enabled Form builder / ui. I wanted my editors to have a very easy way to create forms and surveys that have conditional logic. If I want this, should I install Webform Conditional Module? Will that give me conditionals that work with Form Builder UI or is it not quite the same functionality?

quicksketch’s picture

Right now there is no way to have conditional logic with Form Builder + Webform. The Webform Conditional project will not help with this problem. We simply have not yet implemented the interface for any conditional logic yet in Form Builder.

danny englander’s picture

Status: Active » Fixed

Ok thanks, I'll let my client decide which is more important to them, easy creation of forms or conditionals. Cheers!

danny englander’s picture

oops, sorry I marked as fixed but not sure, you may want a different status since I was not the one to open this originally.

quicksketch’s picture

Title: Form builder Web UI and Webform Conditional. » Form builder Web UI and Conditionals
Status: Fixed » Active

Let's leave it open as a general request for conditional support.

wayne57’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev

I would also like to see the conditionals added to D7 FormBuilder, which is an awesome work so far!

emptyvoid’s picture

I have a project where I could use this.
Where could I start help integrate?

Does webform conditionals have a D7 release?
http://drupal.org/project/webform_conditional

There is an alpha, but I'll need to review the source code and determine if some of the functions can be referenced/reused. But I would expect we'd have to add additional display functions to add-on to the configuration forms for each form in the form builder.

Or are we talking about the "core" conditional functionality in webform?

Question Time:
Does the form builder provide a hook alter or api to extend/expand component definitions in form builder?

I'm assuming we'd need to program an interface/bridge between the components and the conditionals module to trigger evaluation during render.

Could additional settings, values be added to the definition array saved for each component of a webform in the database?

Thoughts or ideas?
Should we attempt to get support/visibility with the maintainers of the webform conditions module?

fenstrat’s picture

Cross linking here as quicksketch is working on conditional stuff in webform core #1215456-12: Multiple and same-page conditional rules

quicksketch’s picture

Yeah my work in the other issue would immediately work with Form Builder, since it moves all the conditional logic to a new interface.

quicksketch’s picture

Status: Active » Fixed

With #1215456: Multiple and same-page conditional rules in the 4.x branch of Webform, this issue is fixed.

Status: Fixed » Closed (fixed)

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