StanLindsey

Perfect - solved. I didn't think of using the sub-selectors in the sort param for some reason.

I'm working on an e-commerce shop. Currently, a categories default sorting is by descending price. The client doesn't have images for all products, wants the category sorted by products with images by default. Easy: sort=-image This sorts by the filename, essentially alphabetically. I'd like to sort by those with images, with a secondary sort of price descending. sort=-image, sort=price This does not work, because the image sort is sorting alphabetically, not by the existence of the field. So you end up with this: name | image | price product1 | product1.jpg | £12.34 product2 | product2.jpg | £43.43 product3 | product3.jpg | £12.20 product4 | product4.jpg | £76.20 product5 | product5.jpg | £12.50 product6 | null | £18.50 product7 | null | £16.21 product8 | null | £13.10 Notice that images prices are essentially ordered randomly, those with null image are ordered descending. So I need to have the selector sort by the existence of the image field, not by the content of the image field. I need to do this as part of the selector because some of these categories have 2000+ products and I cannot do it in-memory. Thoughts?

This thread is really exciting. I'm looking forward to offering webp easily. =D Thanks @horst for your hard work.

So we're over half way through the year. How are we getting on with this @ryan? I don't see much of a discussion around it? I think this is a really important first step to making ProcessWire part of the larger web development community and really increasing its popularity. (And sales of pro modules!).

Yeah, that doesn't come through on the $input variable, so you'd have to grab it yourself. I've pushed a PR to include it in the $input variable as it makes sense for ProcessWire to support that out of the box. @ryan

@LostKobrakai, @marcus - what about using "json_decode(file_get_contents("php://input"))". That let's you retrieve the raw data from the request body. http://php.net/manual/en/wrappers.php.php

Anybody got a working config for 3.0.x I can steal?

I'm been using VSCode for the last 9 months or so and I love it. I'm mostly a Javascript developer so it does fit in my alley but I've had success with using it with PW. The little circle/refresh symbol in the bottom left allows you to push your changes to Github/Gitlab etc. Or you can use the command palette to "Git Push". Works a treat with Continuous Interaction. There's also a remote FTP plugin which lets you sync which I've used a couple of times on legacy projects.

I've just started using MarkupRegions and I think they are fantastic. It is basically identical to the Delayed Output strategy but you are able to focus on the markup instead of various php variables. Definitely give it a try before you write it off.

Bit of a bump. Ther Api-Docs are great and it is useful that they are built on the dockblocks but that still really limits how far they can go. A site that allows us to bring the core API-Docs, plus the fantastic blogs, tutorials, guides and forum posts would be perfect. All this information is so spread out at the moment its terrible compared to competing platforms.

There are so many ways to skin a cat in Javascript, especially considering how far Javascript has came in recent years. You really don't need jQuery at all. It is also good to learn the Javascript core as to expand your skill set as well as remove a dependency on your project. Some of the posts here are way out of date and verbose. Native Fetch is much better than XMLHttpRequest, and there are some polyfills online if you need IE11 support. fetch('../my-url/', { method: 'post', body: JSON.stringify({ test: response.test }) }).then(response => { return response.json(); }).then(json => { document.querySelector('#output').innerHTML = json.test; }); Read more here: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API And there are a bunch of good basic examples here: https://github.com/mdn/fetch-examples/tree/master/fetch-json

Yeah sorry - went off topic - but that's why I originally asked - if there was any additional functionality included for setting up templates and fields beyond the default APIs capabilities. The migrations module install idea is genius though. Thanks.

I already do this for most of my builds for fixtures but can't find a way to edit the other "data" of a template - the url info or other advanced data.

Can this module set up some templates, fields and pages?

You could also use Url Segments to pull out the image ID from the URL and then pull that out of your specific gallery page you're holding the images in.