Shops, forms, and page builders

LocalePro translates the page a visitor sees, so most plugins need nothing special. If a plugin prints ordinary text, that text translates. A few things don’t fit that, and got extra care. The plain version is on the integrations page. This one is the detail.

WooCommerce

• Cart and checkout. These update after the page has loaded. LocalePro translates those updates as they arrive. A product name already saved fills in immediately, and one unfamiliar word never blanks out the rest of the cart.
• Prices and counts. Amounts, currency symbols, and the little cart counter are left alone. “$13.50” does not come back as “13,50 €”.
• Order email. LocalePro remembers the language a customer checked out in, and sends later order email in that language, even if it goes out days later from a different screen. Your own copy of the same email is untouched.
• The mini-cart. WooCommerce only fully sets up the mini-cart on the cart and checkout pages. LocalePro fills in the missing piece everywhere else, so it still works on a translated page.

Gravity Forms

Notifications often go out later, from a background task, sometimes from “Resend Notifications” months after the fact. LocalePro writes the visitor’s language onto the entry when they submit, and reads it back when the email actually sends. The form itself, its labels, and its error messages translate with the page. What the person typed stays as they typed it.

Page builders

Elementor, Divi, Beaver Builder, Oxygen, Bricks, WPBakery, Thrive Architect, and Brizy all show a published page as ordinary text and images. LocalePro translates that. The editing screen is the part that needs care, because it also renders on the front of the site. Translating it could save a translation back over the words you wrote. LocalePro leaves those editing screens alone.

Yoast and Rank Math

Both add a block of details for search engines that visitors don’t see. LocalePro translates the words in that block, and points the links inside it at the translated page, so the details don’t disagree with the page itself.

If you build plugins

Everything above uses the same public hooks in hooks and filters. If a plugin you run has its own late-loading content, its own data shape, or its own email queue, those are the hooks to use.