Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.4.1
-
None
-
Yes
Description
Steps to reproduce
- Install Ibexa DXP v4
- Add a new language e.g. fre-FR (BO and yaml file)
- Create a CT with ezdate, ezauthor, ezdatetime, ezboolean, ezfloat, ezinteger, and ezkeyword fields without translation
- Regenerate graphQL schema
- Create content from created CT
- Publish
- Execute a query similar to the following:
{ content { testt(contentId: 73){ date_gb: field6437d5fe8a3d8(language: fre_FR){ timestamp }, datetime_gb:field6437d6078308b(language: fre_FR){ timestamp }, author_gb: field6437d60d8236b(language: fre_FR){ name }, boolean_gb: field6437d6196ea1e(language: fre_FR), float_gb: field6437d620da7a3(language: fre_FR), integer_gb: field6437d622917f5(language: fre_FR), keyword_gb: field6437d624f344b(language: fre_FR), } } }
Result
instead of the result is the following error message
"errors": [ { "debugMessage": "Ibexa\\GraphQL\\Resolver\\ItemResolver::resolveItemFieldValue(): Return value must be of type Ibexa\\GraphQL\\Value\\Field, null returned", "message": "Internal server Error", "extensions": { "category": "internal" },
Expected:
the result should look like with other fields, i.e. null value returned
{ "data": { "content": { "testt": { "date_gb": null, "datetime_gb": null, "author_gb": null, "boolean_gb": null, "float_gb": null, "integer_gb": null, "keyword_gb": null } } } }
Designs
Attachments
Issue Links
- relates to
-
IBX-5329 GraphQL throws an error if we query content with a non-existent translation
- Closed