-
Notifications
You must be signed in to change notification settings - Fork 641
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.x]: GraphQl: Tried to load an unregistered type "*_MatrixField" #13622
Comments
got same error after upgrade to 4.5.2 last day.. on production.. |
I've got the same issue on both 4.5.2 and 4.5.3. I've rolled back to 4.4.17 for now.
If I used the type "QueryArgument" instead I get this error:
The mutation looks like this: mutation editActivity(
$id: ID!,
$timeDates: [activityTimeDates_MatrixBlockContainerInput]
$timeDatesSortOrder: [QueryArgument],
) {
save_activities_Entry(
id: $id
activityTimeDates: {blocks: $timeDates, sortOrder: $timeDatesSortOrder}
) {
timeDates: activityTimeDates {
... on activityTimeDates_day_BlockType {
id
}
}
}
} |
I'm experiencing the same issue, but when querying *_NeoFields. There's no rhyme nor reason why some queries work and others that also include the same fields, don't. |
Hi all, thanks for reporting! I’ve narrowed it down to GQL lazy-loading improvements introduced in v4.5. I’m working on a solution now. |
This is now fixed for the next release! You can get it early by changing your |
FYI, I also hit this bug and as long as I added a |
Craft 4.5.4 is out with this fix. |
What happened?
Description
Trying to use a MatrixField type on a fragment fails in DEV_MODE=false.
Steps to reproduce
Expected behavior
I expected the graphql output to work:
Actual behavior
The output is just something went wrong, attached is a the error message in the logs:
Error Log
From storage/logs/*
Craft CMS version
Craft Pro 4.5.3
PHP version
8.2.0
Operating system and version
Darwin 22.5.0
Database type and version
MySQL 5.7.39
Image driver and version
GD 8.2.0
Installed plugins and versions
none
The text was updated successfully, but these errors were encountered: