WPML GraphQL

This release keeps WPML GraphQL working smoothly alongside WPML 5.0 and fixes a language-filtering issue in comment queries.

Also in this release

• GraphQL comment queries now respect the language filter, so you only get comments for the language you are querying.

Security

• This release includes security hardening.

WPML GraphQL 1.2.0 makes ACF Options Pages language-aware — so now, you can pull the correct translated content from global settings fields.

• ACF Options Pages now respect language in GraphQL queries. If your site uses Advanced Custom Fields and Options Pages, you can now pass a language parameter in your WPGraphQL query and get back the translated values for that language.
• Querying translated content by URI now works as expected. You can now look up translated posts, pages, and custom post types using their URI — covering postBy(`uri`:), post(`id`:, `idType`: `URI`), pageBy(`uri`:), page(`id`:, `idType`: `URI`), myCustomPostType(`id`:, `idType`: `URI`), myCustomPostTypeBy(`uri`:), nodeByUri(`uri`: ), contentNode(`id`:, `idType`: `URI`). This is useful when your headless frontend routes by URL and needs to fetch the right translation.
• WooGraphQL fix: Querying product translations no longer causes a server error.
• A minor security issue was fixed.

• Declare the compatibility with up to WPGraphQL 2.0.0.
• Fix the uri field for the translation of a page that is set as the homepage.

• Fixed an issue where WPML fields would get registered multiple times for the same object type.

• Fixed nodeByUri queries.

• Added support for querying menus and menu items with language filters.
• Improved compatibility with PHP 8.3.

• Added consistent language handling for nested taxonomies on translated posts.
• Added consistent language handling for nested posts on translated taxonomies.
• Added consistent language handling for nested queries related to comments on translated content.
• Added support for querying translated posts by DATABASE_ID or SLUG.

• Initial release.