What’s new in WPML 5.0 at a glance:

• A redesigned admin, with everything under a single WPML menu
• Automatic translation on by default for new sites
• Free re-translation of edited content, within the words you’ve already paid for
• One-step setup for regional language variants
• Translate Everything Automatically works without having admin open
• Taxonomy translation directly from the Translation Dashboard
• Consistent editing rights for local translators
• WCML 6.0 realigned to the new WPML menu

A Redesigned Admin Experience

The WPML admin has been rebuilt from the ground up. Instead of scattered menu items across the WordPress sidebar, everything now lives under a single WPML menu with five clear sections: Translations, Settings, AI Translation Billing, Support, and Activate & Update.

The Translation Dashboard now has a tab menu at the top with quick links to all the areas you need most: Menus, Strings, Taxonomies, Translation Jobs, Glossary, and more.

Reorganized Settings Section with Search

The Settings section now includes a search bar, so you can find any option without knowing exactly where it lives.

Translate Everything Automatically Is Now the Default

For new sites, Translate Everything Automatically (TEA) is now the default translation mode. When you set up WPML on a new site, TEA is what you get out of the box with no extra configuration needed to start translating your entire site automatically.

Cut-Off Date Setting per Post Type

If your site has years of content but you only want to translate recent posts, you can now tell TEA to automatically translate only content published after a certain date, and set different dates for different post types. Your pages might be translated in full while blog posts are limited to the last two years, for example.

TEA Now Translates from Any Language on Your Site

For example, if your default language is English but you publish a new post in Spanish first, TEA will now automatically translate it into English and all other languages on your site. Previously, only content published in the default language would trigger automatic translation.

PTC Is Now the Default Translation Engine with New Features

WPML’s AI-powered Private Translation Cloud (PTC) is now the default translation engine for all new sites. It also comes with new features that will save you money and improve your translations.

It’s the only engine that allows us to guarantee translation quality, learn from your existing translations, and keep building features that make automatic translation better and better over time.

DeepL, Google Translate, and Microsoft Translator are staying available but are now treated as legacy options.

Re-translating Edited Content Is Now Free

From now on, editing your original content no longer means paying to translate it all over again. For pages you’ve already translated with PTC, WPML remembers how many words you paid for. When you update the content and re-translate it, those words are free — you only pay if your edits push the page past its original word count, and then only for the difference.

Manual Translations Now Inform PTC Translations

When you send content for automatic translation that was previously translated manually using the WordPress editor or in the Classic Translation Editor, PTC now uses your existing translation as a starting point rather than replacing it. This means the tone, terminology, and style you established are preserved in the new translation.

Automatic Translation Improvements Based On Your Editing

When you edit translations done using PTC, you often make the same edits again and again.

WPML now watches for these repeating edits and works out the preference behind them. When it spots a pattern, it suggests the real fix instead of another one-off correction:

• Glossary terms: if PTC translates dashboard as tablero but you always change it to panel, WPML offers to add panel to your glossary.
• Links: if you keep repointing an English URL to its localized equivalent, WPML captures the mapping and applies it to existing and future pages.
• Regional variants: if you keep editing toward a regional variant (for example, Swiss German), WPML suggests switching the language pair to that variant.
• Formality: if you consistently change the register, WPML suggests updating the formality setting.

WPML applies accepted suggestions across all current and future translations and re-translates the affected content. This way, you don’t repeat the same edit dozens of times.

Suggestions reach you where you work: as a banner in the Advanced Translation Editor, on the WPML → Translations → Improve Translations page, and as an email notification.

This feature works with WPML’s AI translation (PTC) only. Because it learns from the edits you make to AI translations and applies engine-level settings such as glossary, formality, and regional variants, it isn’t available for the legacy DeepL, Google Translate, and Microsoft engines.

Easily Select Language Variants

WPML 5.0 brings a single, unified way to set up your site’s languages in both the Setup Wizard and the WPML → Languages page.

Now you can:

• Pick a language and its regional variant in one step. For example, Mexican Spanish or Argentinian Spanish instead of generic Spanish
• Choose the flag you want including uploading a custom flag, without workarounds
• Create custom languages and dialects more easily, using presets and clearer guidance to avoid mistakes

For existing sites, WPML now automatically detects when your site is using a regional variant of a language and reflects that in the new Languages configuration so you don’t have to reconfigure anything by hand.

No More Waiting in Admin for Translations to Complete

With WPML 5.0, you no longer need to keep a browser tab open in your site’s admin for automatic translations to run. Previously, translations that were in progress only continued while an admin page was open. If you closed the tab, the queue stalled until someone came back to it.

Now, WPML creates and delivers translation jobs on its own, server-to-server, with no open browser required.

There are a few cases where our service can’t reach your site, so the original open-tab behavior still applies: sites on a private network, staging, or VPN-only environment; sites protected by a restrictive security plugin, and similar configurations. In cases like this, WPML warns that your site can’t be reached.

Translate Taxonomies from the Translation Dashboard

WPML 5.0 adds a Taxonomies section to the Translation Dashboard, so you can translate categories, tags, and custom taxonomies right where you manage the rest of your content. Until now, bulk-translating categories automatically meant awkward workarounds, like assigning every category to a dummy post.

