The v1.4.x series started with a big feature drop — WooCommerce translation, translated slugs, the built-in language system. What followed was a long stretch of filling in the gaps: edge cases that only show up on complex sites, compatibility problems that are tricky to reproduce, and a handful of power features that users kept asking for.
Here’s a rundown of everything we shipped from v1.4.20 to v1.4.55.
Elementor Template Reliability
This was the most persistent pain point we tackled in this range. Sites using Elementor headers and footers would hit a frustrating problem: after translating a template, the translated copy would inherit the original’s display conditions. That meant your French footer could start showing up on every language simultaneously, or your translated header would appear where it shouldn’t.
We fixed this in v1.4.36 and v1.4.38 by stripping display conditions at copy time. Translated templates now start clean — no inherited visibility rules from the original.
The second issue was nested templates. If your header contained a reusable Elementor section, we were only swapping nav menu IDs — the nested component itself wasn’t being replaced with its translation. V1.4.40 fixes this by traversing and swapping nested reusable components inside headers and footers.
We also sorted out the editor vs. frontend split (v1.4.39–v1.4.44). Previously, editing a header in Elementor could flip to the translated version mid-session. Now the editor always shows the original, and the frontend serves the right language version independently.
On the usability side: each template in the settings panel now has its own translate button (v1.4.37), and template processing was moved to per-template AJAX requests (v1.4.35) so a slow server can’t time out the whole batch at once. A new “Translate Advanced Templates Only” toggle (v1.4.53) gives you finer control over which templates get processed.
WooCommerce Compatibility
WooCommerce generates a lot of URLs that need to be language-aware: product pages, category archives, My Account endpoints, breadcrumbs — each has its own routing quirks.
The most-reported issue was product pages returning 404 when a default language prefix was enabled. This came down to rewrite rule ordering: our rules needed to fire before WordPress’s CPT rules, which they now do (v1.4.29).
My Account was trickier. Pages like /en/my-account/orders/ or /en/my-account/edit-address/ were returning 404 because WooCommerce registers its endpoints separately from the main page, and our prefix rules didn’t cover them. V1.4.50 and v1.4.51 add explicit rewrite rules for all registered WooCommerce endpoints.
Product category archives (v1.4.45–v1.4.46) and breadcrumbs (v1.4.27) are also fixed. We also added a product fallback option: if a product has no translation yet, you can now show the default language version rather than a 404.
Language Prefix Routing
Enabling a language prefix for the default language — so your site serves /en/about/ instead of /about/ — sounds simple but cascades into a surprising number of edge cases. We chased down most of them in this range.
- Single posts with custom permalink bases like
/blog/%postname%/were returning 404 — fixed in v1.4.32. - Language root URLs like
/it/without a translation were looping intoERR_TOO_MANY_REDIRECTS— fixed in v1.4.34. - Paginated archives like
/fr/blog/page/2/were 404ing — fixed in v1.4.49. - Custom category/tag base slugs set in Settings >Permalinks weren’t respected with a language prefix — fixed in v1.4.47.
- Sites where WordPress translates the category base itself (e.g., French → “categorie”) were also broken — fixed in v1.4.48.
New Features
A few genuinely useful additions landed alongside the bug fixes.
Bulk delete(v1.4.52) was one of the most-requested changes. The translations list now has checkboxes — select several entries and delete them all at once, instead of clicking through a long list one translation at a time.
Bundled SVG flags (v1.4.28): the language switcher no longer depends on an external CDN for flag icons. All 86 flags ship with the plugin, which also makes the switcher work on sites with strict CSP headers.
Custom language name formats(v1.4.28) let you control how each language appears in the switcher — native name (Français), English name (French), uppercase code (FR), or lowercase code (fr). Previously this was all-or-nothing.
We also split the Settings > Templates panel into Active and Advanced sections (v1.4.26), added a real-time switcher preview that renders actual frontend output (v1.4.26), and filled in 116 missing translation strings across all 9 supported UI languages (v1.4.28).
Translation Quality
Two small but annoying bugs got fixed early in this range. Line breaks inside Elementor widget content were disappearing during translation (v1.4.20, v1.4.21) — you’d write a heading with a deliberate line break and it would come out as a run-on sentence in the translated version. That’s fixed.
Menu translation was also incomplete in some setups: only menus assigned to theme locations were being translated and swapped. Now all registered menus are handled (v1.4.22).
Everything Else
- Admin notice added when TranslatePress is active, explaining the incompatibility and pointing to the built-in language system (v1.4.21)
- Language code debug panel to diagnose template language mismatches without digging into the database (v1.4.33)
- Fixed an invalid UTF-8 byte in readme.txt that was corrupting the plugin description on WordPress.org (v1.4.30)
- Fixed emoji characters in the plugin description that caused display issues on WordPress.org (v1.4.55)
- Build scripts now exclude development files from the published ZIP, keeping it lean (v1.4.28)
V1.4.55 is available now via the Plugins screen. If you’re on an earlier v1.4.x, the Elementor display condition fix is the main reason to update — it resolves the most-reported template issue we’ve seen on complex sites.
If you run into anything weird, reach out. Most of the fixes in this range started as a single support ticket.
Try Meep AI Translator
Start free with 1,800 words/month or grab the Agency Lifetime Deal for unlimited translations.
Questions or feedback? Reach out at support@meeptech.com or leave a review on WordPress.org.