Jump to content
dadish

GraphQL for ProcessWire

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites
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.

  • Like 1

Share this post


Link to post
Share on other sites
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.

  • Like 2

Share this post


Link to post
Share on other sites

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.

  • Like 1

Share this post


Link to post
Share on other sites

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 by dragan
typo

Share this post


Link to post
Share on other sites
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.

  • Like 1

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites
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.

  • Like 5

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites
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?

  • Like 1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

@charger I don't think that hashing graphql queries would cause performance problems. They are not that big. You should be fine.

  • Like 1

Share this post


Link to post
Share on other sites

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.

  • Like 12
  • Thanks 4

Share this post


Link to post
Share on other sites

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

  • Like 5

Share this post


Link to post
Share on other sites

@dadish Great news indeed! Big thanks for this rewrite. Can't wait to try it out (probably not before the weekend).

  • Like 1

Share this post


Link to post
Share on other sites

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

  • Like 5

Share this post


Link to post
Share on other sites

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 by dadish
grammar
  • Like 5

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites
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.

  • Like 1

Share this post


Link to post
Share on other sites
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).

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...