tet3

If you want to test against a demo environment, you can get a free Developer instance at https://developer.force.com. Developer instances work like production instances (but have pretty tight user and data limits), but would thus be accessible by this plug-in.

That said, it’s pretty tough to corrupt a Salesforce database. I mean, you can pour a lot of dirty data in there with forms and this add-on, and that could affect your reporting, and all that comes with poor data integrity, but you’re not going to “break” Salesforce by creating new records with forms and this add-on. As long as you’re not writing into record ID fields, you shouldn’t write over existing data either, just create new records.

Yes, this. The fields would either have to be populated by a hidden field, or if you’re sending out an email that links to your form, you could fill the form with a URL parameter that’s dynamically generated with the right ID by your email program.

I got this same error. On a Dreamhost shared hosting account, it was fixed by changing the PHP version on the site from v5.2 to v5.3 – I guess they included SoapClient by default in their v5.3 builds, but not v5.2.

How you add it if it’s not built-in by default on your host is going to depend on the host, the version of PHP your site is currently running, and the amount of access you have (shared hosting, VPS, dedicated, etc.) Forms -> Settings lists your current version numbers for PHP, MySQL, WP and GF at the bottom (why isn’t this in the normal WP admin interface?!)