Jump to content
dadish

GraphQL for ProcessWire

Recommended Posts

So I made a mistake by not taking into account the ProcessWire's module naming convention. I totally forgot the fact that if module name starts with Fieldtype it becomes a fieldtype and PW will treat it like any other fieldtype. Like it would try to let you add a new field with that fieldtype. Which we do not want for our GraphQL extension modules. I already faced bugs because of this on admin side.

So naming rule for GraphQL extension modules will be changed from suffixing the name with GraphQL to prefixing the name with GraphQL. So it is GraphQLFieldtypeMapMarker instead of FieldtypeMapMarkerGraphQL. Other than that, everything is the same as before. I'll also update the previous post to reflect this change. Sorry if this causes inconvenience to anyone.

The updated version of ProcessGraphQL that works with new rules is available for use in latest release.

  • Like 7

Share this post


Link to post
Share on other sites

Wow o_O @dadish I am humbled by your excellent work here. I stumbled on this thread researching PWAs and then was transfixed for the full 37 minutes of your excellent video intro. Thank you very much indeed for all of this, I am yet again thankful for the ProcessWire community's generous and excellent work.

I've had Vue.js noted down as "something I want to use", along with using ProcessWire as/via an API, and most recently, PWAs. I am hoping, if I've not misunderstood, now I may be able to use all these together for a project.

Brilliant! \o/

  • Like 7

Share this post


Link to post
Share on other sites

I'm very happy you like it @alan. You definitely can use this for any single page application. That's exactly why I built this module for. Please don't hesitate to share the issues that might come up when using this module. I would love hear some feedback and maybe fix bugs if there are any.

  • Like 3
  • Thanks 1

Share this post


Link to post
Share on other sites
5 hours ago, dadish said:

I'm very happy you like it @alan. You definitely can use this for any single page application. That's exactly why I built this module for. Please don't hesitate to share the issues that might come up when using this module. I would love hear some feedback and maybe fix bugs if there are any.

THANK you @dadish ^_^ — this; SPA + PW as an API + GraphQL for PW, for me is a milestone exciting proposition. I hope I make it the biggest thing to happen to my PW world since I read the word "ProcessWire" on the bottom generous Marty Walker's web site and first visited processwire.com.

First steps for me are reading up on PWAs and finally trying to finish a Wes Bos course on ES6, then I'm off to add in PW as an API & GraphQL. Exciting!

  • Like 3

Share this post


Link to post
Share on other sites

First of all, I love the module thus far. Unfortunately (for me), When I go to Setup->GraphQL, it pops up with "Loading...", but never actually loads anything . I am currently using php 5.6.30. Any idea what might be causing this? I dont currently have any errors in my console either. 

Screen Shot 2018-03-28 at 3.48.57 PM.png

Share this post


Link to post
Share on other sites
27 minutes ago, louisstephens said:

First of all, I love the module thus far. Unfortunately (for me), When I go to Setup->GraphQL, it pops up with "Loading...", but never actually loads anything . I am currently using php 5.6.30. Any idea what might be causing this? I dont currently have any errors in my console either. 

Screen Shot 2018-03-28 at 3.48.57 PM.png

This one is weird. I just installed the module on Classic profile and Skyscrapers profile with latest ProccessWire. Works fine for me.

The "Loading..." is a placeholder till JavaScript kicks in. So this means the GraphiQL js assets are not loading or firing. Could you please try to see if GraphiQL works out of ProcessWire admin. You can either do that manually, using API that exposes GraphiQL in your template file. Or use GraphQL Pages generator. It's in the modules setting page. Looks like this.
5abbfa69e4934_ScreenShot2018-03-29at2_23_50AM.thumb.png.b59965ccf4237c8e0634d51515e46a63.png

Just press it and go to `/graphiql/` on your website and show us what you got there.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @dadish! I did as you suggested and still got "Loading...". However, I went through and looked at modules (pretty clean install with not many modules) and disabled TraceyDebugger and now it seems to be working perfectly. I should have done this prior, so my apologies.

Share this post


Link to post
Share on other sites

@dadish I guess I have one question in regards to actually obtain an output in templates (sorry I am really new to ajax in general). I currently have

$result = $modules->get('ProcessGraphQL')->executeGraphQL($query, $variables);

in my header of a file, but need to have an "operation" included. I was testing it out with just trying to get the title and body of the current page. I geuss I am a little unsure of how to get started with this.

Share this post


Link to post
Share on other sites

