Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.13.7]: Descenants in GraphQL broke #16382

Open
kennethdenhollander opened this issue Jan 3, 2025 · 3 comments
Open

[4.13.7]: Descenants in GraphQL broke #16382

kennethdenhollander opened this issue Jan 3, 2025 · 3 comments

Comments

@kennethdenhollander
Copy link

kennethdenhollander commented Jan 3, 2025

What happened?

Description

Since update 4.13.7 there was a fix for GraphQL, however after this update trying a 'descendants' query, it always returns an empty result. We rolled back to version 4.13.5 and we got back an array of 'descendants' again.

Steps to reproduce

Create a similar GraphQL query in the GraphiQL like below and make sure to use a section that has hierarchy enabled.

query facilities {
  facilities: entries(section: "facilities") {
    id
    title
    descendants {
      id
    }
  }
}

Expected behavior

We expect an array of facilities returned on the 'descendants' property.

Actual behavior

There is never a descendant returned after version 4.13.7

Craft CMS version

4.13.7

PHP version

8.1.31

Operating system and version

Linux 4.18.0-513.9.1.lve.el8.x86_64

Database type and version

MariaDB 10.6.20

Image driver and version

Imagick 3.7.0 (ImageMagick 7.1.1-39)

Installed plugins and versions

@kennethdenhollander kennethdenhollander changed the title [4.13.7]: Descenants in GraphQL [4.13.7]: Descenants in GraphQL broke Jan 3, 2025
@brandonkelly
Copy link
Member

I’m unable to reproduce that. Any chance you can share your database and Composer files, plus any custom plugins or modules with us, so we can test with your site on our end? If so, please send them to support@craftcms.com.

@brandonkelly
Copy link
Member

We had a similar report (but for children) come in right before yours (#16381). In that case, they are only able to reproduce it on their hosted environment, but not on a local dev environment. Any chance you’re seeing the same? And if so, where are you hosted?

@kennethdenhollander
Copy link
Author

kennethdenhollander commented Jan 6, 2025

As you mentioned for the other issue, there is no problem in de (local) development environment only on production. We run our own hosting servers, what kind of information do you need to be able to check?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants