I've seen postings that began the same as my issue...someone needed to use CAPTCHA with the form they were sending directly to Salesforce, and the need to validate the CAPTCHA thus 'broke' being able to send it. I saw a few examples of people solving their problems using CURL.
So, I set CURL to 1 in the form plugin settings. I then clicked the form and CURL and set each field to the same name that was showing (since the names were from the form field names, which were already working with Salesforce).
Now none of the leads sent from the form show up in Salesforce (they all showed up prior to adding changing to CURL).
On our site I created a test page that simply did a php print_r($_POST), and pointed the CURL target URL to it, and all the form data shows up, with all the correct Salesforce field names, including the hidden ones.
Is there something else I need to change to get it to work with Salesforce? I would have thought the fact that it is CURL would be transparent, but maybe not? As far as they're concerned, it's nothing to do with them, though they haven't specifically checked to see if there's a problem using CURL with them (and this was the Premier support people...level 1 never heard of CAPTCHA or CURL).
So, I set CURL to 1 in the form plugin settings. I then clicked the form and CURL and set each field to the same name that was showing (since the names were from the form field names, which were already working with Salesforce).
Now none of the leads sent from the form show up in Salesforce (they all showed up prior to adding changing to CURL).
On our site I created a test page that simply did a php print_r($_POST), and pointed the CURL target URL to it, and all the form data shows up, with all the correct Salesforce field names, including the hidden ones.
Is there something else I need to change to get it to work with Salesforce? I would have thought the fact that it is CURL would be transparent, but maybe not? As far as they're concerned, it's nothing to do with them, though they haven't specifically checked to see if there's a problem using CURL with them (and this was the Premier support people...level 1 never heard of CAPTCHA or CURL).
Hi,
how did you see the print output ?
Cheers,
Max
On our site I created a test page that simply did a php print_r($_POST), and pointed the CURL target URL to it, and all the form data shows up, with all the correct Salesforce field names, including the hidden ones.
how did you see the print output ?
Cheers,
Max
My memory is a little foggy at this point, but I believe it was because I turned on debug, and there was a display that showed the data twice, once in print_r format. I assumed that the first set of data was what CURL was sending, and the second was the print_r from the invoked page.
aha, this is fine then, I'm not sure where is the problem then! :?
Here is Salesforce's take on connecting to them via CURL:
Thank you for your patience in this matter. i have consulted with our tier 3
support and at this time there is little that we can do to assit you further
in this matter. Our Web2Lead servlet is uncomplicated and accepts the
values of data if passed to us correctly. As noted, I created and used the
UI generated customer Web2Lead form, Lead was created without issue so
proper operation has been established.
Support does not provide troubleshooting for Customer's Custom HTML Web2Lead
however we do have a few avenues that you can take.
Paid Services:
1. They can engage our ProServ group to scope and evaluate the integration.
2. They can engage Developer Support to scope a Small Project
Do keep in mind that if the you leverage our Generated Web2Lead that works
for comparison, you should be able to determine what custom code is
responsible for preventing the submittal to SF (this is key) slowly adding
pieces of their code back and testing to see what breaks it.
At this time I will be closing your case. Please let me know if there are
any further questions.
Thank you for your patience in this matter. i have consulted with our tier 3
support and at this time there is little that we can do to assit you further
in this matter. Our Web2Lead servlet is uncomplicated and accepts the
values of data if passed to us correctly. As noted, I created and used the
UI generated customer Web2Lead form, Lead was created without issue so
proper operation has been established.
Support does not provide troubleshooting for Customer's Custom HTML Web2Lead
however we do have a few avenues that you can take.
Paid Services:
1. They can engage our ProServ group to scope and evaluate the integration.
2. They can engage Developer Support to scope a Small Project
Do keep in mind that if the you leverage our Generated Web2Lead that works
for comparison, you should be able to determine what custom code is
responsible for preventing the submittal to SF (this is key) slowly adding
pieces of their code back and testing to see what breaks it.
At this time I will be closing your case. Please let me know if there are
any further questions.
Hi, please contact me through the "contact us" page and give me admin login and I will run a test to see if I can find anything myself!
Max
Max
This topic is locked and no more replies can be posted.