Now, you can send all untranslated terms of a taxonomy for translation in a couple of clicks. Automatic translation receives the right context, such as whether a term is a category or a tag, and which post type it belongs to. This makes sure the results are more accurate.

It also works smoothly with Translate Everything: if you switch a taxonomy from “Not translatable” to “Translatable” after automatic translation has already run, WPML quietly queues the existing terms for translation, with no extra prompts or manual steps.

Improved Workflow for Local Translators

WPML 5.0 makes editing rights consistent for translators. Previously, a translator could see the Edit translation button for content that was translated automatically, but not for content another translator had already translated.

Now, translators can edit any translation in their assigned language pairs, regardless of how, when, or by whom it was originally translated. The Edit translation button appears in the admin bar whenever a translation exists and the translator has the matching language pair.

To avoid two people overwriting each other’s work, WPML warns when someone else is actively translating the same content.

WCML Adjustments for WPML 5.0 Interface Changes

WPML Multilingual & Multicurrency for WooCommerce (WCML) 6.0 will be released alongside WPML 5.0 and adapts to the new navigation. WCML 6.0 Beta is also available for testing right now.

WCML’s screens move out of WooCommerce → WCML and into the WPML menu, so everything related to translation lives in one place:

• WCML Settings: WPML → Settings → WCML
• Multicurrency: WPML → Settings → Multicurrency
• Store URLs: WPML → Translations → Store URLs
• Status and troubleshooting tools: WPML → Support

Don’t worry, the old WooCommerce → WCML page points to these new locations so you can quickly navigate to the screen you need.

Other Fixes

Beyond the major features and improvements, WPML 5.0 Beta includes a large number of smaller fixes across the plugin. If you’ve been experiencing a minor issue in an earlier version, there’s a good chance it’s been resolved in this release.

For a full list of fixes, see the WPML 5.0 Beta changelog.

How to Install WPML 5.0 Beta and Test

Install this beta on a testing site only, not on a live site.

1. Log in to your WordPress admin dashboard.
2. Go to Plugins → Add Plugin and click the Commercial tab.
3. Click the Check for updates button.
4. Use the Updates channel dropdown and select Beta.
5. In the list of plugins, select WPML, String Translation, and any other beta addon plugin you want to test and click the Download button.

Available beta plugins in this release and their changelogs:

• WPML Multilingual CMS 5.0
• WPML String Translation 5.0
• WPML Media Translation 5.0
• Advanced Custom Fields Multilingual (ACFML) 3.0
• WPML Multilingual & Multicurrency for WooCommerce (WCML) 6.0
• OTGS Installer 3.2.0

Let Us Know How It Goes

If things work as expected, we’d love to hear about it in the comments below.

If you run into any issues, please open a ticket in our support forum and mention that you’re testing WPML 5.0 Beta. This helps us prioritize and respond faster.

The post WPML 5.0 Beta – A Redesigned Experience and Smarter Automatic Translation appeared first on WPML.

Slider Revolution is one of the most popular WordPress plugins for designing animated sliders, hero sections, and motion-rich page layouts. With version 7, the Slider Revolution team built an AI Translate Addon that delegates translation to WPML, so the sliders you design behave like any other content on your multilingual site.

The two teams have been collaborating on this integration over the last few months. Slider Revolution shipped the addon in their 7.0.16 release in June 2026, and we tested the integration end-to-end against our Translate Everything Automatically flow before recommending it to clients.

“WPML is the standard our users reach for when they go multilingual, so building AI Translate to work with it as the primary source was an easy call. It means our customers get the design freedom of Slider Revolution and the localization power of WPML, with none of the manual duplication.”

— Moritz Praetorius, Founder, Slider Revolution

What Changes for You

In Slider Revolution 6, shipping a slider in more than one language meant duplicating slides per language and tagging each one. Every design tweak turned into one edit per language. The Slider Revolution 7 AI Translate Addon replaces that with a single source slider that WPML translates:

• You design once. Build the module in your source language. WPML extracts every translatable string the moment you save.
• WPML translates in the background. With Translate Everything Automatically on, you don’t open a single dialog. Modules translate alongside your pages and posts.
• Design changes don’t multiply. Move a layer, swap an image, tweak the timing. The change propagates to every language because there’s only one module to maintain.
• Sliders that pull in posts translate themselves. A “latest three posts” slider inherits its translations from the underlying posts, and per-language featured images are picked up automatically.

How to Set It Up

You’ll need three things active on your site:

• WPML Multilingual CMS with String Translation
• Slider Revolution version 7.0.16 or later
• The Slider Revolution AI Translate Addon, which comes with Slider Revolution’s premium licence

With all three active, Slider Revolution’s Plugin Dashboard shows a “WPML compatible” notice and every module you create or edit becomes translatable through WPML.

From there, the workflow depends on whether you use Translate Everything Automatically:

• Translate Everything Automatically on. Build the module, save it, and insert it into a page with the Slider Revolution block. WPML translates the strings in the background. Visitors see the slider in their language as soon as the page goes live.
• Translate Everything Automatically off. Modules appear on the Translations Dashboard under their own Slider Revolution section, so you can pick which ones to send for translation and choose the engine or translator per language.

Display Different Images per Language

