Lang Forge – Multilingual, Translation & hreflang SEO

更新日志

1.0.29

• Fixed: the shared Forge interface (dashboard, Connect, credits) could display in a stale translation, or fall back to English, on sites using a community language pack. It was reading the plugin’s own bundled catalogue instead of the pack WordPress installs.
• Russian and Ukrainian are no longer bundled with the plugin. Both now have community-reviewed language packs on translate.wordpress.org, which WordPress uses in preference to anything shipped here — so bundling our own copy could only ever serve an older, unreviewed version. The download is 36% smaller than in 1.0.25.
• Translations: a large quality pass across all 13 bundled languages. Terminology now follows each locale’s official WordPress glossary, and the Japanese, French, German, Spanish and Brazilian Portuguese catalogues follow their locale’s published style guide — Japanese spacing and punctuation, French apostrophes and non-breaking spaces, German and Spanish quotation marks. Corrections made by the Dutch and Polish translation editors have been adopted as-is.

1.0.28

• Translations: reviewed every locale against WordPress core’s own wording and corrected 692 strings. The plugin now uses the same vocabulary core does — the Russian word for “posts”, the French term for permalinks, the Italian term for unlinking, and so on — instead of a plausible-but-foreign synonym. Two strings that had been left in English in the Hindi catalogue are translated, and a Hindi string that said the opposite of what it meant (“Disconnect”) is fixed.

1.0.27

• Translations: every bundled language is now complete. 227 missing strings were translated across the 15 supported locales, and 62 plural forms that carried the English two-form shape were rebuilt with the correct number of forms for their language (3 for Russian, Ukrainian and Polish, 6 for Arabic, 1 for Japanese, Korean and Chinese) — those catalogues previously failed to compile and picked the wrong plural at runtime.
• Dropped 49 placeholder language files that were only 1–4% translated. They shipped almost nothing but English and made the download 24% larger. The 15 supported locales are unchanged: Arabic, German, Spanish, French, Hindi, Italian, Japanese, Korean, Dutch, Polish, Portuguese (Brazil), Russian, Turkish, Ukrainian and Chinese (Simplified).

1.0.26

• Fixed: hreflang alternates pointed at the page being viewed instead of the translation. On an English page the es, de and x-default links all resolved back to the English URL (and the same on every other language), so search engines discarded the annotation. Both the wp_head tags and the hreflang sitemap are affected.
• Fixed: the canonical URL on a translated page could resolve to a sibling translation instead of the page itself.
• Fixed: on a non-default-language page, permalinks lost their language prefix, because the language-aware home_url() was being used as the base for detecting it.
• Fixed: /sitemap-hreflang.xml and /sitemap-hreflang-N.xml were redirected to a trailing-slash URL before the sitemap could render.
• Plugin name now mentions hreflang SEO, which the plugin has always handled.

1.0.25

• readme: clearer plugin title, updated tags and an expanded FAQ covering multilingual setup, WooCommerce, hreflang, migration and RTL.
• No functional changes.

1.0.24

• Security hardening: all dynamic output is now escaped late with the context-appropriate function (esc_html/esc_attr/esc_url, esc_html__ for translated strings used as format strings, and wp_kses for trusted pre-built admin markup). No behavioural changes.
• The glossary CSV export now neutralises CSV/formula injection in exported cells.

1.0.23

• Free now supports an unlimited number of languages with no plan-based cap — removed all license-gated language-limit code (no “locked” language rows, no over-limit notice, no limit on saving).
• Tightened the glossary REST list endpoint to the same administrator capability as glossary management.

1.0.22

• Hardened WP-CLI export: files are now always written to a plugin-slug folder inside the uploads directory (wp-content/uploads/langforge/) instead of an arbitrary path, so nothing is ever written into the plugin folder.
• Uninstall cleanup now only removes data under the plugin’s own unambiguous prefix, so unrelated options/metadata belonging to other plugins are never deleted.

1.0.18

• New: Support menu item that opens the Avakode support dashboard.
• New: Opt-in anonymous usage analytics (OFF by default) — see Third-Party Services.
• New: Contextual, dismissible Pro feature tips on the plugin dashboard (Free users only).

1.0.15

• WordPress.org compliance and licensing hardening.
• Pro entitlement is now resolved by the Lang Forge Pro add-on; the free plugin bundles no licensing SDK.
• The plugin no longer modifies admin notices belonging to other plugins.
• readme metadata cleanup.

1.0.0

• Initial release.