When installing on WP Engine, you will need to contact WP Engine support and request that they turn off the “redirect_bots” setting, and purge the cache. If this setting is not disabled, then it will not be possible to send HTTP POSTs to your app, as the WP Engine server will intercept and stop them from succeeding. You’ll need to send a support ticket to WP Engine Support and ask them to allow your posts to contain variables.
This function automates the process of scanning for subscriptions that are active, but are at or past their end date. Infusionsoft does not automatically provide this capability.
If you are receiving a 300, 400, or 500 series error when trying to do an HTTP POST from Infusionsoft, these errors are usually easily fixable, and we’ll walk through them below. If you are receiving a 500 error, then something is causing a server crash and it will require some investigation. We’ll go through the common errors below in order, and touch on how to solve them. The most common sources of errors are:
Memberium strives at all times to maintain maximum compatibility with WordPress Core and Plugins. However there are situations where plugins may bypass or override core functions, resulting in a loss or change of functionality.
The Infusionsoft HTTP POST is a powerful tool in your Infusionsoft Membership site automation toolkit. HTTP POSTs are a simple API that can be used between web servers to allow them to signal each other that something has happened, or than an action has been taken.
Memberium requires the ability to send and receive data to the web to operate, both to communicate with your Infusionsoft app and to connect to our License Server. When operating in a locked down or high security environment, you may need to take extra steps. If you do not have direct access to send data to the internet, your IT Department likely has an HTTP Proxy such as Squid, or NginX configured.
If you come across an HTTP POST error message like org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 5000 ms, it is most likely that your hosting provider is blocking any posts from Infusionsoft because their IP address appears on certain web spam bot lists.
Make sure the test member’s email isn’t the same as an existing wordpress admin email. Log ins for test members can’t use the same email addresses as wordpress admins.
Check the password field in a test member record in user’s Infusionsoft app. See if a password is saved in the field.
If no password is present, make sure there’s an http post happening after a new member submits a web form or order form, and make sure it correctly has your http post Auth key added. If it’s not, add &auth_key=yourcustomauthkey to the end of any http posts being sent to your wordpress site.
An example of a correct http post with an auth key properly added is:
|
1 |
http://yourdomain.com/?operation=makepass&overwrite=no&adduser=yes&auth_key=yourcustomauthkey |