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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...