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 jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...