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 horst
      ---------------------------------------------------------------------------------------------------------------------------------
        when working with PW version 2.6+, please use Pim2, not Pim!
        read more here  on how to change from the older to the newer version in existing sites
      ---------------------------------------------------------------------------------------------------------------------------------
      PageImage Manipulator, API for version 1 & 2

      The Page Image Manipulator is a module that let you in a first place do ImageManipulations with your PageImages. - And in a second place there is the possibility to let it work on any imagefile that exists in your servers filesystem, regardless if it is a 'known PW-image'.

      The Page Image Manipulator is a Toolbox for Users and Moduledevelopers. It is written to be as close to the Core ImageSizer as possible. Besides the GD-filterfunctions it contains resize, crop, canvas, rotate, flip, sharpen, unsharpMask and 3 watermark methods.



      How does it work?

      You can enter the ImageManipulator by calling the method pim2Load(). After that you can chain together how many actions in what ever order you like. If your manipulation is finished, you call pimSave() to write the memory Image into a diskfile. pimSave() returns the PageImage-Object of the new written file so we are able to further use any known PW-image property or method. This way it integrates best into the ProcessWire flow.

      The three examples above put out the same visual result: a grayscale image with a width of 240px. Only the filenames will slightly differ.

      You have to define a name-prefix that you pass with the pimLoad() method. If the file with that prefix already exists, all operations are skipped and only the desired PageImage-Object gets returned by pimSave(). If you want to force recreation of the file, you can pass as second param a boolean true: pim2Load('myPrefix', true).

      You may also want to get rid of all variations at once? Than you can call $pageimage->pim2Load('myPrefix')->removePimVariations()!

      A complete list of all methods and actions are at the end of this post.
       
      You may also visit the post with tips & examples for users and module developers.


      How to Install
      Download the module Place the module files in /site/modules/PageImageManipulator/ In your admin, click Modules > Check for new modules Click "install" for PageImageManipulator Done! There are no configuration settings needed, just install and use it. Download    (version 0.2.0)
      get it from the Modules Directory History of origins

      http://processwire.com/talk/topic/3278-core-imagemanipulation/


      ----------------------------------------------------------------------------------------------------------


      Page Image Manipulator - Methods

      * pimLoad  or  pim2Load, depends on the version you use!

      pimLoad($prefix, $param2=optional, $param3=optional)
      param 1: $prefix - (string) = mandatory! param 2: mixed, $forceRecreation or $options param 3: mixed, $forceRecreation or $options return: pim - (class handle) $options - (array) default is empty, see the next method for a list of valid options! $forceRecreation - (bool) default is false It check if the desired image variation exists, if not or if forceRecreation is set to true, it prepares all settings to get ready for image manipulation
      -------------------------------------------------------------------

      * setOptions

      setOptions(array $options)
      param: $options - (array) default is empty return: pim - (class handle) Takes an array with any number valid options / properties and set them by replacing the class-defaults and / or the global config defaults optionally set in the site/config.php under imageSizerOptions or imageManipulatorOptions.

      valid options are:
      quality = 1 - 100 (integer) upscaling = true | false (boolean) cropping = true | false (boolean) autoRotation =true | false (boolean) sharpening = 'none' | 'soft' | 'medium' | 'strong' (string) bgcolor = (array) css rgb or css rgba, first three values are integer 0-255 and optional 4 value is float 0-1, - default is array(255,255,255,0) thumbnailColorizeCustom = (array) rgb with values for colorize, integer -255 - 255 (this can be used to set a custom color when working together with Thumbnails-Module)
        outputFormat = 'gif' | 'jpg' | 'png' (Attention: outputFormat cannot be specified as global option in $config->imageManipulatorOptions!) set {singleOption} ($value)
      For every valid option there is also a single method that you can call, like setQuality(90), setUpscaling(false), etc.
      -------------------------------------------------------------------

      * pimSave

      pimSave()
      return: PageImage-Object If a new image is hold in memory, it saves the current content into a diskfile, according to the settings of filename, imagetype, targetFilename and outputFormat. Returns a PageImage-Object!
      -------------------------------------------------------------------

      * release

      release()
      return: void (nothing) if you, for what ever reason, first load image into memory but than do not save it, you should call release() to do the dishes! 😉 If you use pimSave() to leave the ImageManipulator, release() is called automatically.
      -------------------------------------------------------------------

      * getOptions

      getOptions()
      return: associative array with all final option values example:
      ["autoRotation"] bool(true) ["upscaling"] bool(false) ["cropping"] bool(true) ["quality"] int(90) ["sharpening"] string(6) "medium" ["targetFilename"] string(96) "/htdocs/site/assets/files/1124/pim_prefix_filename.jpg" ["outputFormat"] string(3) "jpg" get {singleOption} ()
      For every valid option there is also a single method that you can call, like getQuality(), getUpscaling(), etc. See method setOptions for a list of valid options!
      -------------------------------------------------------------------

      * getImageInfo

      getImageInfo()
      return: associative array with useful informations of source imagefile example:
      ["type"] string(3) "jpg" ["imageType"] int(2) ["mimetype"] string(10) "image/jpeg" ["width"] int(500) ["height"] int(331) ["landscape"] bool(true) ["ratio"] float(1.5105740181269) ["bits"] int(8) ["channels"] int(3) ["colspace"] string(9) "DeviceRGB" -------------------------------------------------------------------

      * getPimVariations

      getPimVariations()
      return: array of Pageimages Collect all pimVariations of this Pageimage as a Pageimages array of Pageimage objects. All variations created by the core ImageSizer are not included in the collection.
      -------------------------------------------------------------------

      * removePimVariations

      removePimVariations()
      return: pim - (class handle) Removes all image variations that was created using the PIM, all variations that are created by the core ImageSizer are left untouched!
      -------------------------------------------------------------------
      * width

      width($dst_width, $sharpen_mode=null)
      param: $dst_width - (integer) param: $auto_sharpen - (boolean) default is true was deleted with version 0.0.8, - sorry for breaking compatibility param: $sharpen_mode - (string) possible: 'none' | 'soft' | 'medium' | 'strong', default is 'soft' return: pim - (class handle) Is a call to resize where you prioritize the width, like with pageimage. Additionally, after resizing, an automatic sharpening can be done with one of the three modes.
      -------------------------------------------------------------------

      * height

      height($dst_height, $sharpen_mode=null)
      param: $dst_height - (integer) param: $auto_sharpen - (boolean) default is true was deleted with version 0.0.8, - sorry for breaking compatibility param: $sharpen_mode - (string) possible: 'none' | 'soft' | 'medium' | 'strong', default is 'soft' return: pim - (class handle) Is a call to resize where you prioritize the height, like with pageimage. Additionally, after resizing, an automatic sharpening can be done with one of the three modes.
      -------------------------------------------------------------------

      * resize

      resize($dst_width=0, $dst_height=0, $sharpen_mode=null)
      param: $dst_width - (integer) default is 0 param: $dst_height - (integer) default is 0 param: $auto_sharpen - (boolean) default is true was deleted with version 0.0.8, - sorry for breaking compatibility param: $sharpen_mode - (string) possible: 'none' | 'soft' | 'medium' | 'strong', default is 'soft' return: pim - (class handle) Is a call to resize where you have to set width and / or height, like with pageimage size(). Additionally, after resizing, an automatic sharpening can be done with one of the three modes.
      -------------------------------------------------------------------

      * stepResize

      stepResize($dst_width=0, $dst_height=0)
      param: $dst_width - (integer) default is 0 param: $dst_height - (integer) default is 0 return: pim - (class handle) this performs a resizing but with multiple little steps, each step followed by a soft sharpening. That way you can get better result of sharpened images.
      -------------------------------------------------------------------

      * sharpen

      sharpen($mode='soft')
      param: $mode - (string) possible values 'none' | 'soft'| 'medium'| 'strong' return: pim - (class handle) Applys sharpening to the current memory image. You can call it with one of the three predefined pattern, or you can pass an array with your own pattern.
      -------------------------------------------------------------------

      * unsharpMask

      unsharpMask($amount, $radius, $threshold)
      param: $amount - (integer) 0 - 500, default is 100 param: $radius - (float) 0.1 - 50, default is 0.5 param: $threshold - (integer) 0 - 255, default is 3 return: pim - (class handle) Applys sharpening to the current memory image like the equal named filter in photoshop.
      Credit for the used unsharp mask algorithm goes to Torstein Hønsi who has created the function back in 2003.
      -------------------------------------------------------------------

      * smooth

      smooth($level=127)
      param: $level - (integer) 1 - 255, default is 127 return: pim - (class handle) Smooth is the opposite of sharpen. You can define how strong it should be applied, 1 is low and 255 is strong.
      -------------------------------------------------------------------

      * blur

      blur()
      return: pim - (class handle) Blur is like smooth, but cannot called with a value. It seems to be similar like a result of smooth with a value greater than 200.
      -------------------------------------------------------------------

      * crop

      crop($pos_x, $pos_y, $width, $height)
      param: $pos_x - (integer) start position left param: $pos_y - (integer) start position top param: $width - (integer) horizontal length of desired image part param: $height - (integer) vertical length of desired image part return: pim - (class handle) This method cut out a part of the memory image.
      -------------------------------------------------------------------

      * canvas

      canvas($width, $height, $bgcolor, $position, $padding)
      param: $width = mixed, associative array with options or integer, - mandatory! param: $height = integer, - mandatory if $width is integer! param: $bgcolor = array with rgb or rgba, - default is array(255, 255, 255, 0) param: $position = one out of north, northwest, center, etc, - default is center param: $padding = integer as percent of canvas length, - default is 0 return: pim - (class handle) This method creates a canvas according to the given width and height and position the memory image onto it.
      You can pass an associative options array as the first and only param. With it you have to set width and height and optionally any other valid param. Or you have to set at least width and height as integers.
      Hint: If you want use transparency with rgba and your sourceImage isn't of type PNG, you have to define 'png' as outputFormat with your initially options array or, for example, like this: $image->pimLoad('prefix')->setOutputFormat('png')->canvas(300, 300, array(210,233,238,0.5), 'c', 5)->pimSave()
      -------------------------------------------------------------------

      * flip

      flip($vertical=false)
      param: $vertical - (boolean) default is false return: pim - (class handle) This flips the image horizontal by default. (mirroring)
      If the boolean param is set to true, it flips the image vertical instead.
      -------------------------------------------------------------------

      * rotate

      rotate($degree, $backgroundColor=127)
      param: $degree - (integer) valid is -360 0 360 param: $backgroundColor - (integer) valid is 0 - 255, default is 127 return: pim - (class handle) This rotates the image. Positive values for degree rotates clockwise, negative values counter clockwise. If you use other values than 90, 180, 270, the additional space gets filled with the defined background color.
      -------------------------------------------------------------------

      * brightness

      brightness($level)
      param: $level - (integer) -255 0 255 return: pim - (class handle) You can adjust brightness by defining a value between -255 and +255. Zero lets it unchanged, negative values results in darker images and positive values in lighter images.
      -------------------------------------------------------------------

      * contrast

      contrast($level)
      param: $level - (integer) -255 0 255 return: pim - (class handle) You can adjust contrast by defining a value between -255 and +255. Zero lets it unchanged, negative values results in lesser contrast and positive values in higher contrast.
      -------------------------------------------------------------------

      * grayscale

      grayscale()
      return: pim - (class handle) Turns an image into grayscale. Remove all colors.
      -------------------------------------------------------------------

      * sepia

      sepia()
      return: pim - (class handle) Turns the memory image into a colorized grayscale image with a predefined rgb-color that is known as "sepia".
      -------------------------------------------------------------------

      * colorize

      colorize($anyColor)
      param: $anyColor - (array) like css rgb or css rgba - but with values for rgb -255 - +255,  - value for alpha is float 0 - 1, 0 = transparent  1 = opaque return: pim - (class handle) Here you can adjust each of the RGB colors and optionally the alpha channel. Zero lets the channel unchanged whereas negative values results in lesser / darker parts of that channel and higher values in stronger saturisation of that channel.
      -------------------------------------------------------------------

      * negate

      negate()
      return: pim - (class handle) Turns an image into a "negative".
      -------------------------------------------------------------------

      * pixelate

      pixelate($blockSize=3)
      param: $blockSize - (integer) 1 - ??, default is 3 return: pim - (class handle) This apply the well known PixelLook to the memory image. It is stronger with higher values for blockSize.
      -------------------------------------------------------------------

      * emboss

      emboss()
      return: pim - (class handle) This apply the emboss effect to the memory image.
      -------------------------------------------------------------------

      * edgedetect

      edgedetect()
      return: pim - (class handle) This apply the edge-detect effect to the memory image.
      -------------------------------------------------------------------

      * getMemoryImage

      getMemoryImage()
      return: memoryimage - (GD-Resource) If you want apply something that isn't available with that class, you simply can check out the current memory image and apply your image - voodoo - stuff
      -------------------------------------------------------------------

      * setMemoryImage

      setMemoryImage($memoryImage)
      param: $memoryImage - (GD-Resource) return: pim - (class handle) If you are ready with your own image stuff, you can check in the memory image for further use with the class.
      -------------------------------------------------------------------

      * watermarkLogo

      watermarkLogo($pngAlphaImage, $position='center', $padding=2)
      param: $pngAlphaImage - mixed [systemfilepath or PageImageObject] to/from a PNG with transparency param: $position - (string) is one out of: N, E, S, W, C, NE, SE, SW, NW,
      - or: north, east, south, west, center, northeast, southeast, southwest, northwest
      default is 'center' param: $padding - (integer) 0 - 25, default is 5, padding to the borders in percent of the images length! return: pim - (class handle) You can pass a transparent image with its filename or as a PageImage to the method. If the watermark is bigger than the destination-image, it gets shrinked to fit into the targetimage. If it is a small watermark image you can define the position of it:
      NW - N - NE | | | W - C - E | | | SW - S - SE  
      The easiest and best way I have discovered to apply a big transparency watermark to an image is as follows:
      create a square transparent png image of e.g. 2000 x 2000 px, place your mark into the center with enough (percent) of space to the borders. You can see an example here! The $pngAlphaImage get centered and shrinked to fit into the memory image. No hassle with what width and / or height should I use?, how many space for the borders?, etc.
      -------------------------------------------------------------------

      * watermarkLogoTiled

      watermarkLogoTiled($pngAlphaImage)
      param: $pngAlphaImage - mixed [systemfilepath or PageImageObject] to/from a PNG with transparency return: pim - (class handle) Here you have to pass a tile png with transparency (e.g. something between 150-300 px?) to your bigger images. It got repeated all over the memory image starting at the top left corner.
      -------------------------------------------------------------------

      * watermarkText

      watermarkText($text, $size=10, $position='center', $padding=2, $opacity=50, $trueTypeFont=null)
      param: $text - (string) the text that you want to display on the image param: $size - (integer) 1 - 100, unit = points, good value seems to be around 10 to 15 param: $position - (string) is one out of: N, E, S, W, C, NE, SE, SW, NW,
      - or: north, east, south, west, center, northeast, southeast, southwest, northwest
      default is 'center' param: $padding - (integer) 0 - 25, default is 2, padding to the borders in percent of the images length! param: $opacity- (integer) 1 - 100, default is 50 param: $trueTypeFont - (string) systemfilepath to a TrueTypeFont, default is freesansbold.ttf (is GPL & comes with the module) return: pim - (class handle) Here you can display (dynamic) text with transparency over the memory image. You have to define your text, and optionally size, position, padding, opacity for it. And if you don't like the default font, freesansbold, you have to point to a TrueTypeFont-File of your choice.
      Please have a look to example output: http://processwire.com/talk/topic/4264-release-page-image-manipulator/page-2#entry41989
      -------------------------------------------------------------------





      PageImage Manipulator - Example Output


    • By d'Hinnisdaël
      Format Datetime fields as Carbon instances.
      You can find the latest release and the complete readme on Github.
      Installation
      composer require daun/datetime-carbon-format Usage
      All Datetime fields will now be formatted as Carbon instances instead of strings. Some examples:
      // $page->date is a Datetime field // Output format: j/n/Y echo $page->date; // 20/10/2020 echo $page->date->add('7 days'); // 27/10/2020 echo $page->date->format('l, F j'); // Monday, October 20 echo $page->date->year; // 2020 echo $page->date->diffForHumans(); // 28 minutes ago Frontend only
      The ProcessWire admin seems to expect datetime fields to be strings. This module will only return Carbon instances on frontend page views.
      Date output format
      When casting a Carbon instance to a string (usually when outputting the field in a template), the field's date output format will be respected.
      Links
      GitHub • Readme • Carbon docs
       
       
      PS. I remember reading about a Carbon module in a recent newsletter, but couldn't find it anywhere. Was that you, @bernhard?
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Warning: This module requires ProcessWire 3.0.167 which is above the current stable master release at the moment.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Attention, please note!
      Nested repeaters cannot be supported technically. Therefore a check is made to prevent this. However, a nested repeater can only be detected if the field name ends for example with "_repeater1234". For example, if your MatrixRepeater field is named like this: "content_repeater" or "content_repeater123", this field is identified as nested and the module does not load. In version 2.0.1 the identification has been changed so that a field ending with the name repeater is only detected as nested if at least a two-digit number sequence follows. But to avoid this problem completely, make sure that your repeater matrix field does NOT end with the name "repeater".
      Changelog
       
      2.0.1
      Bug fix: Thanks to @ngrmm I could discover a bug which causes that the module cannot be loaded if the MatrixRepeater field ends with the name "repeater". The code was adjusted and information about the problem was provided 2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.1)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
×
×
  • Create New...