Hi,

I am getting an error when querying pages that are set as child of other pages, and it seems related to WPML. The error says: "SyntaxError: Unexpected token < in JSON at position 0".

If I have only WPGraphQL enabled it works fine and I can fetch all the pages. However if I enable WPML I get this error when fetching any page that has a parent. It doesn't matter if the pages have translations or not.

Has anybody experienced something similar?

Thanks in advance for any feedback!

Adding a product to the cart is giving an error, while it is working with WPML and WPGraphQL WPML disabled. I tried to send the query from GraphiQL IDE, Postman and my Next.js app.

The query: mutation MyMutation { addToCart(input: {productId: 32009, clientMutationId: "asdasd", quantity: 1}) { cartItem { key } } }

The error: { "errors": [ { "debugMessage": "Call to a member function get_cart_from_session() on null", "message": "Internal server error", "extensions": { "category": "internal" }, "locations": [ { "line": 2, "column": 3 } ], "path": [ "addToCart" ], "trace": [ { "file": "/wp-content/plugins/wp-graphql-woocommerce/includes/mutation/class-cart-add-item.php", "line": 93, "call": "WPGraphQL\WooCommerce\Data\Mutation\Cart_Mutation::check_session_token()" },

The website: https://dev.supplybeaver.ca/ Versions: WPGraphQL WPML - 1.0.7 WPML Multilingual CMS - 4.5.1 WPGraphQL WooCommerce (WooGraphQL) - 0.10.6 WooCommerce - 5.9.0 WP GraphQL - 1.6.7

I am creating the same issue for WPGraphQL WooCommerce (WooGraphQL), as I don't know on which side exactly the issue is. I really hope that it will be possible to use a combination of these plugins on my website soon. Thank you!

Thank you to anyone who can help with this. Maybe my approach is wrong and you can tell me how you are getting the results I'm looking for.

fragment AuthorFields on User {
  name
  firstName
  lastName
  avatar {
    url
  }
}

fragment PostFields on Post {
  title
  excerpt
  slug
  date
  featuredImage {
    node {
      sourceUrl
    }
  }
  author {
    node {
      ...AuthorFields
    }
  }
  categories {
    edges {
      node {
        name
      }
    }
  }
  tags {
    edges {
      node {
        name
      }
    }
  }
}

fragment AdditionalFields on Post {
  content
  locale {
    locale
  }
  translations {
    post_title
    locale
    href
  }
  seo {
    metaDesc
    metaKeywords
    metaRobotsNofollow
    metaRobotsNoindex
    opengraphAuthor
    opengraphDescription
    focuskw
    cornerstone
    canonical
    breadcrumbs {
      text
      url
    }
    opengraphImage {
      altText
      link
      uri
      title
      sourceUrl
    }
    opengraphModifiedTime
    opengraphPublishedTime
    opengraphPublisher
    opengraphSiteName
    opengraphTitle
    opengraphType
    opengraphUrl
    title
    twitterDescription
    twitterTitle
    twitterImage {
      altText
      caption
      uri
      sourceUrl
    }
  }
}

query PostBySlug($id: ID!, $idType: PostIdType!) {
  post(id: $id, idType: $idType) {
    ...PostFields
    ...AdditionalFields
  }
}

query AllPosts($length: Int!, $after: String) {
  posts(first: $length, after: $after, where: {orderby: {field: DATE, order: DESC}}) {
    edges {
      node {
        title
        excerpt
        slug
        date
        featuredImage {
          node {
            sourceUrl
          }
        }
        author {
          node {
            name
            firstName
            lastName
            avatar {
              url
            }
          }
        }
      }
      cursor
    }
    pageInfo {
      hasNextPage
      hasPreviousPage
      startCursor
    }
  }
}

wp-graphlql is working fine for default language.

i installed wp-graphql-wpml but when i send my query. The data for for the second language is empty. It works fine with the GraphIQL.

My query query MyQuery { menus { nodes { name slug menuItems(where: {parentId: "null"}) { nodes { title label } } } } } response external { "name": "Hauptmenü", "slug": "hauptmenue", "menuItems": { "nodes": [] } }

response GraphIQL { "name": "Hauptmenü", "slug": "hauptmenue", "menuItems": { "nodes": [ { "title": null, "label": "Umsatzsteuer" } ] } }

do have any ideas? thanks for your reply

I have installed your plugin, but when I query posts it still only shows the posts in the default language.

How do I query all posts (regardless of language)?

Hello, thank you for your work.

My issue is that when a static page is set as "Page on front" in WordPress and the translation page for it is created, they have the following URI patterns in the CMS:

mydomain.com/
mydomain.com/LOCALE/

In other words, the front page slug or the post name is removed from the URL.

However, this is not the case when the translated page is retrieved in GraphQL. We have instead:

/
/LOCALE/translated-page-slug/

Can this issue be be addressed by this plugin or it should be fixed within a different layer?

Thanks.

So it always worked for me but for some reason menuItems is returning all Menu items from everywhere. My query is

query getNavItems {
  menuItems(where: {location: PRIMARY}) {
    nodes {
      title
      path
      label
      locations
    }
  }
}

And my response still is>

{
  "data": {
    "menuItems": {
      "nodes": [
        {
          "title": null,
          "path": "/register/",
          "label": "Register",
          "locations": null
        },
        {
          "title": null,
          "path": "/",
          "label": "Home",
          "locations": [
            "PRIMARY"
          ]
        },
        {
          "title": null,
          "path": "/support/",
          "label": "Support",
          "locations": null
        },
        {
          "title": null,
          "path": "/blog/",
          "label": "Blog",
          "locations": [
            "PRIMARY"
          ]
        },
        {
          "title": null,
          "path": "/try/",
          "label": "Try",
          "locations": null
        },
        {
          "title": null,
          "path": "/about/",
          "label": "About",
          "locations": [
            "PRIMARY"
          ]
        },
        {
          "title": null,
          "path": "/contact/",
          "label": "Contact",
          "locations": [
            "PRIMARY"
          ]
        },
        {
          "title": null,
          "path": "/pricing/",
          "label": "Pricing",
          "locations": [
            "PRIMARY"
          ]
        },
        {
          "title": null,
          "path": "/try/",
          "label": "Try",
          "locations": [
            "PRIMARY"
          ]
        },
        {
          "title": null,
          "path": "/pricing/",
          "label": "Pricing",
          "locations": [
            "PRIMARY"
          ]
        }
      ]
    }
  },
  "extensions": {
    "debug": [
      {
        "type": "DEBUG_LOGS_INACTIVE",
        "message": "GraphQL Debug logging is not active. To see debug logs, GRAPHQL_DEBUG must be enabled."
      }
    ]
  }
}

Hi,

I am using the last version of WPML and wordpress 5.6.1.

When I query the posts I get all the post but the translated post are also part of the request. For exemple if the last post is translated in two other languages I get 3 times the same post, one for each language.

The posts and the translations don't have the same post id so I suppose this is why I get them but is this an expected behavior or do I miss something to only query one language at the time?

I'm running into a problem when I query posts for different languages.

Versions used: WP GraphQL: 1.8.1 WPGraphQL WPML: 1.1.0

My GQL query looks like so:

export const getAllPostsForHome = gql`
  query AllPosts($locale: String) {
    posts(
      first: 6
      where: { orderby: { field: DATE, order: DESC }, wpmlLanguage: $locale }
    ) {
      nodes {
        content
        excerpt
        date
        title
        slug
        databaseId
        featuredImage {
          node {
            title
            sourceUrl
          }
        }
      }
    }
  }
`;

With the variable locale I assumed I can then query the posts like so:

export async function getStaticProps(context) {
  const { locale } = context;

  const posts = await client.query({
    query: getAllPostsForHome,
    variables: {
      wpmlLanguage: locale,
    },
  });

  return {
    props: {
      posts: posts.data.posts.nodes,
    },
    revalidate: 1,
  };
 }

Instead it queries all posts, the original including translated posts. I might be missing something here?

In Next.js I've setup i18n in the config file and works as expected. http://localhost:3000/ and http://localhost:3000/en works as expected except the posts.

Hey @rburgst ,

Just pushing a fix to a bug on the define for REST_REQUEST.

Also, added a bare minimum composer.json file in order to be able to add the package by using composer.

Thanks !

Hi,

I can query regionalized pages (like pages under /en-gb) on the WordPress graphQL IDE interface. But when Gatsby creates the nodes locally, those pages do not show on the local graphQL queries (using the same id as in the query above) and they show a 404 when I try to access them on the browser. Besides having the plugin installed, do I need to do anything special during the build process? Thanks,

After we updated to Wordpress 6.1.1, we no longer see the menu in other languages. GraphQL IDE does not retrieve the data either. GraphQL Version 1.13.7 and WPGraphQL WPML Version 1.1.0

When I'm making a query to get the posts page, translated page return false for value isPostsPage.

Reading settings is configured on the good page.

Query :

{
  pages(where: {name: "blog"}) {
    nodes {
      uri
      isPostsPage
    }
  }
}

Result

{
"data": {
    "pages": {
      "nodes": [
        {
          "uri": "/blog/",
          "isPostsPage": true
        },
        {
          "uri": "/fr/blog/",
          "isPostsPage": false
        }
      ]
    }
  }
}

Fixes the issue where language filtering did not work on relationships between taxonomies and post types.

For example, the following query would return the posts associated to each category in the default language (english in my case), even if the categories are in french:

categories(where: {wpmlLanguage: "fr"}) {
  nodes {
    id
    name
    posts {
      nodes {
        title
      }
    }
  }
}

I expected to received the linked posts in the same language as my category.

My fix allows us to add the same wpmlLanguage filter on the child queries which will return the posts in the same language as the category:

categories(where: {wpmlLanguage: "fr"}) {
  nodes {
    id
    name
    posts(where: {wpmlLanguage: "fr"}) {
      nodes {
        title
      }
    }
  }
}

This fix works for the relationship between posts and categories, but il also works with any relationships between custom taxonomies and custom post types.

In an ideal world, we would not have to do this, but this is the fix I came up with. Feel free to do what you want with it.

I can't see the translated categories in the GraphQL. The below only shows the 3 categories in the default language - and not the translated categories.

Similar issue happened with my menus - if you go into a translated menu and then save it, it will then remove all translated menus from the graphql.

query MyQuery { terms(where: {taxonomies: CATEGORY}) { edges { node { id link name ... on Category { id name } taxonomyName uri } } } }

Overview

Enables support for taxonomy term translations that return the correct translated IDs and objects for terms in non-default locales.

Details

Adds fields to Taxonomy types to be visible on the terms:

• locale - the locale of the current term
• translations - list of TermTranslation objects
• translated - list of the translated Term objects

Adds two hooks to resolve the issues with WPML term ID adjustment. Basically, WPML adjusts term ids for every request, shifting request terms to the "current language". The WPGraphQL requests don't typically use a current language and that's especially the case with Gatsby. We want to retrieve all of the terms at once and let Gatsby handle the language switching. These two hooks ensure that term IDs are untouched during GraphQL requests allowing retrieval of non-default locale terms.

Adds a slug field to the term translation response to help in the situation where the same slug is used for terms in different locales. The example in the commit message shows what it would look like for the tech tag in two locales:

• English

  • slug: tech
  • href: https://.../tag/tech

• Spanish

  • slug: tech
  • href: https://.../es/tag/tech-2

Having the slug allows the client to do what it needs - in our case, it was building out tag pages with the correct tag in the route.

I've also included all of this context and more in the commit messages.