zaus

The plugin uses wp_remote_post, which according to this answer doesn’t support sending files, but according to this hack you can use it if you build the entire HTTP post.

Since it should work with the regular curl, you could use hook #5 to bypass the (what was supposed to be more WordPress-y) wp_remote_post and use curl instead; note that you’d have to format the returned response to match the array normally returned by wp_remote_post.

Since this plugin does a server-side post, unless you’re running the website locally (or can view your server’s traffic) you won’t see the 3rdparty post.

Usually it’s safe to assume that if the plugin shows as ‘active’ in the WordPress Admin, then it’s been added, but you won’t know if another plugin is causing a conflict unless you turn off all the plugins and start adding them back one by one, retesting the 3rdparty post each time. However, if you turn on debug mode in this plugin, you should get an email whenever you make a submission, so that would be the first place to start to see if this plugin is working for you.

Also, I was really confused with this sense of deja vu when I started replying until I realized you already asked this in the old plugin forum http://wordpress.org/support/topic/a-way-to-check-that-plugin-is-really-added-to-a-web-site

If I remember correctly, most recent Drupal forms (depends on the version) have essentially the same originator validation as wp_nonce, so you probably wouldn’t be able to ‘spoof’ a post using this plugin.

You can always try; it’s probably possible to disable that validation in the form admin. The easy way to get the form action URL is to create the Drupal form, then right-click and ‘view source’ (CTRL+U Chrome/FF) or ‘inspect element’ to find the <form tag and look for the action attribute. Then copy the THENAME out of each <input name='THENAME'... as the 3rdparty mapping field name.

Sorry for the delay. You could write another hook similar to the Forms 3rd-party XPost, hooking later, to manipulate the $args['body'] string returned by the plugin. Something like:

function my_cf7_xml_override($args, $service, $form) {
    $body = $args['body'];

    // pull out relevant contents via regex, substring, etc
    // re-wrap and combine back into body

    $args['body'] = $body;
    return $args;
}
add_filter('Forms3rdPartyIntegration_service_filter_args', 'my_cf7_xml_override', 13 /* later than original xpost plugin */, 3);

The better solution would be for XPost to interpret 3rdparty field names with a slash (or something else) to indicate element nesting, so you could map to PERMISSIONS/USERNAME rather than USERNAME. Can you create a new issue and link back to this thread?

So sorry for the delay. I see you mapped the ‘Email Address’ form name correctly, but there are other hidden fields in that form as well — maybe you need to provide some or all. I’ll repost the form section specifically:

<form action="" method="post">
    	<div><b>Email Address</b></div>

    	<div>
    		<input type="text" maxlength="100" name="Email Address" id="Email Address" value="" size="37" />
    	</div>

    	<input type="submit" value="Submit" />

    	<span style="display: none;" id="post_code"></span>
    	<input type="hidden" name="__successPage" id="__successPage" value="http://pages.s6.exacttarget.com/page.aspx?QS=472529ec60bdf32a451a85f056ddb68a8380966ce9c6ee9f9c606cb24f31812a" />
    	<input type="hidden" name="__errorPage" id="__errorPage" value="" />
    	<input type="hidden" name="__contextName" id="__contextName" value="FormPost" />
    	<input type="hidden" name="__executionContext" id="__executionContext" value="Post" />
    </form>

Any luck?

Any luck?