I love this module - it is making our lives so much easier! The only problem I have with it is that the webform module no longer handles the submission of the form - so you don't get an email sent from the webform module, and the results for the forum submission are not being collected.
I've attached a patch (against the Drupal 5 version of the module) which makes a couple of small changes, instead of just changing the form action an additional submit handler has been added, this pings a POST request over to your Sugar using drupal_http_request - control is then handed back to the webform module and the form is handled as per any other normal webform.
Cheers,
Mike
Comment | File | Size | Author |
---|---|---|---|
#10 | sugarwebform.module.txt | 12.97 KB | drupalninja99 |
#9 | sugarwebform.module.txt | 13.05 KB | drupalninja99 |
#8 | sugarwebform.module.txt | 13.16 KB | drupalninja99 |
#7 | sugarwebform.module.txt | 11.16 KB | drupalninja99 |
#5 | sugarwebform.zip | 8.64 KB | webchuck |
Comments
Comment #1
metareason CreditAttribution: metareason commented+1 for this patch - just started writing the same kind of thing so that the webform validation isnt skipped then found this already written.
Seems to work so far, forms are validated, emailed and are also going neatly into Sugar.
Thanks!
Comment #2
pkrekelb CreditAttribution: pkrekelb commentedWow, this is exactly what I need. I am actually trying to use sugarwebform to post webforms to another CRM (Eloqua), but I need this same functionality for forms such as for registration. I still need the fields to get posted to Drupal, but sent along to Eloqua as well.
Eloqua just has a few hidden fields I need to add.
Our site is Drupal 6. How different would this technique be in a sugarwebform-like module?
Thank you !
-Patrick
Comment #3
mdixoncm CreditAttribution: mdixoncm commentedThe principle would be the same, just the syntax around the form handling would differ a little - if I get chance over the next week I'll roll a Drupal 6 version of the patch too (it's about time we moved our site onto 6 anyway!)
Cheers,
Mike
Comment #4
pkrekelb CreditAttribution: pkrekelb commentedThat would be great. I may try to do the same, and if I do, I'll post it up.
Comment #5
webchuck CreditAttribution: webchuck commentedI actually found this patch a little too late, so I had already written up my own solution around the issue. I'll go ahead and post it here for anyone else. Mine is not quite as elegant as the above... I ended up rewriting the SugarWebform module entirely. But I like the simplicity of the solution because it no longer requires changes to Sugar's file system, a database table created or additional fields for the node form. You'll also notice that I removed the custom fields section, only because I never understood how they worked and didn't find them necessary.
The installation and usage instructions are found in INSTALL.txt. It uses PHP's cURL, so you'll need that on your server.
Hope this helps some other poor soul suffering with this integration.
Comment #6
drupalninja99 CreditAttribution: drupalninja99 commentedSo should I use your module or the patch? Also I'm using the 6 version which is more updated so I'm really confused as to what is the path of least resistance. I could use your module and upgrade it manually integrate that patch, not sure what to do.
Comment #7
drupalninja99 CreditAttribution: drupalninja99 commentedHere is the d6 version of the patched module.
The only thing I haven't been able to figure out is how to upgrade the validation for the custom fields.
UPDATE: OK I tested this module and it didn't work so try my new module update below
Comment #8
drupalninja99 CreditAttribution: drupalninja99 commentedOK I've got an updated version of the d6 module that works pretty well I think. We are now using it on http://mediacurrent.com. I have integrated the patch drupal_http_request patch so that now the redirect works fine and also I added a feature for handling custom fields.
First of all I don't really understand the custom fields box on the settings page. It doesn't make sense to me at all.
What I ended up doing is making any component field key that isn't a standard CRM field be appended to the description. This is a little rough but I got it to work.
So my submit form function looks like this:
It needs some work I'm sure but it works for me. It's a nice 1-size fits all solution for us bc now we can turn on CRM integration with very little configuration. For the standard field names I just have to make sure the component key (in advanced settings) matches the key I see in the sugarwebform_fields.inc file. After that any component with a different field key goes in the description. Works really well. Hope this helps!
This is a drupal 6 version.
Comment #9
drupalninja99 CreditAttribution: drupalninja99 commentedUPDATE: fixed big flaw, use this module instead.
Comment #10
drupalninja99 CreditAttribution: drupalninja99 commentedmore fixes...
Comment #11
axon CreditAttribution: axon commentedWow for someone new to Drupal.. and having istalled Drupal 6.x.. can anyone tell me how can I implement all those patches?
tks
Comment #12
axon CreditAttribution: axon commentedjaykali what Sugar URL are you using to post? index.php?entryPoint=WebToLeadCapture