WPML translates the strings in your module the moment you save it. The image files stay the same in every language. For most images, that’s what you want. Some images need to change per language: a banner with text baked into the artwork, a product photo for a market that uses different packaging, or a hero shot that should feel local.

If you want per-language images, install WPML Media Translation. You upload an alternate file per language for each image you want to vary, and the slider serves the right one to each visitor.

The full walk-through with screenshots covers both flows step by step.

The post Slider Revolution 7 Now Translates Automatically With WPML appeared first on WPML.

Here’s what’s new.

Full Compatibility with PHP 8.5 and PHP 8.4

WPML 4.9.5 is fully tested and compatible with PHP 8.5 and PHP 8.4.

Recent PHP versions are stricter about certain coding patterns and raise deprecation notices for them. Left unaddressed, these notices clutter your logs and, depending on your server configuration, can surface as warnings in the WordPress admin.

We resolved issues for WPML core plugin and all of its companion components: String Translation, Media Translation, CMS Nav, and the shared libraries they rely on.

A few things worth knowing:

• Nothing changes for you if you’re on an older PHP version. We made these fixes while keeping WPML compatible with the full range of PHP versions we support, all the way back to PHP 7.4. You can update to 4.9.5 safely no matter which PHP version your server runs.
• If you’re already running PHP 8.4 or 8.5, you’ll get a clean experience with no WPML-related deprecation notices.

If you’ve been holding back on upgrading your server’s PHP version, WPML is ready when you are.

A Smoother, Clearer Site Migration Flow

Whenever you copy or move a WordPress site to a new address — pushing a staging site to production, switching hosts, or cloning a site for a new project — WPML needs to recognize the new location so your translations, translation credits, and translation memory stay correctly linked to the original site.

Now, WPML automates this for you: when it detects that your site has moved, it handles the reconnection in the background and shows you a notice explaining what happened. WPML 4.9.5 polishes several rough edges in that flow so it’s clearer and more dependable.

• Migration notices now appear right away. In some situations, there used to be a short window where your site looked like it was working normally, but the next translation action would fail — and the notice explaining the situation only appeared afterwards. WPML now surfaces that notice on the same page load, so you always know your site’s state and what to do next, before anything breaks.

• You’re told why a change happened. WPML includes a safety check that detects when the advanced “alias domain” option was set up by mistake and automatically corrects it. Previously, that correction could happen with no on-screen explanation, leaving site owners wondering why their site had suddenly changed. The migration notice now includes a short, plain-language explanation of what WPML detected and why it acted — no more unexplained resets.

• The alias-domain option is reachable again. Some advanced setups genuinely run the same WordPress installation under two different URLs. For those cases, you can again register an alias domain manually from WPML’s Troubleshooting page. WPML verifies in the background that the URL really points to the same installation before saving it, so an accidental typo or wrong entry can’t quietly misconfigure your site.

• Sites that were mid-migration before updating now recover correctly. If your site carried over a leftover migration “lock” from an earlier version that state could leave the Translation Dashboard locked with no visible way to continue. For example, this can happen because the site had been moved to a new domain, or because a migration was started but never finished. Updating to 4.9.5 clears this stale state automatically: WPML re-detects the migration, shows the right notice, and your Dashboard works again.

Together, these changes mean fewer surprises and a clearer path forward whenever your site changes address.

Other Improvements

WPML 4.9.5 also includes a range of smaller fixes and performance improvements across the plugin. You can find the complete list in the changelog.

How to Update to WPML 4.9.5

As always, we recommend backing up your site before updating.

We’re releasing WPML 4.9.5 gradually. When it becomes available to your site, you’ll see it on your Plugins page.

If you’d like to update right away, use the following steps:

As always, if you run into any issues, our support forum is here to help.

The post WPML 4.9.5 – Full PHP 8.5 Support and a Smoother Site Migration Experience appeared first on WPML.

Why Saving Variable Products Has Been Slow

When you save a product, WPML Multilingual & Multicurrency for WooCommerce (WCML) keeps every translation in sync with the original. That work covers prices, attributes, stock, variations, and other related data.

On a single-product, single-language site, that work is invisible. On a store with 100 variations in 7 languages, the same save quietly runs hundreds of database updates. Most of those updates are for translation data that didn’t actually change.

This made sense as a safety guarantee. It ensured nothing ever fell out of sync. But it also meant that fixing a typo paid the same cost as importing a brand-new product. Stores with large catalogs felt it. Many of you told us.

WCML 5.5.6 changes that.

New: Editor Scoped Sync Mode

We’ve added a new setting called Variation translation sync on product save. It has two modes.

Complete Sync (Default, Unchanged)

WCML keeps doing what it does today. Every save synchronizes every variation in every language. This is the strongest guarantee that translations stay aligned with the source.

Complete sync remains the default after you upgrade. Your site doesn’t change unless you choose otherwise.

Editor Scoped Sync (New, Opt-In)

In this mode, saving from the WooCommerce editor only synchronizes the variations you actually edited.

We tested on a product with 9 variations translated into 19 languages, measuring the full save cycle — from clicking Save to the editor being usable again. Updating only the product description, WCML + WPML’s contribution dropped from 2.08s to 1.42s, a 32% reduction. WooCommerce and WordPress were unaffected. The total save time went from 5.52s to 4.86s — a 12% improvement overall.

Processing time to update a product

