WishList Member v2.91 Build 3138

New

• AutoResponder Integration
  • Added Drip AutoResponder Integration.
  • Updated MailChimp to support v3.0 of its API.

Bug Fixes

• AutoResponder Integration
  • Infusionsoft
    • Fixed broken integration if shopping cart integration is disabled.
  • Aweber API
    • Fix the error Fatal error: Invalid static property access: AWeberAPI::_collectionMap which makes the Aweber API integration page blank on HHVM web servers.
• Shopping Cart Integration
  • Stripe
    • Payment Form – Fixed issue where product price is being removed when payment button is clicked.
  • Authorize.Net Automatic Recurring Billing
    • Fixed issue where changes made on the products’ settings are not being saved and product’s name is blank.
  • Paypal Payment Standard
    • Fixed issue where on some servers or some WordPress Installs, the Paypal Payment Standard Integration page doesn’t load completely due to Javascript Conflicts where jQuery’s $ sign is not defined.
• Login
  • Fixed issue where logging in on Microsoft Edge and Internet Explorer with cookies disabled does not redirect the member to the default WordPress Login page and it refreshes the page that has the [wlm_loginform] shortcode
  • Fixed issue where “Cookies Disabled” error message is not displaying on Firefox Web Browser.
• Fixed BBPress protection
  • Fixed issue where Topics and Replies created by members are not protected even if the parent Forum is protected. Topics and Replies created by members on the frontend will now automatically inherit the protection settings of the parent Forum.

Updates

• AutoResponder Integrations
  • Mailchimp Integration
    • Supported MailChimp API v3.0. Clients using the MailChimp integration will have the option to migrate to MailChimp’s new API
• Shopping Cart Integrations
  • Paypal Payment Standard
    • Added support to cancel suspended recurring payments.
• Custom Post Types
  • Added Default Protection support for Custom Post Types in Settings > Custom Post Types
  • Custom Post types added via the frontend (eg. Topics, replies, forums) will now automatically be protected if “Default Content Protection” is set to “On” in Settings > Protection Defaults
• License Activation
  • Removed the email field as we no longer need it at this point