Not really sure if this is the best place to post this (or if it belongs in the thread for the module itself, but if it needs to be moved please do so. I successfully got graphql set up and love how easy it makes it to query etc. 

In my endpoint, I have:

echo $modules->get('ProcessGraphQL')->executeGraphQL();

And on another page, I was testing with:

$.ajax({
		type: "POST",
		url: 'localhost/pw/graphql/',          
		data: "{ modals(s: \"title=Test-Page\") { list { id title body } } }",      
		
		success: function(data) {
			console.log(data);
		} 
	});

However, I seem to be getting an error message returned with: "Must provide an operation.". I do apologize if I have just missed something basic (very new to ajax and how it all functions), but is there something missing from my initial request?

Share this post


Link to post
Share on other sites

I get the same "loading" screen.

My browser console shows 

Failed to load resource: the server responded with a status of 404 ()

It looks for a file that doesn't exist: site/templates/admin/admin.js

edit: OK, I also disabled Tracy, and everything works fine.

 

Edited by dragan

Share this post


Link to post
Share on other sites
On 4/5/2018 at 7:47 PM, louisstephens said:

Not really sure if this is the best place to post this (or if it belongs in the thread for the module itself, but if it needs to be moved please do so. I successfully got graphql set up and love how easy it makes it to query etc. 

In my endpoint, I have:


echo $modules->get('ProcessGraphQL')->executeGraphQL();

And on another page, I was testing with:


$.ajax({
		type: "POST",
		url: 'localhost/pw/graphql/',          
		data: "{ modals(s: \"title=Test-Page\") { list { id title body } } }",      
		
		success: function(data) {
			console.log(data);
		} 
	});

However, I seem to be getting an error message returned with: "Must provide an operation.". I do apologize if I have just missed something basic (very new to ajax and how it all functions), but is there something missing from my initial request?

@louisstephens Your query should be assigned to query variable. Try to change above code like this

$.ajax({
  type: "POST",
  url: 'localhost/pw/graphql/',          
  data: {
    query: "{ modals(s: \"title=Test-Page\") { list { id title body } } }" // <-- change here
  },  
  success: function(data) {
    console.log(data);
  } 
});

 

  • Like 1

Share this post


Link to post
Share on other sites
On 4/2/2018 at 10:09 PM, chumneypwire said:

@dadish I guess I have one question in regards to actually obtain an output in templates (sorry I am really new to ajax in general). I currently have


$result = $modules->get('ProcessGraphQL')->executeGraphQL($query, $variables);

in my header of a file, but need to have an "operation" included. I was testing it out with just trying to get the title and body of the current page. I geuss I am a little unsure of how to get started with this.

You shouldn't use it to obtain output in your template file. ProcessWire already comes with the best API to access your content. The purpose of the GraphQL module is to let you access content via AJAX, using JavaScript from client side.

  • Like 1

Share this post


Link to post
Share on other sites

@dadish

While installing the module I get 

require_once(): Failed opening required ' ... modules/ProcessGraphQL/vendor/autoload.php'

There is no 'vendor' folder on the master branch, but it exists on dev branch. Am I missing something? 

Share this post


Link to post
Share on other sites

Thank @dadish for this great module. I liked this post long time ago. I just have a chance to get my hand dirty on it. It turns Processwire to a powerful headless CMS with no pain! I am going to use this in my next project with Vue.js or Nuxt.js. 😋

One noob question. Could this module query and mutate session data? I have modules that read/write user, including the unsigned guests, session data. I have no idea how to make it happen using only a GraphQL end point.

Share this post


Link to post
Share on other sites
8 hours ago, Zeka said:

@dadish

While installing the module I get 


require_once(): Failed opening required ' ... modules/ProcessGraphQL/vendor/autoload.php'

There is no 'vendor' folder on the master branch, but it exists on dev branch. Am I missing something? 

Hi @Zeka. You should not install the main repository of the module. The main repository of the module is intended only for development of the module. You can install the module in two ways:

  • By module classname. Go to Modules -> Site -> Add New in your PW admin and write `ProcessGraphQL` in Module Class Name field and press Download and Install button.
  • By a zip file. You need to download the module for installation from the releases page of the module. There you can download a .zip file and place it's contents to the site/modules/ directory of the module.
  • Like 2

Share this post


Link to post
Share on other sites
21 hours ago, Karl_T said:

Thank @dadish for this great module. I liked this post long time ago. I just have a chance to get my hand dirty on it. It turns Processwire to a powerful headless CMS with no pain! I am going to use this in my next project with Vue.js or Nuxt.js. 😋

One noob question. Could this module query and mutate session data? I have modules that read/write user, including the unsigned guests, session data. I have no idea how to make it happen using only a GraphQL end point.

Hi @Karl_T.

The module has no ability to modify the session data. It only can modify PW pages. AFAIK session data is not stored as pages.

What you can do is add a custom GraphQL mutation field for modifying your session. But that would require you to learn GraphQL and the PHP library that we use. Here is how it might look like

<?php namespace ProcessWire;

use Youshido\GraphQL\Type\Scalar\BooleanType;
use Youshido\GraphQL\Type\Scalar\StringType;
use Youshido\GraphQL\Type\Scalar\IntType;
use Youshido\GraphQL\Execution\ResolveInfo;

$processGraphQL = $modules->get('ProcessGraphQL');

wire()->addHookAfter('ProcessGraphQL::getMutation', function ($event) {
    $mutation = $event->return;
    $mutation->addField('modifySessionData', [
        'type' => new BooleanType(),
        'args' => [
          'foo' => new StringType(),
          'bar' => new IntType(),
        ],
        'resolve' => function ($value, array $args, ResolveInfo $info) {
          $success = false;
		  // modify session data here...
          if ($something) {
            $success = true;
          }
          return $success;
        }
    ]);
});

echo $processGraphQL->executeGraphQL();

And then the query for this could look like this

mutation {
  modifySessionData("foo": "boblibob", "bar": 12234)
}

Haven't tried it. So there might be something I'm missing. But I hope this gives you the idea of how you can achieve what you want.

  • Like 6
  • Thanks 1

Share this post


Link to post
Share on other sites

Slightly OT but worth a read:

Open Source GraphQL Engine Launched

https://www.i-programmer.info/news/197-data-mining/11962-graphql-engine-launched.html

quotes:

"The GraphQL community can harness our lightweight GraphQL-as-a-Service engine and turbocharge any of their new or existing Postgres applications."
"While this release focuses on Postgres, the plan is to add support for other databases in the future."

Share this post


Link to post
Share on other sites

Love this module, but I'm concerned about the speed. In my tests, a native template returning the same records and data as the GraphQL endpoint:

Returning 20 pages and some details about  page references:

Native Template: 0.4s
GraphQL Endpoint: 3.2s

Is this performance something that could still be improved? 

Share this post


Link to post
Share on other sites

How do you get the name of Pages from a Page Reference field? I have one called 'colors' and it only lets me get the following total, limit, start - no means to get colors -> name or title?


 

{
  product_single (s: "parent=X") {
    list {
      title
      product_code
			colors {
			  getTotal
			  getLimit
			  getStart
			} 
    }
  }
}

 

Share this post


Link to post
Share on other sites
On 9/17/2018 at 8:37 PM, patricktsg said:

How do you get the name of Pages from a Page Reference field? I have one called 'colors' and it only lets me get the following total, limit, start - no means to get colors -> name or title

It should be like this

{
  product_single (s: "parent=X") {
    list {
      title
      product_code
        colors {
          getTotal
          getLimit
          getStart
          list { // list of colors
            name // name for each color
          }
        }
      }
    }
  }
}

 

  • Like 1

Share this post


Link to post
Share on other sites
On 8/29/2018 at 3:11 AM, bcartier said:

Love this module, but I'm concerned about the speed. In my tests, a native template returning the same records and data as the GraphQL endpoint:

Returning 20 pages and some details about  page references:

Native Template: 0.4s
GraphQL Endpoint: 3.2s

Is this performance something that could still be improved? 

Unfortunately I haven't had much time in optimization for this module. I'm very busy so can't promise any timelines when this will happen. The only thing you can do now is to keep your graphql schema as small as possible by unchecking all the unwanted fields and templates in the module config page.

There is supposed to be a way to cache the schema (https://github.com/youshido-php/GraphQL/pull/37) I was planning to look into it. But never had a time for it and thus is not implemented in this module yet.

  • Like 1

Share this post


Link to post
Share on other sites
22 hours ago, dadish said:

It should be like this


{
  product_single (s: "parent=X") {
    list {
      title
      product_code
        colors {
          getTotal
          getLimit
          getStart
          list { // list of colors
            name // name for each color
          }
        }
      }
    }
  }
}

 

Thanks for getting back to me - tried that code but I just get an empty array for the list

 

{
  "data": {
    "product_single": {
      "list": [
        {
          "title": "Widget",
          "product_code": "12345",
          "colour": {
            "getTotal": 1,
            "getLimit": 0,
            "getStart": 0,
            "list": []
          }
        }
      ]
    }
  }
}

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MoritzLost
      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.
      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) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
×
×
  • Create New...