Troubleshooting

Things that look like a fault in Milo and are not always one, with what to do about each.

After installing Milo, WordPress keeps sending me to the WooCommerce payments settings

You click something in the admin, a product for instance, and land on WooCommerce’s payments screen instead. The address ends with something like:

?page=wc-settings&tab=checkout&section=woocommerce_payments&wcpay_subscription_disabled=1

That redirect comes from WooPayments, not from Milo. The wcpay_ prefix is theirs.

WooPayments ships its own built-in subscriptions feature. When it detects another subscriptions plugin on the site, it switches that feature off and sends you to its settings page to say so. The outcome is the one you want, since two subscription engines billing the same customers on the same store would be worse, but it announces itself with a redirect rather than a notice, which is easy to read as Milo breaking your admin.

It is meant to happen once. Load that page, then carry on. If the redirect repeats, reach the product a different way in the meantime, through Products in the WooCommerce menu rather than from Milo, and let us know: we will help you take it up with WooPayments.

“View details” on an available update says “Plugin not found”

Older versions of the Milo add-ons handed that request back to WordPress, which asks wordpress.org, which has never heard of a privately distributed plugin.

Update any one Milo add-on and it stops for all of them. The licence client is bundled in each add-on but defined only once, by whichever plugin loads first, so a single updated add-on fixes the popup site-wide, including for add-ons you leave on their current version.

Every admin page sends me to the Milo setup wizard

Fixed in 1.8.11. Before that, an unfinished setup wizard redirected every page in the admin back to itself, so editing a product or opening any other screen landed on the wizard.

Update to 1.8.11 or later. If you cannot update straight away, opening Subscriptions and either completing the wizard or using its Exit link stops the redirect permanently.

The Subscriptions tab in My Account returns a 404

This happens on sites where Milo was activated before WooCommerce, because the account endpoint’s rewrite rule was never written.

Sites in that state repair themselves from 1.8.8 onwards, with nothing to do and no need to re-save permalinks. On an older version, updating fixes it; visiting Settings then Permalinks and saving once also does.

Renewals are not being charged on a staging or development copy

That is on purpose. Milo detects a cloned site and refuses to process renewals on it, because a clone carries the production database, real customers and real payment methods, and a renewal there would charge them.

The subscription screens will still show what a renewal would do. If you genuinely need to exercise the renewal path on a copy, do it against test payment credentials, never against a clone still holding live customer data.