Your results will vary depending on WooCommerce, your theme, your host, and your other plugins. Stores with large catalogs and many languages will see the biggest gains.

What About the Variations You Didn’t Touch?

We know this is the first question. There are two safety nets.

After-save notice. When editor scoped sync is on, every save shows you a notice. It lists how many variations were skipped. It also gives you a one-click button: Force update all variation translations. This way, a full sync is always one click away, you don’t have to switch modes to get it.

A nudge when Complete sync is doing wasted work. If you stay on Complete sync, we watch for saves that did a lot of work without actual changes. When we see that pattern, we suggest switching modes. The nudge only appears on large products. We use a threshold of variations × languages ≥ 120. Below that, the cost isn’t noticeable. We don’t bother you.

Where Editor Scoped Sync Applies

Editor scoped sync only affects saves from the WooCommerce product editor. That’s the screen where you feel the slowness.

It does not change:

• The Translation Dashboard
• Translate Everything Automatically
• CSV imports, API calls, and other programmatic ways of editing products
• Background sync after a translation service returns a job

Translator workflows are not affected.

How to Switch on Editor Scoped Sync

After updating to 5.5.6, go to WooCommerce → WCML and click the Settings tab. You will see the Variation translation sync on product save option. Switch it to Only sync variations edited in the editor and click Save changes.

Save any product to confirm the after-save notice appears.

More Performance Improvements

Product Pages Load Faster on Stores with Object Caching

Many of you use a persistent object cache like Redis or Object Cache Pro. With those caches, product pages with many reviews will load noticeably faster after this update.

We changed how WCML handles the product review cache. Previously, it cleared part of your object cache on every product view. Now it works with your object cache instead of clearing it.

Cart Calculations Only Run When Something Changes

WCML used to recalculate cart totals on every page a logged-in shopper visited. That included product pages, account pages, and shop archives. It happened even when nothing about the cart had changed.

From this release, we recalculate only when the currency, the exchange rates, or the cart contents have actually changed. On every other page, WCML stays out of the way.

Cleaner Mini-Cart Behaviour

WooCommerce already fires one cart-refresh request at the start of each shopping session. That request keeps the mini-cart accurate.

WCML was firing a second request on every page load. It fired even when the cart was empty.

That second request is gone in 5.5.6. Fewer background requests. Less load on your server.

Less Work behind Translated Product Images

We simplified how translated product gallery images are handled.

Previously, the work was done twice. Once when the product was saved or translated. Then again on every page view. The page-view pass has been removed. The data saved when you translated the product is now trusted as the source of truth.

The result on your site is the same. Fewer queries get you there.

Big Variable-Product Pages: Pair This Update with the Latest WooCommerce

Some of you reported very slow loading on single product pages with hundreds of variations. We investigated. WooCommerce 10.4.x had a performance issue of its own that significantly amplified the slowdown. WooCommerce 10.7 has since fixed it.

If you’ve seen this on your store, update to WooCommerce 10.7 or later together with WCML 5.5.6. That’s the fastest path forward.

Useful Fixes

Variations Now Fall Back to the Default Language

Some stores let secondary languages fall back to the default language when a product hasn’t been translated yet. On those stores, variations on an untranslated product used to disappear from the dropdown. They now stay visible. They fall back to the default language, as the setting promises.

Filter Counts Refresh on Translated Shop Pages

You add a new attribute to a product that’s already translated. You expect the Filter by attribute counts on the translated shop page to reflect the change. They didn’t, until this release. The original-language shop updated. The translated shop didn’t.

WCML now clears the right WooCommerce cache after syncing attributes to translations. Both shops stay in agreement.

Currency Switcher Spinners on Every Switcher

You can place the [currency_switcher] shortcode more than once on the same page. For example, in the header and again in the footer. The loading spinner used to appear only on the last switcher. From this release, it appears on all of them when a customer changes currency.

Compatibility with WooCommerce 10.8

WooCommerce 10.8 is scheduled for release on Tuesday, 26 May 2026. We tested WCML 5.5.6 against it. Our release is timed for the day after. The version you install is the one we’ve verified against the released WooCommerce build.

Update & Feedback

As usual, we’re rolling out this release gradually. If you’d like to update right away:

1. In your site’s admin, go to Plugins → Add New Plugin. Click the Commercial tab.
2. Click Check for updates.
3. WPML Multilingual & Multicurrency for WooCommerce 5.5.6 will appear in the list. Update from there.

We’d love to hear how editor scoped sync behaves on your store. We’re especially interested if you have a large catalog with many variations and many languages. Drop a comment below or open a ticket in our support forum. Let us know what you measure.

The post WPML Multilingual & Multicurrency for WooCommerce 5.5.6 – Faster Saves on Variable Products appeared first on WPML.

What’s New in WordPress 7.0

WordPress 7.0 introduces a number of changes to the block editor and core functionality. Here’s what WPML 4.9.4 addresses.

Fully iframe-based block editor

WordPress 7.0 makes this the new standard, improving style isolation and giving you a more accurate WYSIWYG experience. Without this update, WPML would force the block editor to fall back to the older, non-iframe mode on every post and page — causing you to miss out on these improvements and any future enhancements that build on the new editor. WPML’s Language Switcher blocks have also been updated to support Block API version 3, including the React hook required for the iframe editor to work correctly.

