0.1.3

Patch release fixing language URL resolution.

• Fix: separate language domains and subdomains resolve regardless of the host's letter case (ENGLISH.TEST as english.test). Paths, query parameters and language slugs stay case-sensitive; unknown hosts, unsupported schemes, userinfo and conflicting lang selectors are still refused.
• Fix: a language on its own domain or subdomain without a translated static front page resolves its home to null instead of the default language's front page.
• Fix: #comment-ID URLs resolve only in their post's language, through the comment loader's visibility checks.
• Tests: URL regressions cover lowercase, uppercase and mixed-case hosts in every URL mode, root and subdirectory installations, unknown hosts, and comment URLs.

GitHub CI passed on the minimum (WordPress 6.5, PHP 7.4, WPGraphQL 2.0.0, Polylang 3.7) and current (WordPress 7.1.2, PHP 8.4, WPGraphQL 2.23.1, Polylang 3.8.10) stacks.

0.1.2

Patch release fixing language URL resolution, nested translated-menu scopes/privacy, and GraphQL enum collisions.

Translation loading now batches across sibling nodes while keeping inaccessible translations omitted. For the measured 21-post connection, translation batches dropped from 20 to 1 and anonymous SQL queries from 73 to 16.

CI now covers two mutually compatible stacks:

• Minimum: WordPress 6.5, PHP 7.4, WPGraphQL 2.0.0, Polylang 3.7.
• Current: WordPress 7.1.2, PHP 8.4, WPGraphQL 2.23.1, Polylang 3.8.10.

Both stacks passed locally: all 9 HTTP tests plus isolated regressions for translation visibility/batching, nested menus, empty-language states, language enums, and URL configurations. Lint, static analysis, and disposable-setup safety checks passed. Setup verifies dependency constraints and prevents automatic version drift. GitHub CI also passed lint/static analysis and both integration stacks.

Polylang Pro, HTTP authentication flows, and live domain DNS/TLS remain unverified. Authenticated visibility tests use administrator/subscriber identities in fresh WP-CLI processes.

Install the attached ZIP through WordPress Plugins → Add New → Upload Plugin.

0.1.1

Fixes GraphQL schema errors when Polylang has no configured languages, including after the last language is removed. Ordinary queries and schema introspection work without referencing missing language enums. Behavior with configured languages is unchanged.

Adds isolated regression coverage without resetting the existing test database.

Verification: Composer lint and static analysis, all three language-state regression phases, and all nine bilingual HTTP integration tests passed.

Install the attached ZIP through WordPress Plugins → Add New → Upload Plugin.

0.1.0

First release.

• Languages: the Language type, LanguageCodeEnum and LanguageCodeFilterEnum, plus the root fields languages, defaultLanguage, language(code:) and translateString. A language's title and description are translated.
• Content: language, translations and translation(language:) on translated post types and taxonomies. Connections take where: { language, languages }.
• URIs: nodeByUri resolves each language's front page at its home (/en/), and never to content in another language. A translated front page has isFrontPage: true and its home as uri.
• Menus: menuItems(where: { location, language }) reads per-language menus, and the items of menus Polylang assigned are public.
• Requests: GraphQL requests run Polylang in its REST context, so nothing is filtered by language implicitly.