Lang Forge – Multilingual, Translation & hreflang SEO

Changelog

1.0.39

• Glossary opens with no licence check. It has always been part of this plugin, and the menu no longer puts it behind a gate that could only answer yes.
• The PRO badge in the menu and in the section tabs marks a screen the Lang Forge Pro add-on provides and this site does not have. It follows whether the add-on is installed, not the licence.
• The String Translation help shows the [langforge_string] shortcode. The old [lf_string] form keeps working in existing content.

1.0.38

• Fixed: on a site without WPML or Polylang, the first activation made Russian the default language and added English under /en/, whatever language the site was written in. A fresh install now starts with the site’s own language (Settings → General → Site Language) as its only language, so an English site stays English; add more languages under Lang Forge → Languages.

1.0.37

• This release needs Lang Forge Pro 1.1.0 or newer. An older add-on is switched off whole rather than left running, because beside this core it would be present and wrong rather than absent. Until you update it AI translation, bulk AI translation, translation memory, translation QA and the frontend editor are unavailable. Translations already saved are untouched, an admin notice names both versions and what stopped, and installing the current add-on brings all of it back.
• Deleting the last Forge product on a site now clears the job queue the Forge plugins share — its table, its two scheduled events and its version marker. While any other Forge product is still installed, deleting this one leaves the queue exactly as it is, because the pending jobs in those rows are that product’s too.
• Fixed: Lang Forge → Tools stopped with a fatal error on a site whose licence includes bulk duplication while the Pro add-on is not loaded. The card shows the Pro teaser instead.

1.0.36

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

1.0.35

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

1.0.34

• Smaller package and one less admin surface: the SDK’s own menu, opt-in screen and promotional notices are gone.

1.0.33

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

1.0.32

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

1.0.31

• Fixed: requesting a URL that doesn’t exist answered with a redirect to the homepage instead of a 404. The “missing translation → language homepage” fallback now fires only when the request itself names a language — a language-prefixed URL, a ?lang= parameter, a language subdomain or mapped domain, or the language cookie from an earlier switch. A dead URL with no language signal returns a real 404: your theme’s 404 page for visitors, and the correct status code for search engines instead of a soft-404.

1.0.30

• Declares support for WordPress 7.1. Checked against 7.1-RC3, where the post editor canvas moves into an iframe for good: the language panel, the admin-bar switcher and the editor scripts all still work, because they read the post through the editor’s own data store rather than reaching into the canvas.
• The sibling plugin formerly called SEO Forge is now Rank Forge, so the shared Forge screens and the cross-links name it correctly.

1.0.29

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

1.0.28

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

1.0.27

• No change in this package: the release updated parts that ship only in the edition distributed through avakode.com.

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: 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.