Updated “open on click” setting for navigation submenus

WordPress 7.0 changed how the Navigation block stores this setting. WPML now reads the updated attribute correctly, so submenus respect the behavior you configured.

New block content available for translation

WordPress 7.0 introduces several new and restructured blocks. WPML 4.9.4 registers the following as translatable, so they appear in the translation editor and display correctly on the frontend in all languages:

• Icon block accessibility labels (aria-label attributes)
• Navigation overlay close button text
• Tab block labels

Updated block asset registration

WPML’s internal code for registering block assets has been updated to use the correct WordPress 7.0 APIs. This fixes console warnings in the block editor and ensures WPML’s CSS loads correctly inside the iframe editor. All changes are backward compatible to WordPress 6.3.

Fixed PHP deprecation notices

A PHP function deprecated in WordPress 7.0 has been replaced with the modern equivalent throughout WPML’s codebase.

Other Fixes

• Fixed a blank white screen on the WPML Settings and Translation Dashboard pages in wp-admin.
• Fixed slow loading on the Menu Sync page.

Updating to WPML 4.9.4

The update is available now for all WPML clients with active subscription. It will appear on the Plugins page in your WordPress admin within 24 hours.

If you’d like to update right away, use the following steps:

Why Keeping WPML Updated Matters

WordPress 7.0 is not a one-off event. Every major WordPress release brings changes under the hood, and some of them affect multilingual sites in ways that aren’t always obvious until something stops working.

Our team tests every WordPress release candidate before it goes public, identifies compatibility issues, and ships fixes in time. That’s what an active WPML subscription gives you: your site stays current with WordPress without you having to track every core change yourself.

The post WPML 4.9.4 – Updated and Ready for WordPress 7.0 appeared first on WPML.

Your checkout is the last thing a customer sees before buying — and the first thing that sends them away if it asks for too much. Whether you want to add or remove fields, build a multi-step flow, or charge extra fees, the right WooCommerce checkout plugin depends on your store’s setup. Not every plugin works the same way, so we put six of them to the test to give you a clear answer.

Overview Summary

What to Look For

Every plugin in this roundup lets you customize your WooCommerce checkout. But they don’t all do it the same way — and the differences matter. Here’s what we looked at, and what’s worth asking yourself before you choose a plugin.

Checkout Fields

The number and variety of field types available, split by free and paid tier.

Field Controls

Whether you can add, hide, or reorder fields in the checkout form.

Ease of Use

The number and variety of field types available, split by free and paid tier.

Multi-step Checkout

The option to split the checkout into multiple steps to reduce friction.

Classic & Block Checkout

Compatibility with the WooCommerce Classic and Blocks Checkout.

WPML Compatibility

Whether you can translate your store with WPML, using the plugin’s free or paid tier.

The Most Free Fields

Checkout Field Editor for WooCommerce

By themehigh.com

Free

---

Best for: Stores that need checkouts with extensive fields.

Overview

ThemeHigh’s Checkout Field Editor earns its spot through sheer field coverage and checkout compatibility. Where most plugins offer 9–12 field types, ThemeHigh gives you 20 in the free version alone. This includes everything from basic text inputs to date/time pickers, phone fields, and URL inputs. It works with both Classic Checkout and WooCommerce Blocks, follows WordPress styling closely, and has almost no learning curve. WPML compatibility is also included in the free version — something most competitors lock behind a paywall.

Checkout Customization

Free Fields

Text

Number

Hidden

Password

Email

Phone

Textarea

Radio

Select

Multiselect

Checkbox

Checkbox Group

Heading

Datetime Local

Date

Time

Month

Week

URL

Paragraph

Paid Fields

Date Picker

Time Picker

File Upload

Label

Field Controls

Add

Yes

Hide

Yes

Reorder

Yes

Stretch / Split

Yes

Checkout Control

Multi-step checkout

Available as a free add-on (MultiStep Checkout for WooCommerce). Only works with Classic Checkout.

Screenshots

Compatibility

Classic Checkout

● Compatible

---

Checkout Block

● Compatible

---

WPML

● Compatible

Pricing

FREE

$0

20 free fields

Add, remove & reorder fields

WPML compatible

Multi-step checkout (add-on)

PRO

$49/y

4 pro fields

Conditional logic (cart, role, fields)

Extra fees (fixed & dynamic)

What WPML Clients Say

“Easy to use, flexible field customization without coding.”

Cecconi • olens.it • Using 2 years

“I can add company code and VAT number fields — exactly what I need for client sites.”

Dainius Valiukas • Web developer • Using 3+ years

Best premium version

Flexible Checkout Fields for WooCommerce

By wpdesk.net

Free

---

Best for: Stores planning to add more eCommerce features and want a bundle of premium plugins.

Overview

WPDesk’s Flexible Checkout Fields features a drag-and-drop editor — a usability edge shared with only one other plugin in this roundup. The free tier covers 12 field types, works with both Classic Checkout and WooCommerce Blocks, and includes WPML compatibility out of the box. That being said, the main reason to consider WPDesk is its bundle deal. The standard pro plan is $59/y — but for $99/y, you get access to 20 WooCommerce addons covering refunds, promotions, and more.

Checkout Customization

Free Fields

Text

Textarea

Number

E-mail

Phone

