-
Notifications
You must be signed in to change notification settings - Fork 66
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
Asset transforms (in nested blocks) do not work with GraphQL queries #638
Comments
So far, I've found that this line in Craft returns an empty array for this query, making the eager loading break down. That means I'm not yet sure if the issue is on Neo's or Craft's end, though, but I'll keep looking into it. |
Just wanted to update that I've made progress on this today which seems to be working. Will need to do more testing to make sure it hasn't had any undesired side effects, but hopefully I can release the fix by the end of the week. |
Just released Neo 3.3.6 with the fix for this. |
Is there any possibility that this issue came back? Got the same behavior with latest Craft and Neo relase! |
I've just tested this and it worked as expected. Can you confirm whether this happens if you set up a test from a fresh Craft install? |
Me again, the issue has made a comeback on a new project, Craft CMS v4.10.7, Neo v4.2.9 |
@jesuismaxime if you're able to reliably reproduce that with GraphiQL, if possible could you please send your Composer files, database backup, and example GraphQL query to [email protected] and I'll have a look. |
Description
Transforms on Asset field (in nested blocks) aren't working as expected.
The following segment work fine in relation fields (see
relationEntryPage
above) but is doing afit
instead acrop
on a direct block fieldThe GQL query
The Result
As you can see above; the first image (link to a page through
relationEntryPage
is working fine, the image is crop. But in the second image (image
field attach to the blocklayout_BlockCtaNextPage_BlockType
is doing a resize.The issue also appear on other blocks in our
layout
field. So this is not isloated to one block. Plus; it appears on all our local machine + our staging environment.The query above was tested in GraphiQL interface, so this is not a "front-end" issue.
Other information
The text was updated successfully, but these errors were encountered: