View this article for step-by-step instructions on upgrading MemberMouse.
Summary of New Features, Enhancements and Bug Fixes
- Integrated the Authorize.Net Accept.js token exchange into the Authorize.net CIM integration. With the Accept.js library integrated, payment data is sent directly to Authorize.Net and does not reach your servers. Accept.js replaces Direct Post Method (DPM) with a modern implementation that doesn’t require a post-back. Learn more about Accept.js. (1455)
- Updated the Facebook SSO Login to account for the removal of support for Graph API 2.2. Learn more about our Facebook SSO feature.(1486)
- Improved the plugin deactivation process to allow for more failed attempts in contacting the licensing server before deactivation and to include sending an email alert to the site administrator prior to deactivation. Learn more about the MemberMouse license cancellation and deactivation protocol. (1477)
- Addressed issues causing the creation of complimentary accounts. Accounts are no longer made to be complimentary if they are unlocked after being locked. Additionally, when an order is abandoned, and then the same user successfully completes a purchase, complimentary access in no longer given. (1482, 1443)
- Addressed an issue occurring when using alternate products. Previously, if Product A has been set as an alternate product for a Product B with a trial, Product A was not able to be deleted. (1483)
- Generic shortcodes and other non-SmartTags can now be processed when included in Push Notification emails. (1485)
- Addressed issue where drip content access to a bundle differed based on whether the bundle had been purchased separately or assigned to a membership level. (1489)
- The bundle management section on the access rights tab of the member details is now visible even when there are no active bundles. (1467)
- Updated the error tag and form message SmartTags to be run through the localization process. (1441)
- Modified the columns in the MemberMouse tables to contain fewer characters so that INNODB can index them accordingly with its max key size limit without causing a fatal error when trying to install MemberMouse. (1434)
- Addressed an issue on the checkout form when two or more payment methods were offered. The isDefault parameter was being ignored and whichever payment method was first on the page was used as the default payment method. (1464)
- Addressed an issue where links from the My Account page and certain form button SmartTags did not trigger the loading of Stripe.js and the token exchange framework. (1479, 1387)
- Adjusted the custom fields so that a radio button can be marked as a required field. (1456)
- Optimized the Reporting Suite CSS for mobile view. (1426)
- Addressed issue where the processing overlay message that shows up after clicking submit on the checkout page doesn't appear in Safari browser. (1447)
|May 11, 2017||Initial release||Manual upgrade of the plugin required|
|May 15, 2017||Resolved issues 227-1, 227-2, 227-3||Manual upgrade of the plugin required|
|May 24, 2017||Resolved issues 227-4, 227-5||None; unless you're explicitly experiencing|
issues with PayPal, then a Repair Install is required.
MM menu: General Settings > Manage Install >
|July 22, 2017||None|
|October 20, 2017||None|
|October 27, 2017||None|
|March 7, 2018||Billing handler updated to check for and restart skipped rebills||None|
|May 16, 2018||Addressed issue with coupon code AJAX||None|
|August 22, 2019||2.2.7-108||Compatibility update for AWeber service||Manual upgrade of the plugin required|
If you are experiencing any of the below issues, please contact our support team so they can recommend a next action as well as keep you updated on a resolution.
There are no current known issues.
Resolved IssuesIf you're experiencing an issue that has been resolved then download the latest version of the MemberMouse plugin using the link at the top of this page and perform a manual upgrade.
227-1 - Error in the payment scheduler endpoint
This has the potential to effect rebill processing only. In these cases, the payment information reaches our scheduler but fails when sent to the payment processor.
227-2 - 'Days as Member' calculation displaying as '0'In the Member Details interface, the 'days as member' number next to the LCV displays as zero regardless of how long the person has been a member. The protected content still shows up as expected for smarttag decisions and access rights, however. The displayed number is the only thing that is currently effected.
227-3 - Facebook social login does not complete
When attempting to log in from Facebook, a 500 error is returned.
227-4 - With PayPal, products with a paid trial aren't registered correctlyProducts with a paid trial show as free trials when redirected to PayPal. The subscription is registered correctly in PayPal but shows as 'pending activation' in MemberMouse.
227-5 - With PayPal, products with a coupon discount aren't registered correctly
When a coupon is applied to discount the initial payment of a subscription, the discount is not passed on to PayPal.