URL

Checkbox

Headline

Paragraph

Image

HTML

Color

Paid Fields

Multi-checkbox

Select

Multi-select

Radio

Radio with images

Radio with colors

Date

Time

File Upload

Hidden

Field Controls

Add

Yes

Hide

Yes

Reorder

Yes

Stretch / Split

Yes

Checkout Control

Multi-step checkout

Not available.

Screenshots

Compatibility

Classic Checkout

● Compatible

---

Checkout Block

● Compatible

---

WPML

● Compatible

Pricing

FREE

$0

12 free fields

Add, remove & reorder fields

WPML compatible

PRO

$59/y

10 pro fields

Conditional logic (cart, role, fields)

Extra fees (fixed & dynamic)

---

Bundle deal: 25 WooCommerce plugins for $99 / year.

Best preset checkout templates

Flux Checkout for WooCommerce

By iconicwp.com

Paid

---

Best for: Stores that want to configure their checkout by choosing from preset options rather than setting up fields manually.

Overview

Flux Checkout for WooCommerce takes a different approach to checkout customization – it doesn’t let you add, remove, or reorder individual fields at all. Instead, it offers preset checkout templates tailored to different store types: physical products, digital products, company orders, and more. Each preset shows only the fields relevant to that context, which makes for a cleaner checkout without any manual configuration. It works with both Classic Checkout and WooCommerce Blocks, and is compatible with WPML. On top of checkout configuration, the plugin also offers address autocomplete and cross-sell products during checkout.

Checkout Customization

Free Fields

N/A

Paid Fields

N/A

Field Controls

Add

No

Hide

No

Reorder

No

Stretch / Split

No

Checkout Control

Multi-step checkout

Included in the plugin.

Screenshots

Compatibility

Classic Checkout

● Compatible

---

Checkout Block

● Compatible

---

WPML

● Compatible

Pricing

FREE

No free version available.

PRO

$99/y

Multi-step checkout

Cross-sell during checkout

WPML compatible

Best checkout editor

Checkout Field Editor and Manager for WooCommerce

By acowebs.com

Free

---

Best for: Stores that need a simple checkout and want a user-friendly, drag & drop editor.

Overview

Checkout Field Editor and Manager for WooCommerce stands out in this roundup for having the most intuitive editor interface — a drag-and-drop builder. Unlike the table-based editors most competitors use, the layout makes it immediately clear what your checkout will look like as you build it. With 10 free fields and support for both Classic Checkout and WooCommerce Blocks, it covers most stores’ needs straight out of the box. That being said, you’ll need the plugin’s paid plan to enjoy WPML compatibility.

Checkout Customization

Free Fields

Text

Number

Textarea

Checkbox

Select

Radio

Header

Paragraph

Toggle Switch

URL

Paid Fields

Password

Phone

Email

Hidden

Multi-Select

Checkbox Group

Color Picker

Date

Time

File Upload

Label

Google Place Select

Image Group

Color Group

Field Controls

Add

Yes

Hide

Yes

Reorder

Yes

Stretch / Split

Yes

Checkout Control

Multi-step checkout

Not available.

Screenshots

Compatibility

Classic Checkout

● Compatible

---

Checkout Block

● Compatible

---

WPML

● Compatible

Pricing

FREE

$0

10 free fields

Add, remove & reorder fields

Drag-and-drop editor

PRO

$49/one-time

15 pro fields

Conditional logic (cart, role, fields)

Extra fees (fixed & dynamic)

WPML compatible

What WPML Clients Say

“Flexibility without writing a line of code.”

Saimeon • simplestudio.dev • Using 3+ years

Best classic checkout customizer

YITH WooCommerce Checkout Manager

By yithemes.com

Paid

---

Best for: Stores using the Classic Checkout and need extensive field customization.

Overview

YITH WooCommerce Checkout Manager is a solid choice for stores that use the Classic Checkout and need deep field customization. With 11 field types, a clean table-based editor, and features like field tooltips and checkout styling, the plugin goes beyond basic field management. The trade-offs are significant though: there’s no free version, WooCommerce Blocks is not supported, and WPML is not compatible at any tier.

Checkout Customization

Free Fields

N/A

Paid Fields

Text

Number

Password

Phone

Textarea

Radio button

Checkbox

Dropdown select

Multi-select

Date

Time

Field Controls

Add

Yes

Hide

Yes

Reorder

Yes

Stretch / Split

Yes

Checkout Control

Multi-step checkout

Available as a paid add-on (YITH WooCommerce Multi-step Checkout) at $69.99 / year.

Screenshots

Compatibility

Classic Checkout

● Compatible

---

Checkout Block

● Not compatible

---

WPML

● Not compatible

Pricing

FREE

No free version available.

PRO

$69/y

11 fields

Add, remove & reorder fields

Conditional logic (cart, fields)

Best for adding fields

WooCommerce Checkout Field Editor

By woocommerce.com

Paid

---

Best for: Stores using the classic checkout and only want to add new fields.

Overview

WooCommerce’s own checkout field editor is built for stores that need to collect additional information at checkout – not reconfigure what’s already there. Unlike other plugins in this roundup, it doesn’t let you hide or remove the default WooCommerce fields, and can only add new ones. The editor itself is clean and straightforward — a single screen with drag-and-drop reordering and half/full-width field positioning. The trade-offs are significant though: there’s no free version, and it only works with Classic Checkout.

