StanLindsey

I am getting the following error when i add the InputFieldMediaManager to a template and edit a page of that template. `call to member funnction countr() on null` on line `$this->mediaManagerField->currentFieldCnt = $currentPage->$mediaManagerField->count();` Image: https://gyazo.com/b428b27b498789e7a5d7d91958979c3b - I've reinstalled Media Manager. - I've updated to the latest ProcessWire. (3.0.170)

What does $data->id echo out as?

This module is great, my biggest problem is that you have to edit the field to set default values site wide. I'd like my clients to manage some of that themselves in the settings area i have setup. Can the Default Values of the field be inherited from another page? I guess I could write a hook to edit the field when saving a certain template but wondered if there was an easier solution.

Just jumping in to say that I had to also remove this line in order for www. forwarding to work. I think its supposed to check that is not running locally, so we don't force www. but even in prod my servers are running on localhost/ 127.0.0.1. CC @ryan as there may be a bug in the htaccess. Alternatively it may just need an updated comment to remove that line in prod ¯\_(ツ)_/¯

Also looking to check out latest MariaDB versions.

Maybe things have changed in the last couple years but I can't find anything to do with joining in the official docs. Is this api still available for deciding what fields are auto joined? I'd love to have one query that gives me all the data available without needing to do round robin SQL queries.

Brain fart. There we go, dot accessed subfields 😉 Cheers.

I have the current setup: Repeater Field: `testimonials_repeater` --- Fieldset Page: `testimonial` ------ Text: `author` I can't quite figure out the syntax to display the `FieldSet Page`'s `Author` field as the Repeat Item Label in the repeater. To clarify, I'm talking about this field: Nesting is fun =P. Thanks.

I appreciate the effort here, but remember @kongondo that many of us aren't looking for that full list of features from your original post two years ago. I'd much prefer a performant cut down version and the ability to give you some money for ongoing development than one giant release with all the bells and whistles. MVP > feedback from real customers > new releases. Thanks and i hope everybody is okay considering the current climate =D

Hi, I'm a UK based freelance developer that predominately uses Processwire for our CMS client work. I often have overflow work that needs completing, and am looking for some other Processwire Devs assist in overflow work and projects. Please PM me if you're freelance or a small agency who wants to help out. Thanks in advance.

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