Jump to content

charger

Members
  • Content Count

    96
  • Joined

  • Last visited

Everything posted by charger

  1. Here’s the updated code that works for me: <?php namespace ProcessWire; use GraphQL\Type\Definition\Type; $processGraphQL = $modules->get('ProcessGraphQL'); wire()->addHookAfter('ProcessGraphQL::getQueryFields', function ($event) { $query = $event->return; $query[] = [ 'name' => 'hello', 'type' => Type::string(), 'resolve' => function () { return 'world!'; } ]; $event->return = $query; }); echo $processGraphQL->executeGraphQL(); The hook name changed from getQuery to getQueryFields. Also, the new field is now just pushed to the array instea
  2. I’m having problems getting the getQuery hook to execute. If I copy-paste the code from https://github.com/dadish/ProcessGraphQL#getquery-hook to graphql.php (or graphiql.php and ready.php for that matter) and just try to log something inside the function, the hook is never executed. @dadish is the documentation still up-to-date in this regard? I’m on PW 3.0.165 and module version 1.3.0
  3. Does anyone know how to get the module to return webp images? see https://processwire.com/blog/posts/webp-images-in-pw/
  4. I could track down the problem to Apollo fragments (specifically using the same fragment more than once in the same query). Not sure why this only popped up inside Repeater fields though. Thanks for the support!
  5. Yes, it is still the same response: no values.
  6. @dadish I’m afraid the problem persists. I get the exact same response. I cleared compiled files and browser cache.
  7. The template permissions are set correctly then. The guest role has view permission on the product template. I’m setting the field permissions not in template context, but per field. So they all have the view permission, also in template context. Just double-checked that. What’s weird is that title and body generally work outside a repeater field. It’s only within the repeater field, that they return no values. Any other ideas?
  8. When trying to fetch Repeater fields with module version 1.0.5, I get responses like this one: [ { "title": "", "body": "", "products": { "list": [], "__typename": "ProductPageArray" }, "__typename": "RepeaterProductGroupsPage" }, { "title": "", "body": "", "products": { "list": [], "__typename": "ProductPageArray" }, "__typename": "RepeaterProductGroupsPage" } ] So I get an answer with the expected data structure (and no errors whatsoever), but the values of the fields are always empty. Also the amount of repeater items in the respo
  9. 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.
  10. 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 $cacheS
  11. @schwarzdesign I’m sorry, but I think I wasn’t specific enough. How does your router.js look like? 🙂 As you say the routing is handled by Vue. However, I wonder how Vue knows about the routes that exist. Do you manually add the routes to router.js? Or do you grab existing routes via API and then include them in the Vue router config?
  12. Thanks for the detailed write-up! Would you mind sharing how exactly you sync the PW routes with Vue router?
  13. I can do that, but you don’t have to set up a new environment. You just grab the PW files and put them in a newly created folder in your webserver’s root.
  14. I was able to solve the problem meanwhile. It was related to my template file structure. I’m using the delayed output strategy together with some nested wireRenderFile() calls which lead to the problem.
  15. The following line in RockPdf.module.php returns a wrong URL if the PW installation lives in a subdirectory (subdirectory is applied twice): 'httpUrl' => rtrim($this->pages->get(1)->httpUrl, '/') . $url,
  16. Thanks for the hint, wasn’t aware of that. But if the default age for a temp folder is 120 seconds, then that should be plenty of time already. The PDF generation maybe takes around 3 seconds.
  17. This will not work for me as I generate the PDF if there’s a "pdf" GET parameter found (this is e.g. how https://github.com/wanze/Pages2Pdf handles it as well). That’s why I was pursuing another way meanwhile: the wireSendFile() function (https://github.com/processwire/processwire/blob/master/wire/core/Functions.php#L257, https://github.com/wanze/Pages2Pdf/blob/master/Pages2Pdf.module#L312). Here’s the relevant code from my template file: $inputPdf = $input->get('pdf'); $inputPdfSan = $sanitizer->int($inputPdf); if ($inputPdfSan == 1) { $pdf = $modules->get('RockPdf');
  18. Hmm, that didn’t help on my side. I still see the "Unable to remove" errors in the wire-temp-dir logfile, now they’re just referring to the newly set directory. And yes, these are more complex PDFs, but not overly complex (~3MB).
  19. What kind of mime-type errors? And how could that be related to PW only but not the webserver or PHP in general? I also just checked it on the webserver (was on localhost before): same problem there. It’s weird that one option would work while the other two wouldn’t. I can’t make sense of it atm.
  20. @bernhard download() and show() both work outside of PW.
  21. Latest Chrome/Safari/Firefox on macOS 10.14 show all the same problem. The weird thing is it creates the correct amount of pages in the PDF, they’re just blank. Calling `$mpdf->Output($filename, \Mpdf\Output\Destination::DOWNLOAD);` directly results in the same error.
  22. Did anyone else encounter problems with `show()` and `download()`? If I use them, all I get is blank pages resulting in an invalid PDF. The `save()` function works as expected though. I’m running PW 3.0.98 with PHP 7.1.12 and RockPdf 1.0.1
  23. You’re right. Bad example. But it also doesn’t work with width and height values like this: @page { size: 100mm 150mm; }
  24. Did anyone successfully use @page in the stylesheet to e.g. set page size or margins? I don’t see anything happen if I add the following code block to templates/pages2pdf/styles.css: @page { size: A5; margin: 10mm; } I’m using the dev branch of Pages2Pdf (mPDF v6.1).
  25. Found the solution myself: https://github.com/wanze/Pages2Pdf/pull/13
×
×
  • Create New...