Checkout Customization

Free Fields

N/A

Paid Fields

Text

Password

Textarea

Select

Multi-Select

Radio

Checkbox

Date Picker

Heading

Field Controls

Add

Yes

Hide

No

Reorder

Yes

Stretch / Split

Yes

Checkout Control

Multi-step checkout

Not available.

Screenshots

Compatibility

Classic Checkout

● Compatible

---

Checkout Block

● Not compatible

---

WPML

● Compatible

Pricing

FREE

No free version available.

PRO

$49/y

9 fields

Add & reorder fields

WPML compatible

What WPML Clients Say

“Easy to add the extra checkout fields that WooCommerce doesn’t include by default — gives me the flexibility to adapt checkout to different client projects.”

Mario • flotarium.com • Using 3+ years

Which Plugin Is Right for You?

All six plugins let you customize your WooCommerce checkout — but which one is right for you depends on your needs.

Checkout Field Editor for WooCommerce

You want a free plugin with many field types that works with both the Classic and Block checkout.

Flexible Checkout Fields for WooCommerce

You need additional eCommerce features and want a bundle of premium plugins rather than paying for each one separately.

Flux Checkout for WooCommerce

You want a polished multi-step checkout and prefer picking from preset options over configuring fields from scratch.

Checkout Field Editor and Manager for WooCommerce

You need a simple checkout and prefer dragging fields into place over working from a table-based editor.

YITH WooCommerce Checkout Manager

You’re using the Classic Checkout, need extensive field customization, and don’t plan to build a multilingual store.

WooCommerce Checkout Field Editor

You’re using the Classic Checkout, only need to collect extra information at checkout, and don’t need to hide or remove any existing fields.

Customize Your Store for International Customers

Translate your store and display prices in different currencies with WPML Multilingual & Multicurrency for WooCommerce.

The post Best WooCommerce Checkout Plugins (6 Tested) appeared first on WPML.

What Changed in WPML SEO 2.2.5

In this version, we fixed issues that affected both popular SEO plugins.

Yoast SEO + WPML: Improved Sitemap Rendering and Translating Term Meta-data

• Faster Sitemap Rendering. We improved performance for rendering translations of taxonomy and product sitemaps. 

• More Reliable Translating Of Term Metadata. Yoast SEO term meta descriptions sometimes disappeared if they were translated before the term itself. Now, they display correctly no matter when they’re translated. 

RankMath and Yoast SEO: Correct Home and Blog URLs in Sitemaps

• We’ve resolved an issue where sitemaps would display incorrect homepage URLs in secondary languages.

Update To The New Version

We’re releasing WPML SEO 2.2.5 gradually — if your plugin version isn’t automatically updated, you can update manually:

1. In your site’s admin, go to Plugins → Add New Plugin and switch to the Commercial tab.
2. Click to check for updates.
3. You’ll see WPML SEO 2.2.5 — just click to update.

And you’re all set! Feel free to leave us a question or comment below.

The post WPML SEO 2.2.5 — Smoother Integration with RankMath and Yoast SEO appeared first on WPML.

A few weeks ago, we released WPML 4.9.0, which brought improvements to automatic translation workflows and performance with object cache. WPML 4.9.1 is a follow-up maintenance release focused on third-party compatibility and bug fixes.

Divi 5 is set to move from beta to production on February 26. We’ve spent the last weeks working through compatibility issues you reported.

Smooth Migrations from Divi 4 to Divi 5

When migrating from Divi 4 to Divi 5, source language pages were losing their content. The pages appeared empty in both the backend editor and on the frontend, while translated pages continued to display correctly.

This is resolved in WPML 4.9.1, but there are a few things to keep in mind before you migrate:

• Update to WPML 4.9.1 before running the Divi 5 Migrator.
• If you migrated to Divi 5 before updating WPML, roll back the migration, update WPML, and run the migration again.

Divi Canvases Are Now Translatable

Divi 5 introduced Divi Canvases — a way to create off-canvas menus, popups, and other embeddable content for your pages.

WPML 4.9.1 now recognizes Divi Canvases as a custom post type, so you can translate them like any other content. To get started, go to WPML → Translation Dashboard and find the Global Canvases section. All your canvases will be listed there, both page-specific and global.

​​One Known Issue Remains

If you use dynamic content in Divi 5, dynamic field text settings such as “Before” and “After” cannot be translated yet. We’re aware of this issue and working on a fix for an upcoming release.

This WPML release also includes the following Elementor-related fixes and improvements:

• Nav Menu, Mega Menu, and Theme Builder templates now show the correct translated content on the frontend, whether you translated them using automatic translation or the Advanced Translation Editor.
  
• When using WooCommerce products inside Elementor loop-grid queries, filters now return the correct results on translated pages.
  

Besides this, we’re continuing to expand WPML compatibility with Elementor Editor v4, which is still in beta. As of WPML 4.9.1, links in atomic buttons can now be translated automatically and in the Advanced Translation Editor. As a reminder, if you run into any issues with Editor v4, let us know in the Elementor Editor v4 erratum comments.

With WPML 4.9.1, we’ve stopped officially supporting PHP 7.0, 7.1, 7.2, and 7.3. These versions are no longer maintained by the PHP project and do not receive security updates.

