This module is still in development. As explained on the project page, several patches are still required in order for it to work at all. If you'd like to try it out, here are the instructions.
You'll first need to download the latest HEAD versions of this module and the modules it depends on (see the project page for further details).
You'll then need to apply the latest patches from the following issues (for convenience, links to the latest patch as of January 27 are included in parentheses).
For Webform
- #976102: Drupal 7 version of Webform not updated for text format changes (http://drupal.org/files/issues/webform-text-formats-976102-10.patch)
- #1009240: Individual field inline-label support (http://drupal.org/files/issues/webform_title_display.patch)
For Form Builder
- #1010254: Update the theming of form_builder to D7 (http://drupal.org/files/issues/form-builder-theme-1010254-3.patch)
- #1010818: Drupal.formBuilder.clickField is fragile and could be improved (http://drupal.org/files/issues/form_builder_click.patch)
- #1010926: Improve AJAX form requests and submission (http://drupal.org/files/issues/form-builder-ajax-1010926-2.patch)
- #1011060: Dragging fields into fieldsets is wonky and need refinement (http://drupal.org/files/issues/form_builder_dragdrop.patch)
- #1019130: Form Builder AJAX system doesn't support Drupal.settings (http://drupal.org/files/issues/form-builder-render-json-1019130-3.patch)
- The patch attached to this comment #3 of this issue (http://drupal.org/files/issues/form-builder-js-extra-webform-alt-ui-2.patch) - we still need to review and break this one up into sensible chunks before it's ready to be posted as an issue in the Form Builder queue.
With those patches applied, it should be possible to successfully use the module to create webforms in a development (testing) environment. Note that some things still aren't working totally correctly with the above patch set (fieldsets, for example, don't work at all), which means we are still missing some things in the list. But this should be enough to use the module and get a feel for it. (no longer an issue; see comment #3 below)
Comments
Comment #1
BenK CreditAttribution: BenK commentedSubscribing
Comment #2
EclipseGc CreditAttribution: EclipseGc commentedyeah... sub
Comment #3
David_Rothstein CreditAttribution: David_Rothstein commentedThere's an updated patch on one of the above issues (#1010818: Drupal.formBuilder.clickField is fragile and could be improved) that makes it so fieldsets now work.
I've updated the list above to refer to that, and also to link to a new version of the "extra" patch (attached to this comment) required as a result of that.
With those changes, the above instructions should work to get the module functioning correctly!
Comment #4
bryancasler CreditAttribution: bryancasler commentedsubscribe
Comment #5
james.elliott CreditAttribution: james.elliott commentedAnother patch that is necessary for this module to work is #1047612: Allow other modules to specify where the field configuration form will be displayed
Comment #6
David_Rothstein CreditAttribution: David_Rothstein commentedThe patch James linked to contains the main functionality of the "extra" patch that was already attached here. But it doesn't apply cleanly with the other required patches (unless you resolve some conflicts manually). So although we definitely need to get it committed - at which point all the conflicts will work themselves out eventually - you probably don't want to try using it now if your goal is just to get this module up and running.
For that purpose, the instructions at the top of this issue are still the correct ones to use.
Comment #8
bryancasler CreditAttribution: bryancasler commentedIs post #7 spam?
Comment #9
David_Rothstein CreditAttribution: David_Rothstein commentedYes, and it should be gone soon: #1060672: Spammer: harryruiz
Comment #10
paulgemini CreditAttribution: paulgemini commentedsubscribe
Comment #11
Seph CreditAttribution: Seph commentedsubscribe
Comment #12
geerlingguy CreditAttribution: geerlingguy commentedSubscribe. It looks like everything except for #6 under Form Builder is committed; if I'm running the -dev releases of everything, should I just need that patch to get this going now?
Comment #13
David_Rothstein CreditAttribution: David_Rothstein commentedYup, @quicksketch has been committing a bunch of things to Form Builder recently!
It looks to me like #3 and #6 from above might both still be needed. However, I'm not sure if they'll apply anymore, due to the other changes. It would be interesting if someone could try that and report back if it works or not.
Note that in Drupal Gardens, we're currently using a version of Form Builder from early February (basically, the newest code before the recent round of commits during the last few weeks). We haven't gotten around to merging in the latest changes yet. But we know that works, so if the latest dev code turns out not to work, you could always go back to that earlier version and try applying the full list of above patches and it should be able to work then.
Comment #14
pixelsweatshop CreditAttribution: pixelsweatshop commentedsub
Comment #15
newmediaist CreditAttribution: newmediaist commentedThe link for Patch #3 is out of date, there is a newer version of the patch available:
http://drupal.org/node/1010926#comment-4633348
Comment #16
adamdicarlo CreditAttribution: adamdicarlo commented@newmediaist, thank you! I've updated the link in the issue summary.
Comment #17
David_Rothstein CreditAttribution: David_Rothstein commentedNote that although there may be a new patch available that applies against the latest version of Form Builder, the latest version of Form Builder isn't actually likely to work with this module yet. The module has really only been made to work with older development versions of Form Builder (dating from around January or February 2011), and unfortunately no one (that I know of) has gotten it to work with newer versions yet.
Thus, the instructions should maybe say to download an older version of the Form Builder 7.x-1.x code instead (git commit 6436a9e64fc215444c5275f43eeb1d34e182534f is probably around the right time). Consequently, you may have to apply patches that were already committed to Form Builder, or older versions of patches that aren't the most recent posted on each issue, in order to get this all to work correctly.
I was going to edit the issue summary to try to explain that there, but unfortunately, when I tried downloading the latest stable releases of Webform, Options Element, and UX Elements, and combining them with the older version of Form Builder (and the above patches applied) the module didn't seem to work correctly anymore. I'm not sure what's wrong, but unfortunately it means that I no longer know the exact set of instructions/patches to get this module to work.
Note that you can still get a working version of the code by exporting a Drupal Gardens site, so if anyone wants to try that and figure out how to translate that code to a list of working patches, that would be really awesome, but also probably tons of work :(
Comment #18
Johnny vd Laar CreditAttribution: Johnny vd Laar commentedI'm a bit confused on what patches need to be run now on that git checkout.
Would that be only patch 3 and 6?
Perhaps we can place a drush make file here to make things easier to grasp.
Comment #19
mrconnerton CreditAttribution: mrconnerton commentedI tried to figure out a drush make file but couldn't get it 100% so I just opted to create a gardens site, turn webform on and then export it. For the sake of others, I am attaching the modules that were downloaded and work.
I might be able to figure out a make file from theses.
Comment #20
effulgentsia CreditAttribution: effulgentsia commentedHere's the JS and CSS patches that Drupal Gardens is currently running on top of Form Builder 7.x-0.9. Some of this can likely be removed or simplified. The rest will need to be submitted in logical chunks to the Form Builder issue queue. It's gonna take some time to work through and reconcile all of this.
Comment #21
quicksketchA heads up, I have a feeling that the changes from #1405858: Rewrite Webform integration to use new mapping hooks aren't likely to work immediately with the Acquia Gardens version of Form Builder. That set of changes basically modified every single component's form behavior and entirely rewrote form_builder_webform.components.inc. The changes make it so that there's less code redundancy and integrating between Webform and Form Builder is a much more straight-forward task. Essentially instead of needing to directly implement 3-4 different Form Builder hooks per component, there's now just a single "map" hook for each component.
Comment #22
svax CreditAttribution: svax commentedI just tried to set this module up and get it to work, and found that the current description of is no longer valid. Checking out the latest git of all required modules and trying to apply the patches above won't work since many can't be applied any more.
The modules from #19 is in good shape and work nice after some minor fixes.
What's the future of this project? This is an awesome module and hate to see it end here. Many thanks to the people involved.
Comment #23
praba28 CreditAttribution: praba28 commentedhi.....
The field allignment looks not match as original...
here i attach some screenshots... pls help me to solve this
Comment #24
diwant CreditAttribution: diwant commentedHi,
I'm following the 'set this up' in the description of this issue to get the webform alternative UI working but so far I get these errors on build
My makefile looks like
I have more lines for the other dependencies but the patches were only outlined for these so I've only put these.
Comment #25
diwant CreditAttribution: diwant commentedI have commented the lines to patch webform from my above code (the first block) and it seems the form_builder patches don't apply either. Here's what I get:
I'm going to build it sans patches, stick a screenshot of what I see because it compiles but it doesn't work right and I'd like to get it working.
Salud
Comment #26
diwant CreditAttribution: diwant commentedHere is what the create webform page looks like with no patches but with all of the required modules (using UX Elements and not the new Elements, btw).
The arrows indicate which column the element was dragged from, see?
Submitting the create page yields a php error, printed below.
I have to move on to other work. Help me Obi-Wan Kenobi, you're my only hope!
Comment #27
adamtong CreditAttribution: adamtong commentedI have use all lastest version of the dependent modules list below:
Webform Alternate UI 7.x-1.0-alpha6
Form Builder 7.x-1.x-dev (2012-Oct-19)
Options Element 7.x-1.9
UX Elements 7.x-1.0-beta1
Webform 7.x-3.x-dev (2012-Sep-15)
I found I still cannot get this module work well. I found all patches list above should have been committed in the version I list.
Is it any thing I miss to make it work?
Please help.
Thank you.
Comment #28
tajinder.minhas CreditAttribution: tajinder.minhas commentedI am also trying to get workaround for this module, using webform_alt_ui-7.x-1.0-alpha6 but after creating a form by dragging fields and setting there properties its give me nothing then the title of the node. Its gave me an error while setting the fields properties "Form Key is required" but it din't provide the interface where i can provide form key. Is this module working??? or i am missing any step, If any code or patch i am missing please provide the link, if it requires workaround in code that too i can do my client wants a feature something like this http://www.jotform.com/ . Please if anybody can tell me to get this kind of functionality in drupal will be a great favor
Comment #29
mrfelton CreditAttribution: mrfelton commentedSeveral hours later, and I have a drush make file that seems to work. This is based on an export from Drupal Gardens, along with a couple of extra fixes of my own to fix up some undefined index warnings.
Comment #30
sindhuri.rotte CreditAttribution: sindhuri.rotte commentedField form key Required. this is the error system is throwing when trying to edit the field
Comment #31
muschpusch CreditAttribution: muschpusch commentedmrfelton: how do i execute the make file? I tried:
drush make --no-core --contrib-destination=. webform_ui.make
Comment #31.0
muschpusch CreditAttribution: muschpusch commentedUpdate the form-builder-ajax patch link to newer version of patch that applies cleanly to current form builder code.
Comment #32
apaderno