AccessAlly 4.9.3
Released September 15, 2026
Bug fixes
- We fixed PayPal subscriptions being abandoned after a single failed collection. When a PayPal payment failed, AccessAlly marked the subscription Payment failed and stopped checking it again. PayPal, by design, adds the unpaid amount to the next scheduled payment and usually collects it, but the site never found out: the payment was not recorded, the failure tag stayed on the member, the success tag never arrived, and the sales reports stayed frozen. The member carried on paying while shut out of the content they had paid for. An outstanding balance on a profile that PayPal still reports as active is now treated as a payment that is due rather than one that has failed, so the subscription keeps being checked, and Payment failed is reserved for a profile PayPal itself has cancelled or suspended. Subscriptions already sitting at Payment failed are picked up again automatically, so once PayPal collects, the payment is recorded, the failure tag comes off and the success tag applies without anyone having to intervene.
- We fixed the Refresh option on the subscription detail screen being unavailable on exactly the PayPal subscriptions that needed it. It is now offered on these subscriptions, and it can no longer record the same payment twice if it is used at the same moment as the hourly check.
- We fixed order bumps toggling twice from a single tap on a phone. One tap fired both the touch and the click the browser synthesizes after it, so the bump was added and then immediately taken off again, which left buyers unable to remove a bump once it was on. A scroll that began with a finger resting on the bump could also add one that was never wanted. Desktop checkouts were not affected. A tap and a scroll are now told apart, and the duplicate click is ignored.
Known issue
On some sites the WordPress Plugins screen shows a fatal error instead of loading. It can also appear when a security plugin runs a full scan, because that asks WordPress for AccessAlly’s plugin information. Your site, your members and your data are not affected, and nothing on the front end stops working, but the Plugins screen itself becomes unusable while it happens. The cause was introduced in 4.9.0, we have identified it, and a fix is in progress. If this is affecting you, please contact our support team and we will get you sorted in the meantime.


