kongondo Posted December 18, 2018 Share Posted December 18, 2018 41 minutes ago, bernhard said: I guess I need to try GraphQL Yes. They say it's the next big thing since...eh, the last next big thing ?.... https://medium.freecodecamp.org/a-beginners-guide-to-graphql-60e43b0a41f5 https://blog.apollographql.com/graphql-vs-rest-5d425123e34b https://graphql.org/ https://www.prisma.io/blog/top-5-reasons-to-use-graphql-b60cfa683511/ https://medium.com/open-graphql/graphql-1-140fab436942 ...and some reasons why you may want to avoid using it... https://www.robinwieruch.de/why-graphql-advantages-disadvantages-alternatives/ https://blog.logrocket.com/5-reasons-you-shouldnt-be-using-graphql-61c7846e7ed3 1 1 Link to comment Share on other sites More sharing options...
dotnetic Posted December 18, 2018 Share Posted December 18, 2018 8 hours ago, bernhard said: I guess I need to try GraphQL and hope to find some time for that soon... Hey @bernhard, thats the same what I want to do, since a while, but time is also missing. I want to figure out, how to get the data into ag-grid/RockGrid. I hope to start experiments between christmas and new years eve. I think GraphQL is much easier than using MySQL queries and has one big advantage (at least for me) over using direct SQL queries: The GraphQL processwire module respects access rights and only returns results that the user has access to. One problem with RockGrid is that there is currently no way to display only entries that the user has access to. Or you would have to include this in the SQL query. Link to comment Share on other sites More sharing options...
bernhard Posted December 18, 2018 Share Posted December 18, 2018 @jmartsch now you can: Link to comment Share on other sites More sharing options...
sodesign Posted February 7, 2019 Share Posted February 7, 2019 Hello, Thanks for all your work on this module, it's a joy to use! I have a question around modifying a mutation, and am not sure how the ___getMutation Hook works. I normally use TracyDebugger but using Tracy with this module seems to break (all graphql responses throw a json error) How do I modify the value of a field in a mutation using the getMutation hook? Thanks, Tom Edit - to clarify - I'm generating a base64 image in vuejs on the front end, and need to save this to an image field. I'm planning to do this by sending the base64 string as part of the request (I'm using vue apollo) - and then intercepting this with a hook, creating and saving as a png file in a temporary directory, and then setting this as the PageImage url in the query. Link to comment Share on other sites More sharing options...
dragan Posted March 3, 2019 Share Posted March 3, 2019 I noticed that this module is actually quite slow in the backend. A native PW query in the Tracy Console takes 27ms, and the equivalent GraphQL query >6s (TTFB in the inspector network panel). Is that because of the overhead of the GraphQL playground frontend assets? Or in other words, would a real-life request take also that long? Link to comment Share on other sites More sharing options...
dadish Posted March 3, 2019 Author Share Posted March 3, 2019 21 minutes ago, dragan said: I noticed that this module is actually quite slow in the backend. A native PW query in the Tracy Console takes 27ms, and the equivalent GraphQL query >6s (TTFB in the inspector network panel). Is that because of the overhead of the GraphQL playground frontend assets? Or in other words, would a real-life request take also that long? GraphQL requests are slow for sure, but 6 seconds is a bit too much. In my cases it usually took around 200-300ms. Not sure what's causing it to be so slow on your end. 1 Link to comment Share on other sites More sharing options...
dadish Posted March 3, 2019 Author Share Posted March 3, 2019 On 2/8/2019 at 12:00 AM, sodesign said: Edit - to clarify - I'm generating a base64 image in vuejs on the front end, and need to save this to an image field. I'm planning to do this by sending the base64 string as part of the request (I'm using vue apollo) - and then intercepting this with a hook, creating and saving as a png file in a temporary directory, and then setting this as the PageImage url in the query. Unfortunately the getMotationHook requires you to use the Youshido/GraphQL library that this module depends on. The issue with it, is that the youshido/graphql is not maintained anymore. Which means that I'll be rewriting GraphQL module to get red of it and use some other library. So I can't give you the correct solution because it's being deprecated at the moment, and I can't tell when I'll finish the migration to another php graphql library because I'm limited with my spare time. Sorry for replying this late, I hope you found a solution. 2 Link to comment Share on other sites More sharing options...
sodesign Posted March 4, 2019 Share Posted March 4, 2019 No problem, thanks for the clarification. In the end I solved this by saving the base64 image as a text field, and I'm planning to use an on page-created hook to convert this to an image in a more PW way. I look forward to seeing where this plugin goes; even in its early form it's been very helpful. 1 Link to comment Share on other sites More sharing options...
dragan Posted March 26, 2019 Share Posted March 26, 2019 (edited) I was spending some more time with this module, and have tried various queries. The exact same query with JS + graphQL: 6s. PW inside Tracy (and JSON output): 0.177s (tried several times) Does the number of allowed fields and templates play a role with performance? Edited March 26, 2019 by dragan typo Link to comment Share on other sites More sharing options...
dadish Posted March 26, 2019 Author Share Posted March 26, 2019 1 hour ago, dragan said: Does the number of allowed fields and templates play a role with peformance? Yes it does. The more fields and templates are enabled the bigger the schema, the bigger the response time. 1 Link to comment Share on other sites More sharing options...
dragan Posted March 26, 2019 Share Posted March 26, 2019 well then... that explains it. I had allowed approx. 4 dozen fields. Roughly 40% of these are page-ref fields. Is that a general graphQL (architectural) performance issue, or just with this particular PHP library in particular? (which, as I have noticed, is not being maintained anymore) Link to comment Share on other sites More sharing options...
dadish Posted March 26, 2019 Author Share Posted March 26, 2019 17 minutes ago, dragan said: Is that a general graphQL (architectural) performance issue, or just with this particular PHP library in particular? (which, as I have noticed, is not being maintained anymore) I'm not sure if I can blame the PHP library alone. It definitely could be one of the things that contribute to poor performance. But there are many more things going on. For example permissions is a big one. The schema needs to check the permissions for each field and subfields. So if you have lots of page-refs and fetching their subfields, it will check if the user has permission to view those fields. When you make a query inside your templates, the script already got access and don't do permission checks manually. It needs to be improved. Performance is very important. But right now I'm dealing with PHP library deprecation, because it's not maintained anymore. 5 Link to comment Share on other sites More sharing options...
charger Posted November 1, 2019 Share Posted November 1, 2019 I implemented a very basic caching strategy for GraphQL queries with the help of PW’s native $cache methods. Here’s how my graphql.php template looks like: <?php namespace ProcessWire; $namespace = 'graphql'; $serializedQuery = file_get_contents('php://input'); $cacheName = hash('md5', $serializedQuery); $cacheData = $cache->getFor($namespace, $cacheName); if (!$cacheData) { $cacheData = $modules->get('ProcessGraphQL')->executeGraphQL(); $cacheSaved = $cache->saveFor($namespace, $cacheName, $cacheData, $expire = 604800); $log->save('graphql', "cache saved $cacheSaved with name $cacheName"); } echo json_encode($cacheData, true); When saving a page in the backend, for now I just clear the whole cache associated with this namespace (inside ready.php ) <?php namespace ProcessWire; $pages->addHookAfter('saveReady', function($event) { $deleted = wire('cache')->deleteFor('graphql'); if ($deleted) wire('log')->save('graphql', 'cache deleted'); }); Serializing the whole query just to get a unique cache name obviously isn’t optimal. How about if the module supported globally unique IDs that could then be used as cache name instead? 1 Link to comment Share on other sites More sharing options...
dadish Posted November 1, 2019 Author Share Posted November 1, 2019 1 hour ago, charger said: Serializing the whole query just to get a unique cache name obviously isn’t optimal. How about if the module supported globally unique IDs that could then be used as cache name instead? The link you're referring to talks about the caching on the client side, not server. And we already have unique id for all the objects. They are page ids and are enabled by default. But that wont help you with caching on the server side. I think using a hash of your queries as a cache name is perfectly reasonable solution. Why do you feel uncomfortable with it? 1 Link to comment Share on other sites More sharing options...
charger Posted November 2, 2019 Share Posted November 2, 2019 My idea was to move the logic to get a unique cache name from the server to the client (by setting an ID for a query just like in the linked example) and then use that ID on the server for caching purposes. I was mainly worried that there might be a performance problem with creating hashes from complex queries, but I have no data to back that up. Link to comment Share on other sites More sharing options...
dadish Posted November 19, 2019 Author Share Posted November 19, 2019 @charger I don't think that hashing graphql queries would cause performance problems. They are not that big. You should be fine. 1 Link to comment Share on other sites More sharing options...
dadish Posted November 19, 2019 Author Share Posted November 19, 2019 New version release! 1.0.2 I am very happy to inform you guys that the new major version of the module is out. ⚠️ WARNING: Breaking Changes! ⚠️ The module was rewritten to use webonyx/graphql-php instead of youshido/graphql. This was a big issue because the latter was not properly maintained anymore and the webonyx/graphql-php gone very further in development and supports more features that we need. There are some more breaking changes that are listed on the latest release page. What's new trash(id: ID!): Page! field allows to move pages to trash via GraphQL api. Solves N+1 problem for FieldtypePage field. Significantly improves response speed! Support for even more ProcessWire permissions. Now the full list is: page-add page-create page-delete page-edit page-move page-view page-edit-created page-edit-trash-created It is already available in ProcessWire's modules directory. So you can install it via class name. 12 4 Link to comment Share on other sites More sharing options...
sodesign Posted November 19, 2019 Share Posted November 19, 2019 This is great news! I love using the module, makes integrating Vue with processwire powerful. The only difficulty I had was with the N+1 with FieldtypePage, thrilled this is solved ? Thank you for all your work @dadish 5 Link to comment Share on other sites More sharing options...
dragan Posted November 19, 2019 Share Posted November 19, 2019 @dadish Great news indeed! Big thanks for this rewrite. Can't wait to try it out (probably not before the weekend). 1 Link to comment Share on other sites More sharing options...
flydev Posted November 19, 2019 Share Posted November 19, 2019 Damn, too much work coming on ? Thanks for the new version @dadish ? 2 Link to comment Share on other sites More sharing options...
nbcommunication Posted November 22, 2019 Share Posted November 22, 2019 Haha, I spent last week working on a GraphQL API module built upon the webonyx library! Not wasted time though, I think I've probably implemented a few things that would be welcome additions (e.g. WireCache for $pages->find()). When I get a chance I'll have a look at the new version of this module and see whether I can suggest any additions. Cheers, Chris 5 Link to comment Share on other sites More sharing options...
dadish Posted November 23, 2019 Author Share Posted November 23, 2019 (edited) New Version Release: 1.0.3 - Improves performance for FieldtypeFile & FieldtypeImage fields. @dragan Looking forward to your feedback. I'm still very curious how you managed to get 6s response time from GraphQL. Let me know how the latest version works for you. @nbcommunication That's great to hear! Any involvement is absolutely welcome. If you have your module available on github or some other place I would love to look at your approach and maybe steal some ideas ?. Also, if your implementation is different than mine I would encourage you to finish it. We will only benefit from different approaches. Edited November 23, 2019 by dadish grammar 5 Link to comment Share on other sites More sharing options...
dragan Posted November 24, 2019 Share Posted November 24, 2019 I finally found some time to install the brandnew version and do some tests. I made sure I cleared the modules cache, and cleared file compiler cache. But I get some strange behaviour in the test-tool (pw-admin/setup/graphql/) : Did anything major change in regards to query syntax? This used to work previously: Spoiler { project(s: "industry%=verwaltung, sort=-year, limit=50") { list { year budget title project_desc_short product { list { title } } images { url httpUrl description width height } } } } Now I get lots of errors. Even something smaller throws errors: Spoiler { project(s: "industry%=verwaltung, sort=-year, limit=50") { list { year client_name budget title } } } If I remove "budget" field, it works. I double-checked it's in the allowed fields in the module config. Something similar happens when I include images, and some pages don't have images. i.e. With this selector it works as expected: project(s: "industry%=verwaltung, images.count>0, sort=-year, limit=3") If I just do project(s: "industry%=verwaltung, sort=-year, limit=3") { I get stuff like this: Spoiler { "errors": [ { "debugMessage": "Expected a value of type \"Int\" but received: (empty string)", "message": "Internal server error", "extensions": { "category": "internal" }, "locations": [ { "line": 5, "column": 7 } ], "path": [ "project", "list", 1, "budget" ], "trace": [ { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 846, "call": "GraphQL\\Executor\\ReferenceExecutor::completeLeafValue(GraphQLType: Int, (empty string))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 726, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValue(GraphQLType: Int, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(4), (empty string))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 677, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueWithLocatedError(GraphQLType: Int, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(4), (empty string))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 567, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueCatchingError(GraphQLType: Int, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(4), (empty string))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1247, "call": "GraphQL\\Executor\\ReferenceExecutor::resolveField(GraphQLType: ProjectPage, instance of ProcessWire\\Page(0), instance of ArrayObject(1), array(4))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1201, "call": "GraphQL\\Executor\\ReferenceExecutor::executeFields(GraphQLType: ProjectPage, instance of ProcessWire\\Page(0), array(3), instance of ArrayObject(6))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1163, "call": "GraphQL\\Executor\\ReferenceExecutor::collectAndExecuteSubfields(GraphQLType: ProjectPage, instance of ArrayObject(1), array(3), instance of ProcessWire\\Page(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 853, "call": "GraphQL\\Executor\\ReferenceExecutor::completeObjectValue(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(3), instance of ProcessWire\\Page(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 726, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValue(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(3), instance of ProcessWire\\Page(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 677, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueWithLocatedError(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(3), instance of ProcessWire\\Page(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 952, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueCatchingError(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(3), instance of ProcessWire\\Page(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 821, "call": "GraphQL\\Executor\\ReferenceExecutor::completeListValue(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(2), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 726, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValue(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(2), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 677, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueWithLocatedError(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(2), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 567, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueCatchingError(GraphQLType: ProjectPage, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(2), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1247, "call": "GraphQL\\Executor\\ReferenceExecutor::resolveField(GraphQLType: ProjectPageArray, instance of ProcessWire\\PageArray(3), instance of ArrayObject(1), array(2))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1201, "call": "GraphQL\\Executor\\ReferenceExecutor::executeFields(GraphQLType: ProjectPageArray, instance of ProcessWire\\PageArray(3), array(1), instance of ArrayObject(1))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1163, "call": "GraphQL\\Executor\\ReferenceExecutor::collectAndExecuteSubfields(GraphQLType: ProjectPageArray, instance of ArrayObject(1), array(1), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 853, "call": "GraphQL\\Executor\\ReferenceExecutor::completeObjectValue(GraphQLType: ProjectPageArray, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(1), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 726, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValue(GraphQLType: ProjectPageArray, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(1), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 677, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueWithLocatedError(GraphQLType: ProjectPageArray, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(1), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 567, "call": "GraphQL\\Executor\\ReferenceExecutor::completeValueCatchingError(GraphQLType: ProjectPageArray, instance of ArrayObject(1), instance of GraphQL\\Type\\Definition\\ResolveInfo, array(1), instance of ProcessWire\\PageArray(3))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 1247, "call": "GraphQL\\Executor\\ReferenceExecutor::resolveField(GraphQLType: Query, instance of ProcessWire\\Pages, instance of ArrayObject(1), array(1))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 257, "call": "GraphQL\\Executor\\ReferenceExecutor::executeFields(GraphQLType: Query, instance of ProcessWire\\Pages, array(0), instance of ArrayObject(1))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/ReferenceExecutor.php", "line": 208, "call": "GraphQL\\Executor\\ReferenceExecutor::executeOperation(instance of GraphQL\\Language\\AST\\OperationDefinitionNode, instance of ProcessWire\\Pages)" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/Executor/Executor.php", "line": 155, "call": "GraphQL\\Executor\\ReferenceExecutor::doExecute()" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/GraphQL.php", "line": 165, "call": "GraphQL\\Executor\\Executor::promiseToExecute(instance of GraphQL\\Executor\\Promise\\Adapter\\SyncPromiseAdapter, instance of GraphQL\\Type\\Schema, instance of GraphQL\\Language\\AST\\DocumentNode, instance of ProcessWire\\Pages, null, null, null, null)" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/vendor/webonyx/graphql-php/src/GraphQL.php", "line": 98, "call": "GraphQL\\GraphQL::promiseToExecute(instance of GraphQL\\Executor\\Promise\\Adapter\\SyncPromiseAdapter, instance of GraphQL\\Type\\Schema, '{\n project(s: \"industry%=verwaltung, sort=-year, limit=3\") {\n list {\n year\n budget\n title\n project_desc_short\n product {\n list {\n title\n }\n }\n images {\n url\n httpUrl\n description\n width\n height\n }\n }\n }\n}\n', instance of ProcessWire\\Pages, null, null, null, null, null)" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/ProcessGraphQL.module", "line": 185, "call": "GraphQL\\GraphQL::executeQuery(instance of GraphQL\\Type\\Schema, '{\n project(s: \"industry%=verwaltung, sort=-year, limit=3\") {\n list {\n year\n budget\n title\n project_desc_short\n product {\n list {\n title\n }\n }\n images {\n url\n httpUrl\n description\n width\n height\n }\n }\n }\n}\n', instance of ProcessWire\\Pages, null, null)" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 380, "call": "ProcessWire\\ProcessGraphQL::___executeGraphQL()" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 813, "call": "ProcessWire\\Wire::_callMethod('___executeGraphQL', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\ProcessGraphQL, 'executeGraphQL', array(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/ProcessGraphQL/ProcessGraphQL.module", "line": 81, "call": "ProcessWire\\Wire::__call('executeGraphQL', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 380, "call": "ProcessWire\\ProcessGraphQL::___execute()" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 813, "call": "ProcessWire\\Wire::_callMethod('___execute', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\ProcessGraphQL, 'execute', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/ProcessController.php", "line": 337, "call": "ProcessWire\\Wire::__call('execute', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 380, "call": "ProcessWire\\ProcessController::___execute()" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 813, "call": "ProcessWire\\Wire::_callMethod('___execute', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\ProcessController, 'execute', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/admin.php", "line": 150, "call": "ProcessWire\\Wire::__call('execute', array(0))" }, { "file": "/home/mysitecom/www/subdir/site/modules/AdminThemeUikit/controller.php", "line": 15, "function": "require('/home/mysitecom/www/subdir/wire/core/admin.php')" }, { "file": "/home/mysitecom/www/subdir/site/assets/cache/FileCompiler/site/templates/admin.php", "line": 15, "function": "require('/home/mysitecom/www/subdir/site/modules/AdminThemeUikit/controller.php')" }, { "file": "/home/mysitecom/www/subdir/wire/core/TemplateFile.php", "line": 287, "function": "require('/home/mysitecom/www/subdir/site/assets/cache/FileCompiler/site/templates/admin.php')" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 380, "call": "ProcessWire\\TemplateFile::___render()" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 813, "call": "ProcessWire\\Wire::_callMethod('___render', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\TemplateFile, 'render', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/modules/PageRender.module", "line": 514, "call": "ProcessWire\\Wire::__call('render', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 383, "call": "ProcessWire\\PageRender::___renderPage(instance of ProcessWire\\HookEvent)" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 813, "call": "ProcessWire\\Wire::_callMethod('___renderPage', array(1))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\PageRender, 'renderPage', array(1))" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 914, "call": "ProcessWire\\Wire::__call('renderPage', array(1))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\Page(0), 'render', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/modules/Process/ProcessPageView.module", "line": 208, "call": "ProcessWire\\Wire::__call('render', array(0))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 383, "call": "ProcessWire\\ProcessPageView::___execute(true)" }, { "file": "/home/mysitecom/www/subdir/wire/core/WireHooks.php", "line": 813, "call": "ProcessWire\\Wire::_callMethod('___execute', array(1))" }, { "file": "/home/mysitecom/www/subdir/wire/core/Wire.php", "line": 442, "call": "ProcessWire\\WireHooks::runHooks(instance of ProcessWire\\ProcessPageView, 'execute', array(1))" }, { "file": "/home/mysitecom/www/subdir/index.php", "line": 55, "call": "ProcessWire\\Wire::__call('execute', array(1))" } ] } ], "data": { "project": { "list": [ { "year": 2018, "budget": 12345, "title": "User Interface für xxx", "project_desc_short": "Das Lorem Ipsum dolor site amet....", "product": { "list": [] }, "images": [] }, { "year": 2018, "budget": null, "title": "Neue Website für ...", "project_desc_short": "Das Lorem Ipsum dolor site amet....", "product": { "list": [] }, "images": [] }, { "year": 2017, "budget": 31156, "title": "something else...", "project_desc_short": "Das Lorem Ipsum dolor site amet....", "product": { "list": [] }, "images": [] } ] } } } Funny thing is, the output at the bottom after "data": { "project": { "list": [) still looks OK to me. Do I see these error messages only because the site is in debug-mode? Or because I do this in the backend as superuser? Link to comment Share on other sites More sharing options...
dadish Posted November 24, 2019 Author Share Posted November 24, 2019 6 minutes ago, dragan said: Do I see these error messages only because the site is in debug-mode? Yes. In debug mode it will return very verbose error messages. But ideally it should not return any errors. All my success tests check if the response has data in it and does not assert that there are no errors. So it might be that I have those errors as well, just didn't catch them. I'll try to reproduce your case and fix it. 10 minutes ago, dragan said: If I remove "budget" field, it works. I double-checked it's in the allowed fields in the module config. What type of field your budget field is? I assume integer, but want to be certain. 1 Link to comment Share on other sites More sharing options...
dragan Posted November 24, 2019 Share Posted November 24, 2019 1 minute ago, dadish said: What type of field your budget field is? I assume integer, but want to be certain. Yes, just a regular integer field. I was just thinking... Most fields in the pages / template I'm querying are optional. Granted, I didn't do extensive testing so far, but I guess it throws errors each time when there is no value in a field. (hence, the selector "only show if images.count > 0" was working fine). Could that be? Earlier it just outputted empty nodes or null instead (which I would expect and is totally fine). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now