github.com\/lipis\/flag-icons<\/a><\/li>\n<\/ul>\n\nThe plugin makes no requests to any external service<\/strong> to render a switcher: the flags are served\nfrom this plugin's own directory.<\/p>\n\n\n\n- Upload the
aumlang<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the plugin ZIP via Plugins \u2192 Add New \u2192 Upload.<\/li>\n- Activate the plugin through the Plugins screen.<\/li>\n
- Make sure pretty permalinks are enabled (Settings \u2192 Permalinks) \u2014 language URLs like
\/zh\/<\/code> require them.<\/li>\n- Go to the AumLang settings screen and add your languages. Leave the translation engine on \"WordPress AI Client\" if a provider is already connected under Settings > Connectors; otherwise switch it to the direct connection and enter your own endpoint, model and key.<\/li>\n
- Open any post, page or product and use the AumLang panel to translate it.<\/li>\n<\/ol>\n\n\n
\nDo I need an API key?<\/h3><\/dt>\nNot if WordPress already has one. AumLang's default engine is the AI client built into WordPress 7.0, which uses the provider connected under Settings > Connectors \u2014 that connection belongs to WordPress, is shared with every other plugin, and this plugin never sees the key.<\/p>\n\n
You need your own key only for the second engine, the direct connection. It exists because the connectors WordPress ships cover Anthropic, Google and OpenAI, and a site whose network cannot reach any of those still needs a way to translate. It speaks the OpenAI-compatible chat API, so any service implementing it will do; you supply the endpoint, the model and the key, and the AI account is yours either way.<\/p><\/dd>\n
Does it work with Elementor and Gutenberg?<\/h3><\/dt>\nYes. AumLang reads each builder's own structure, translating only the text and leaving layout, styles and design untouched \u2014 including custom widgets.<\/p><\/dd>\n
Will it translate WooCommerce products?<\/h3><\/dt>\nYes \u2014 product title, description, short description, categories, tags, brands and attributes, while carrying over price, stock and gallery so the translation remains a complete product. Multi-currency is intentionally out of scope; pair AumLang with a dedicated currency plugin if you need it.<\/p><\/dd>\n
How do visitors switch language?<\/h3><\/dt>\nAdd the language switcher via the [aumlang_language_switcher]<\/code> shortcode, the block, the widget, or the aumlang_language_switcher()<\/code> template tag.<\/p><\/dd>\n\n<\/dl>\n\n\n1.7.2<\/h4>\n\n\n- A translation written in the wrong alphabet is no longer accepted.<\/strong> Nothing checked that what\ncame back was in the language that was asked for. A provider that answers an Italian request with\nChinese returns the right number of items, in valid JSON, with no error anywhere \u2014 so it was stored\nas the Italian translation, and retrying produced the same thing because the stored value already\nlooked finished. Replies are now checked against the writing systems the target language actually\nuses, and one in the wrong script is treated as a failed attempt: the retry runs, and if that fails\ntoo the original text is kept. English left in place is a problem you can see; Chinese presented as\nItalian is one you cannot.<\/li>\n
- The check only judges what can be judged with certainty \u2014 a script the language never uses. It does\nnot try to tell Spanish from Portuguese, and it never rejects a reply for a language it does not\nknow: not knowing is not evidence of an error.<\/li>\n<\/ul>\n\n
1.7.1<\/h4>\n\n\n- Bulk translation offered to translate posts that were themselves translations.<\/strong> The posts list\nshows translations alongside their originals, so a site with three languages has four times the\nrows \u2014 and \"select all\" selects what is on the screen. There is no way for the owner to tell which\nrows are copies, so the Japanese copies of three posts were counted as \"will be translated into\nJapanese\": money spent to produce a Japanese translation of a Japanese page, overwriting what was\nthere. Those are now left alone, and the confirmation screen says why.<\/li>\n<\/ul>\n\n
1.7.0<\/h4>\n\n\n- Translate many posts at once.<\/strong> Select rows in the Posts or Pages list, pick a language from the\nbulk actions menu, and AumLang works through them in the background. Until now the only way to\ntranslate was the button in the editor: one post, one language, one click. A site with twenty pages\nand five languages is a hundred clicks across twenty page loads, each waiting for the rounds to\nfinish \u2014 not a slow workflow but an impossible one, and sites were sitting at a handful of\ncombinations done while their owners reported the result as a fault in the translation.<\/li>\n
- Because this spends money, Apply does not start anything. It opens a screen saying how many posts\nwill actually be sent, how many already have a translation and will be left alone, and into which\nlanguage. That screen has the button. The counts are worked out as the screen is drawn, never\nreused from a moment ago.<\/li>\n
- A post that already has a translation is skipped rather than translated again, including one whose\ntranslation is out of date. Re-translating a single post stays where it was, on the button in the\neditor that says what it will do before it does it.<\/li>\n
- The run survives the page being closed: it continues in the background and the progress screen\npicks it up again. Stop<\/strong> finishes the post it is on and then stops; posts already done stay done.<\/li>\n<\/ul>\n\n
1.6.0<\/h4>\n\n\n- A header or footer built as a page is now translated.<\/strong> Builder-driven themes keep the header,\nthe footer and other global blocks in an ordinary page and render it inside every request with\n get_post(), which runs no query \u2014 so nothing this plugin had hooked could see it. The entry was\nin the translation list, translating it changed nothing on the front end, and there was no error\nanywhere. The content is now matched by an exact hash of itself, so it works regardless of how the\ntheme fetched the page, and a theme that uses no such block pays one string comparison.<\/li>\n
- Widget text is now translated whatever wrote the widget.<\/strong> The previous pass used the\n widget_title filter, which only fires if the widget itself calls it. Core widgets do; many others\nsimply print the stored value, and for those the title stayed in the source language and never even\nappeared in the strings list, so there was nothing to notice. Every widget's stored fields are now\nread before it renders. URLs, icons, CSS classes, ids, email addresses and phone numbers are left\nalone \u2014 translating those breaks the widget rather than the wording.<\/li>\n
- 23 more languages show their flag.<\/strong> A flag was drawn from the region in the locale, and\nWordPress writes a number of locales with no region at all \u2014 Japanese is
ja<\/code>, not ja_JP<\/code>. Those\nlanguages sat in the switcher with no flag beside the ones that had one. Languages genuinely spoken\nacross several countries (English, Arabic, Swahili, Catalan, Basque) still show no flag, because\nthere is no right answer for them and a wrong flag is worse than none.<\/li>\n<\/ul>\n\n1.5.1<\/h4>\n\n\n- The plugins list now carries a Guide<\/strong> link beside Deactivate, pointing at this plugin's\nmanual in the language that administrator reads the admin in. The manual is the product's\nfull documentation; it is a separate thing from the plugin's own help text.<\/li>\n<\/ul>\n\n
Older entries are in changelog.txt, which ships with the plugin.<\/p>","raw_excerpt":"AI translation for Elementor, Gutenberg and WooCommerce that keeps layouts intact, with per-language URLs, hreflang, canonicals and sitemaps handled.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/365567","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=365567"}],"author":[{"embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/aumcreate"}],"wp:attachment":[{"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=365567"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=365567"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=365567"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=365567"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=365567"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/pan.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=365567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}