wbmnfktr

Wow... that's what I had all the time using Windows. The moment you clone a repo and it tries to index the files, it went crazy and didn't stop for hours. Disabling all indexing and search features helped a lot but still more fan noise on Windows than nowadays on Linux - at least for me. The last time I heard a fan was when moving the old Thinkpad X260 from Ubuntu 23.10 to 24.04. And passive cooling... there are some MS Surface Laptops out there that don't have a fan at all. My Surface (from 2018 or so) is one of those. Sure it's an i5 but that machine did a great job on Windows and even Linux. Really miss it. Count me in on this. I'm tempted to get a Framework laptop right now but with those new processors... I sure get one. (And yes, it's DHH's fault.)

Awesome. Ok. He is convincing quite a few right now. It's quite interesting to follow the situation. Didn't know about Pinta. Might give it a try. Another thing in regards to Gimp and Inkscape (an Illustrator alternative) - great tutorials here: https://www.youtube.com/c/LogosByNick He offers courses to master both for very little money. Might help to keep things moving in that space.

Here! Moved away from Mac over a decade ago and went with Windows for quite some time. Then about 6+ years ago I made the switch to full-time Linux. Never looked back. Enjoyed distro-hopping between Ubuntu, Fedora, Manjaro, Debian, Arch, Zorin and finally settled with Ubuntu because of the broad support even for tools like ScreamingFrog (.deb and .rpm). Moved away from Gnome to i3wm to have a super minimal environment. Everything works just by pressing keys - from moving windows around workspaces, opening or starting apps, to window tiling. I am a happy camper now. ? As you are on Ubuntu as well I suggest looking at deb-get - a little helper to install most common apps without hunting down the .deb files: https://github.com/wimpysworld/deb-get/blob/main/01-main/README.md You may have seen over on X/Twitter the journey of DHH He released his very own setup as a script to make tons of changes, installing software, fonts, and all kinds of stuff. See here: https://x.com/dhh/status/1798466733222838758 His journey explained here: https://x.com/dhh/status/1799185008378171885

Maybe your hosting company needs that whiskey to unlock it faster. Solution found. That's perfect.

I found these settings for ZOHO - and they use a different server: Outgoing Server Name: smtp.zoho.eu Port: 465 Security Type: SSL Require Authentication: Yes. https://www.zoho.com/mail/help/zoho-smtp.html

Your post should be a blog post here on the ProcessWire blog, be listed as a prime example why PW and its API is so awesome and should be linked on the frontpage under "(Why) Web developers love ProcessWire". ? @FireWire

Didn't even know this existed. Good find.

I'm just in the middle of rebuilding a website and started to move around some fields and made use of more modern solutions like Combo fields. Doing so I created a field called meta. A few moments later it felt wrong and I remembered that we have $page->meta() now. Shouldn't there have been an error while creating that field?

The question should have been more something like: Why does someone might want to use a (static) JS frontend? But... yes, you are right. Those frontends, especially static, are great and help with lots of things. Not only 404s, crawlers and such but with security as well. If it wasn't for the hosting company to take measures, a client wouldn't have noticed someone tried to compromise his website. Being cheap on servers (same for me) is something you can only do with ProcessWire or a static version of site. So a big plus here for ProcessWire. You can really squeeze a cheap hosting with ProcessWire and ProCache. Wouldn't want to try that with Wordpress or so. GraphQL, Rest, JSON... is most of the time the way to go. Yet it seems people start to dislike GraphQL for some reason. Maybe because it's too much of a hassle for most. Don't know. And I am not sure how IntertiaJS does it in Laravel but maybe I will find out one day. I actually just did exactly that and moved smaller projects away from ProcessWire in the frontend. PW sits on cms.domain.tld and the frontend fetches JSON to generate everything. It's totally static and can be triggered via webhook to deploy a new version. It's more just for fun now. One thing for sure (for me): building the first proof of concept or prototype with AstroJS reduces my initial development big times. It's off because of that. Because Strapi doesn't do anything in the frontend and everything in the video was a JS framework.

And all I can think is: "Wow... that's a super nice and clean backend he build there!" But yes. It can be confusing to see how simple (as in clean and streamlined) things can be.

You may remember my question regarding a "Headless ProcessWire" quite a few months back. The end result with either GraphQL, JSON, RestApi, and any other solution based on ProcessWire looked almost exactly like that when I wanted to use that data in either 11ty or Astro - which I used a lot back then. So... yes, in plain ProcessWire this is a super simple no-brainer with 1 to 3 lines of minimal PHP. Yet, when using anything else as the frontend, aka JS Framework (React, Svelte, Astro, 11ty) we still would have to go that route in some way or another. Even with Hygraph, Payload, Directus, and whatever Headless CMS out there - it would look like that. The part you attribute to Strapi here is not really about Strapi. It's more about the used frontend. So... a bit off. Probably more interesting and more comparable would be Laravel with Inertia JS (on the JS side of things) or Laravel with Livewire (on the side or similar to PW of things, from the creator of AlpineJS). For that matter I really enjoy those Laravel-related videos from Aaron Francis (the PHP is cool again - guy) and the 30 days to learn Laravel Workshop. Besides that we might want to ask better questions like: Why use a (static) JS Frontend? How to make PW more compatible with JS Frontend Frameworks?

Check what template your posts use, open the matching .php file and look for the comments field. After that comment it out or delete it and the issue should be gone.

+1 ??

