zaus

Followup discussion regarding SOAP post: https://github.com/zaus/forms-3rdparty-integration/issues/1

That’s not very descriptive, but I’m hoping you’re getting the same PHP 5.4 issue, which should be fixed in v1.4.6.

Hi,

First, I just submitted a fix for the getallheaders error you’re getting from the service test url.

But if you turn on ‘debug mode’ and put your email in the appropriate global setting, you should get full details of the service request, including the exact form fields being posted by GF in the *** Post (Form) *** section, which you can use to determine your mappings.

To map to GF fields, it should be the html ‘name’ property of each field, which in my version of GF follows input_1, input_2 etc; you can get the number from the “Field ID” shown in the GF admin page for each field.

I’m sorry, I really have no idea what you’re asking.

The workflow of the plugin is:
1. You specify specify the admin email to receive responses
2. You enable “Debug Mode” — these will be sent to #2
3. You create a service and attach it to specific forms
4. The service will submit to an indicated url; let’s say you use the included ‘service_test.php’
5. You set up service mapping: field_x becomes submission_a, etc
6. Someone submits the attached form
7. The contact form plugin (CF7 or GF) behaves regularly, sending confirmation emails, printing a message to the screen, etc
8. The 3rdparty-Integration plugin will, at the same time, perform a form POST to the service url from #4, using the mappings from #5 to turn the contact form plugin submission into a service request
9. If the Integration plugin encounters an error with the service request (i.e. a complete failure of the response, or the lack of the specified “success” text) it will send a failure notice to the admin email, and it may update the contact form plugin notification message with a generic “could not send the reply” type message; in the case of CF7 it will print a developer-tools console warning, but for GF it should append to the msg shown on screen or include in the redirect url.
10. Regardless of success or failure, because you enabled Debug Mode in #2, you will get an email detailing the service, the submission, the mapped request, and the response.

After re-reading what I just wrote, maybe you mean in #9 it should have displayed a failure message but did not — is that what you’re talking about?

Timeout setting is available in the “newer version” of this plugin http://wordpress.org/plugins/forms-3rdparty-integration/

You could create a queue using Transients and wp_cron, maybe?
* http://codex.wordpress.org/Transients_API
* http://codex.wordpress.org/Function_Reference/wp_cron

You would have to add items to the queue using the failure hook Forms3rdpartyIntegration_remote_failure (newer plugin) to examine the response for ‘timeout’ errors and create transients/schedule cron.

Did you see the screenshot included in the /3rd-parties/salesforce folder? Unless Salesforce has changed since I wrote the plugin (which was a while ago) it should be the oid field is where you indicate your salesforce account (as indicated in the screenshot by the red arrow “unique account id”).

Also, I no longer support this plugin (and barely have time to support the newer version) but try the newer version http://wordpress.org/plugins/forms-3rdparty-integration/ and submit future issues through GitHub as well https://github.com/zaus/forms-3rdparty-integration.

When you say “don’t ever see the services_test.php outputting to the screen”, what do you mean? Debug Mode only sends emails to whatever address you’ve entered in the admin section; it will send an email of the service settings, the form post, the remote post, and the remote response. Turning on Debug Mode means you always get a ‘debug email’, rather than only when a failure is detected from the remote request.

The services_test.php page is a provided debugging tool so you can examine the post without sending test messages to your actual service — its response will contain the GET/POST/HEADER data it received from the remote request to help you figure out if you’re missing or mis-configured a mapping.

Should I explain this better somewhere? In what way can I make this more easily understandable?