The Turkish translation ships with the plugin​

Installed from WordPress.org, the plugin appeared in English on a Turkish site: the release package left the compiled translation files out, and no WordPress.org language pack existed to take their place. They are back in the package. On WordPress 6.8 and later the whole plugin is Turkish. On 6.6 and 6.7 the settings screen is Turkish, but text that comes from the plugin's PHP code, such as the menu label, stays in English — see Known limits. Other languages can be added on translate.wordpress.org.

Cache warnings no longer come and go​

The two cache-compatibility warnings used to clear, together with every administrator's snooze, whenever a page could not show the problem — a customer opening the cart, or you browsing the store while logged in — and the next page view brought them back. Each check now reaches one of three answers: the problem is there, the page is clean, or this page cannot tell. A warning keeps naming the first page the problem was seen on, and clears only when that same page renders without the problem, when that page no longer exists, or when you save cache compatibility switched off. Snooze until this changes now holds, and both warnings say when they clear. How each warning works is described in the FAQ.

2.2.1 on GitHub

What changed​

To detect a visitor's currency, the plugin asks WooCommerce which country the visitor is in. When WooCommerce had no local MaxMind database, that question could fall back to a remote geolocation service, which received the visitor's IP address. WooCommerce's own storefront code switches that fallback off; this plugin called the same function with its defaults, so for this feature the fallback stayed on. 2.2.0 switches it off too. Detection now uses only CloudFlare's country header or a MaxMind database on your own server — nothing about the visitor leaves your server.

Geolocation starts off on new installs​

Working out a visitor's country from their IP address is data processing, so on a new install it is now something you switch on deliberately, on the Advanced tab. Stores that update keep the setting they already had — nothing is switched off for you.

⚠️ If you use geolocation without CloudFlare or MaxMind​

Detection will now find nothing instead of asking a remote service, and visitors keep your base currency until they choose one. To keep the feature, add a free MaxMind GeoLite2 licence key under WooCommerce > Settings > Integration > MaxMind Geolocation. WooCommerce then downloads the database and keeps it up to date, and every lookup happens on your own server. The Advanced tab now states what geolocation needs, whether or not it is switched on. Details: Advanced settings and Currency detection.

2.2.0 on GitHub

Before you update: three things changed name or shape​

CSS classes. Every class the switcher uses changed its prefix from mhm-cs- to mhmcs-: .mhm-cs-switcher is now .mhmcs-switcher, .mhm-cs-dropdown is now .mhmcs-dropdown, and so on for every class. No alias is kept for the old names, so custom CSS or JavaScript written against them stops matching once you update. The full list is on the CSS classes page.

The exchange-rate fallback. When the main rate source cannot be reached, the plugin now makes a single request to the European Central Bank's daily reference feed. The two-stage chain added in 2.0.0 — Currency API, then Frankfurter — is gone. Coverage does not change, roughly thirty currencies, because the ECB was already the last step of the old chain. If your code filters the fallback address, the mhmcs_fallback_rates_url filter's $source argument is now always ecb. See Managing currencies.

The public rates endpoint. The unauthenticated GET /mhmcs/v1/rates REST route was removed; it repeated what the page already shows in its prices. The authenticated routes the settings screen uses are unaffected. See the REST API reference.

Quieter notices, in the right place​

• The two cache-compatibility warnings can be snoozed. Snoozing clears a warning only for the problem detected at that moment: if a new, different cache problem appears later, the warning comes back instead of staying silent for good. Later: in 2.2.1 a snooze holds until the warning clears — see the 2.2.1 notes.
• The WooCommerce-missing notice and the two cache warnings now appear only on the screens where they belong instead of on every admin screen, and only to people who can act on them: users who can activate plugins for the first, users who can manage WooCommerce for the other two.

Also in this release​

• The settings migration for installs that never updated past the 2026-03 release was removed, together with the matching old-option branches in the uninstall routine. Every version released since 1.0.0 (2026-07) is unaffected.
• The last mhm-cs-, mhm_cs_ and mhm_currency_switcher_ names left in the plugin were renamed to the mhmcs prefix.
• The release package no longer includes the compiled translation files. Later: 2.2.1 puts the Turkish translation back into the plugin — see the 2.2.1 notes.

2.1.0 on GitHub