Has someone a Pro account over on builtwith.com? https://trends.builtwith.com/cms/ProcessWire

What about: https://github.com/NikolayRys/Likely

And we all should put that link into our signature. Otherwise we would probably forget it again. ?

Quoting myself: Customized templates and fields Each and every content type only has the fields it really needs. Books, companies, recipes - it doesn't matter what kind of data my clients or I have to deal with. The templates and fields will reflect that. Therefore clients don't even have to learn anything in regards to creating or editing data. Super easy. It's typesafe (by my definition) We can discuss the meaning of 'typesafe' here but... I think ProcessWire is somewhat typesafe because I define each field, template, relationship, and almost everything else. I know where to expect what kind of data and know what data is allowed in which field. No guessing, no errors. (Sure this depends on your setup and your will to invest some time.) Works perfectly fine for non-developers I won't call myself a coder or programmer - I just tinker around with code and have fun. When I started using ProcessWire, getting around was super easy, and learning the fundamentals took only a day or two. From there on, it was easy-going. It's impressive what you can achieve with only some if/foreach/echo in PHP/ProcessWire. I said it a few years back and still stand behind it: ProcessWire seems to be the easiest way to learn and work with PHP. Low maintenance There are ProcessWire projects of mine that haven't been updated in the last 5+ years and still work without any PHP or security issues. The moment a project is finished and works without flaws it will do so for a very long time. There is no real need to update a project. Small footprint, high performance A ProcessWire website doesn't need that much of a big hosting package. The moment you start using Core cache functionalities or even ProCache most websites are fine and ready for an average amount of traffic. Maybe not ready for a slashdot/reddit/ProductHunt-peak but that's a totally different story. I can get so much out of ProcessWire compared to WordPress (and others I used/tested in the past). ZIP downloads and no real need for a package manager What I really love and enjoy is that you can get everything as a ZIP file, unpack those, move them around and do whatever you want or need with them. Not needing NPM or composer to get started - like in the good old days - is just perfect. In the last 1-2 years I did a lot with NPM due to 11ty and Astro, yet an old-school ZIP file has its very own charme. For comparison: Installing CraftCMS feels good and really nice, yet I absolute don't know what's happening, what is needed, and so on. It's like a blackbox. It works but I don't know why. I hate that. see thread here:

As SQLite is mentioned here more than once in a while I thought this could be interesting for one or another.

Problem solved so it doesn't really matter anymore. ?

Wohoo! Awesome. // my ready.php if ($page->template != 'admin') { $wire->addHookAfter('Pageimage::url', function ($event) { static $n = 0; // slightly different here if (++$n === 1) { $event->return = $event->object->webp()->url(); } $n--; }); }

Create (not copy/clone the existing one) a new image field with the exact same settings and try if it still doesn't work. I guess you already tried different images? Just in case. ? Does the file really exist in the file system? Correct mime-type? Just check if there is some weird setting in the body field. Maybe even create a new body field. Are there any textformatters applied? Is there anything in the logs? As you see... just wild guesses but that's how would look for issues and you already tested quite a lot.

That sounds to me like a totally different project now. This way you could offer a solution that's managed. In other words: the frontend lists all offers/ads, categories, filters, and everything you need. When it comes to posting ads they could all be collected by a more or less simple form (FormBuilder would work perfectly well here). In case of shelters that have a whole lot of animals they want to list, they could send a CSV (or Excel that needs to be converted) and you or someone imports it via ImportPagesCSV. Even references to that animal shelter profile could be set and other things of course. The inital cost would way lower, the project could grow and it would only be necessary to build what is really needed, and you could offer to manage that site for a monthly fee. Start with a minmal solution and go from there. We did this with a restaurant directory completely managed, no registration needed. But that's just my thought before my first coffee. ?

Oh no no no... it would be ProcessWire front, back, and center. But I wouldn't use anything like Svelte or whatever on the frontend or even go headless in this case. In addition to that, when I spoke about custom interfaces and management tools I meant things like we can see in the Invoice Site Profile.

My biggest issue with this - in terms of coding and stitching everything together - would be registration, user management, page creation through registered users, and keeping everything as easy and clean as possible for the users. They need custom interfaces and can't use the ProcessWire backend. They probably wouldn't get it. Second issue would probably be an additional management tool for all ads, users, and tasks that occur on a day to day base for such websites aka things user need help with. Maybe a bit of GDPR to allow users to totally delete their account and all their ads while keeping everything that might need to be archived by law. You didn't mention any form of payment process so things should be quite straightforward from here. For the frontend I'd go with clean PHP, clever site structure, and logic. Search, sort, filter with any kind of JS is nice, but not necessary. Later on I might add some nice and shiny AJAX-powered search bars, and things like that. BUT... all of the above isn't the problem with such projects. What you really need is a clear and precise description of what the client thinks he wants, written agreements about who delivers which part and who is responsible for what. Was asked to create a job board once. Client said: "Super easy. User creates an account. Adds job postings. List them on the website. Remove them after 30 days. Nothing special!" What he really wanted was a rebuild of monster or stepstone of one of those big job portals. So... yeah. How long would it take? At least 30k EUR.

In case you have time this weekend: Saturday: enjoy a day reading the docs and tutorials Sunday: enjoy a day of tinkering with the installation, a site profile, maybe first steps In addition to that I recommend this 10 year old video: ProcessWire looks way different nowadays but the steps are the same. And you can see how easy it is (or can be) to get started.