Leaderboard

This week we have some useful upgrades to ProcessWire’s Markup Regions system. These upgrades make Markup Regions even more flexible and intuitive by reducing the dependence on HTML id attributes. Here is a new blog post that covers it in detail— https://processwire.com/blog/posts/pw-3.0.250/

Short answer is yes, for example you could use FormBuilder (Pro module) to collect user details, with a "Stripe Payment" action to collect payment. Then, use a hook on successful payment to create the user account and email the new user with the relevant info

First look at ProcessWire GitHub as I remember it.

Hi there! I love ProcessWire, and whenever I see someone asking for a lightweight CMS, I always recommend it. However, ProcessWire is somehow still extremely underestimated on GitHub, 201 forks, which is really good, but only 990 stars. Let's make an effort together and bring ProcessWire to 1000 stars this weekend! Only 10 stars left. Star on Github: https://github.com/processwire/processwire More context about initial GitHub stars initiative of @adrian: Upd: 10 stars done in five hours.

RockGrid has seen a lot of great improvements over the last few days 😍 The whole codebase has been cleaned up and all javascript files have been split into several files to make maintenance easier. All of that was easily possible thanks to RockDevTools. RockGrid now supports so called "magic attributes" that can pull data from the grid and create UI elements completely automatic. TagsFilter The new tags filter pulls data from one column of your grid and lists all available options as clickable filter tags: All you have to do: <div rg-tagsfilter="field:your_field_name;"></div> --- Flipper I realised that when building grids for my custom bookkeeping software I built the same stuff over and over again, for example buttons to quickly flip over time periods (like the current year, previous year, this month, previous month, etc...). Now that's also built into RockGrid and can be used with a single dom attribute! 😎 All you have to do: <div rg-flipper="field:date_column;range:year;">Y</div> <div rg-flipper="field:date_column;range:month;">M</div> <div rg-flipper="field:date_column;range:day;">D</div> Go and check out RockGrid v1.6.0 🚀🚀

And now... someone is going to be the one to change that 3-digit count to a beautiful 1000. Who is that going to be? I am a little jelous I can't be the one.

And here goes another friend of mine! Only 2 more to go! Seems like we won't need the whole weekend😎

@harmvandeven, @thomas, join us! Got the game! I hope we're not getting banned for spam)

+2 !!! +3 !!!!! Hey, I know those 3 by names... Community! Start to show your power!!!

Nice challenge! Pinging my friends and colleagues. Already +1 )))

Here we go!!! https://github.com/processwire/processwire/pull/322 Fingers crossed 🤞🚀😍

v1.6 released with one tiny change: the overwrite target field setting is now configurable per prompt instead of globally. This allows you to have some prompts that preserve existing content while others overwrite it, giving you more granular control over AI processing behaviour. Needed the functionality for a client, so I thought it would be a nice addition for the module.

Hey @ryan. After some time off, I’m back, and I can already notice a lot of improvements to the admin theme. Great work! I wanted to touch on the topic of the tight control you have over the project. I think I didn’t explain it clearly before, so let me try again. First off, I truly believe in your intentions and your commitment to ProcessWire — that’s never been in question. My perspective is just from someone looking at things with fresh eyes. Since this project has been with you for over a decade, it’s totally natural that some aspects might go into autopilot or get a bit of tunnel vision. What I meant by "tight control" is that it feels like most things — or nearly everything — end up depending on you. A few things that stood out to me: You're the only one who can commit. That can give the impression that there's a lack of trust in the community. I get that quality matters, but even the most successful open-source projects had to open up at some point. There are many long-time users and proven professionals here who could help with small fixes and improvements — which would make things move faster and ease the burden on you. The master branch is still the default, even though folks on the forum have already pointed out that switching to the dev branch might help newcomers see the project as more active. The development of the new admin theme, while impressive, also felt like a missed opportunity to leverage community input earlier in the process. What exactly does “community” mean in this project? For many of us — like @bernhard and others — PW isn’t just a hobby, it’s the foundation of a businesses. That’s why transparency and shared involvement matter so much. And just as a practical thought — what would happen if, for some unforeseen reason, you were no longer able to maintain the project? Things like GitHub access, the website, and the forum are all critical. It might be worth thinking about a foundation or even just a small board to help guide the future of PW together. That’s the kind of "tight control" I was referring to, and I hope this version makes more sense. Again, I really do appreciate everything you’ve built — and I say all this in the spirit of constructive feedback and shared care for the future of the project. All the best!