To keep your site secure and compatible with future WPML releases, please upgrade your server to PHP 7.4 or higher (PHP 8.3 recommended).

This release includes more than 20 additional fixes. Highlights include:

• Smoother URL migration — When WPML detects a change in your site’s URL, the migration banner now guides you through your options more clearly.
• No more false positives with Wordfence — WPML 4.9 was triggering an incorrect security warning when used alongside Wordfence. This is now resolved.

For the full list, see the changelogs for WPML 4.9.1 and String Translation 3.5.1.

We’re releasing WPML 4.9.1 gradually. When it becomes available to your site, you’ll see it on your Plugins page.

If you want to update right away:

Make sure you update both WPML and String Translation. You need both to benefit from all the fixes and improvements in this release.

The post WPML 4.9.1 – Improvements for Compatibility with Divi 5, Elementor, and More appeared first on WPML.

Translate Options Pages in Translation Dashboard

You can now translate Options Pages directly in WPML → Translation Dashboard. Just expand the ACF Options section and send your Options Page for translation.  

Improved Support for Local Fields

ACFML 2.2.0 brings a number of updates relevant for developers using “Local Fields” – fields you define using PHP or JSON instead of the WordPress admin GUI.  

Simpler Syncing Process for Local Content

After creating your custom fields and other content using PHP or JSON, you need to sync them with WPML. This makes them available for translation.

You can now easily sync the following types of local ACF content:

• Custom post types
• Custom taxonomies
• Field groups
• Options pages 

Just go to ACF → Tools after creating your local content, select Sync once now and click Apply.

This way, you sync your local fields and content only once, when you want to. Until now, this would happen on every request, which could impact performance.

Better Management for Translated Local Fields

Local fields are now recognized as ACF fields, so they can appear in templates or blocks like fields in the original language.

Performance Improvements

How to Update to ACFML 2.2.0

We’re rolling out this release in batches, so you may not see the update immediately. To update right away, follow these steps:

1. Log into your WordPress admin dashboard.
2. Go to Plugins → Add New and click the Commercial tab.
3. Click the Check for updates button.
4. Select ACFML 2.2.0 and click the Download button.

Tell Us What You Think

Have any questions about ACFML 2.2.0? Leave a comment below and we’ll reply to you.

The post ACF Multilingual 2.2.0 – Easier Options Page Translation and Better Local Fields Support appeared first on WPML.

Upfront Translation Costs and Time Estimates

WPML now calculates the exact credits needed before you send content for automatic translation. If you don’t have enough prepaid credits or Pay-As-You-Go set up, translations won’t start. The interface will guide you through the options to continue translating.

And that’s not all—when you send content for translation in bulk, you’ll see progress and an estimated time remaining at the top of the Translation Dashboard. With WPML 4.9, you always know what’s happening, so even big jobs run smoothly without guesswork.

One-Click Fix for Stuck Translation Jobs

Large sites translating bigger volumes of content sometimes experienced stuck translation jobs. In WPML 4.9, we’ve improved how WPML communicates with the Advanced Translation Editor, so these issues should happen less often. 

If a job does get stuck, a new Resend button appears in the Translation Dashboard to restart them with one click. In case you need to contact support, error messages now include all the technical details your Supporter needs to help you right away.

Full Support for Divi 5 and Custom Elementor Widget Translation

We asked you to help us test both Divi 5 compatibility and custom Elementor widget support in WPML 4.9 beta. After your feedback and more testing from our team, both features are stable in WPML 4.9.

Translate JavaScript Strings From Third-Party Plugins or Themes

Some themes and plugins store text in JavaScript files instead of PHP. WooCommerce Cart and Checkout blocks are common examples. 

While translations are usually included for widely spoken languages like Spanish, less common languages are often left out. WPML couldn’t scan these files before, so parts of your site could remain untranslated for some visitors.

WPML 4.9 adds a Detect strings in JavaScript files option in WPML → Settings. Enable it, scan your theme or plugin, and translate all strings via the Other texts (Strings) section in the Translation Dashboard. 

This way, your visitors get a truly multilingual experience, whether they speak Spanish, Latvian, or any other language.

See the full documentation about translating strings in JavaScript files.

If you run a large site, you probably use object caching like Redis or Memcached to improve performance. Until now, using object caching with WPML could cause issues with translations not updating, post status not syncing between languages, or reviewed translations not saving properly.

WPML 4.9 fixes these issues. We’ve tested with Redis, Memcached, and other common caching solutions to ensure translations work reliably in object-cached environments. You can now use object caching on large multilingual sites without affecting translations.

We’re releasing WPML 4.9 gradually. When the update becomes available to your site, you’ll see it on your Plugins page. 

If you want to install WPML 4.9 right away:

• WPML CMS 4.9.0
• WPML String Translation 3.5.0
• WPML Media Translation 3.1.0
• WPML Multilingual & Multicurrency for WooCommerce 5.5.4

We built WPML 4.9 around your feedback. Now that you’ve seen what’s new, we’d love to hear how it’s working on your site.

What’s improved for you? What features would you like to see next? Leave a comment below.

The post WPML 4.9 – Better Automatic Translation Control and Enhanced Compatibility appeared first on WPML.