All Activity

This week there were 45 commits on the dev branch for ProcessWire 3.0.268. The most interesting updates were: Added checkboxes in the Setup > Fields list, so you can bulk delete or export. Added new getRaw() and saveRaw() methods for WireCache ($cache) Added $page->meta() support to PagesExportImport export and import (via @jploch) Added WireTests test framework files and API.md documentation for the following, which finishes up the Inputfield modules: InputfieldTinyMCE InputfieldImage InputfieldFile InputfieldTextTags InputfieldSelector InputfieldPage InputfieldIcon InputfieldPassword InputfieldPageAutocomplete InputfieldHidden InputfieldPage InputfieldPageTitle InputfieldFieldset InputfieldMarkup InputfieldPageName InputfieldName InputfieldPassword InputfieldForm These were done using the AgentTools scheduled tasks Round-Robin feature that rotates between different agents. In this case, between DeepSeek v4 Pro, Kimi K2.7 Code, GLM 5.2 and Claude Opus 4.8. After each API.md and code review was finished, they were queued to GPT 5.5 who verified everything, made any necessary fixes, and then built a WireTests ClassName.test.php file for each. Following that Claude Sonnet 4.6 gave each API.md, ClassName.test.php and ClassName.module a final review and commit. In addition, we have a new version of AgentTools that adds the following: New MCP server support New WireTests coverage Improved CLI safety and migration checks New AgentTools logo added to README (design credit to GPT 5.5) There's also a new version of ProCache posted this week that adds CLI command support, AGENTS.md and API.md files, and fixes a few bugs too. As always, visit the ProcessWire Weekly for the latest news and updates. Thanks for reading and have a great weekend!

I would add a feature to remember the collapsed/expanded position via a cookie in the browser

@JossI'm not sure I follow what you mean about "failed to create the subdirectories in jobs"? There is a /site/modules/AgentTools/tasks/ directory, where the predefined tasks are stored, is that what you mean?

Wow love that view! Nice look out the window too.

@Joss It won't let you upload a new one? Does it give you an error message or anything? We've been having some issues with the forums showing 500 errors when the bots start hitting, so it might be worth another try just in case the upload hit a 500 error. You can always send it to me and I can figure it out too. @Adam Kiss is another one to add to the list of people it would be good to see return.

I just gave this a quick spin. For context, I've developed a couple complex ecommerce sites with ProcessWire, going back to 2014. I've also experimented with Padloper. I suppose what I find interesting is how data is stored (ie what fields are used). My approach has been to use repeaters for things like the line items, even addresses. With Padloper, I believe Kongondo used entirely custom fieldtypes/inputfields. I see that with Mercato it's using textarea with JSON in it for things like the billing address and cart items. Were there specific reasons for that approach?

Well, I might just be back a bit too. But I have a problem. I decided to update my little profile photo. It happily got rid of my old one, but won't let me upload my new one!!!!! Grrr. And so good to see my brother in fantasy @Soma back amongst the brave!

I thought about this as well... somewhere last year/the last years and even prior but couldn't fight my innerer Schweinehund* to follow and keep up with that thought. Back then... everything in that direction was still somehow complicated and not that easy. But today... this could be a super awesome workflow, yet not as easy to share between developers as TailwindCSS. Back to what I remember. What I remember is: Using a more modern CSS reset (Andy Bell) - https://piccalil.li/blog/a-more-modern-css-reset/ Using custom web components (Kevin Powell) - https://www.youtube.com/watch?v=b_x3kzapvcI Using NoBuild - and only individual files (DHH/David Heinemeier Hansson) - https://x.com/dhh/status/1719041666412347651 * The innerer Schweinehund (literally "inner pig-dog") is the iconic German idiom for that stubborn, lazy voice inside you. It's the ultimate excuse for procrastination, the force that tells you to stay in bed, skip the gym, or not build your own CSS framework when you know you should be productive.

@ryan that is exactly the one I have been playing with today. The 14b version. Unfortunately, qwen 3 coder only comes in 30b and 40b, which is pushing it for me. I might try it again with Ollama. It suffered with LM Studio, but Ollama is meant to be better at dealing with local problems like not having a huge stack of GPUs lying around! The hard bit is the prompting. I was trying to get it to do a very simple page. Create a data set, then search it and spit out a single result. It was determined to ignore the search result and just loop the dataset. Grr! EDIT: By the way, when I installed, it failed to create the subdirectories in jobs. I have hand created them and copied the htaccess file from jobs into each one. Is that right? Anyway, here is the reason for the large box, and the view out of my studio window! Let me know when you start a podcast and need an editor!

Thankyou @pideluxe

@Joss Wow, that sounds like a nice hardware setup you've got there. And 128gb ram is like having a bag of gold right now, nice pirates booty. Have you tried Qwen 2.5 coder yet? Not a new model, but seemed pretty good when I tried it: https://ollama.com/library/qwen2.5-coder

Thank you, kind sir! (The Pirate bows!) I will have a play. I have been using qwen instruct but also have a few other models. I am a little limited because I only have an RTX 5080. Google's AI swore blind I could run a 31b model with a fair amount of offset (I have 128gb Ram), but I last saw the machine crawling out from under the desk, sweating and groaning, so I am playing with the 14b instead with 1.5b for autocomplete! I will get there. Honest! I still guess at all this stuff.

@Joss Yes, on the "Agents" tab, enter a new Agent with the settings (replacing the model ID with whichever model you are using): Model ID: llama3.1 API key: ollama Endpoint URL: http://127.0.0.1:11434/v1 Label: Ollama llama3.1 The API key can be any non-empty value, like ollama, because Ollama usually doesn’t require one. AgentTools requires the field to be populated. The endpoint can be either one of these: http://127.0.0.1:11434/v1 http://127.0.0.1:11434/v1/chat/completions The model ID must match an installed Ollama model name from ollama list. Note that the Engineer relies on tool/function calling. So the Ollama model needs decent tool-call support, or it may answer text but fail to use eval_php, site_info, etc. For AgentTools, a coder/instruct model with tool support is the safer choice. Btw, if the connection works but Engineer behaves oddly, try a stronger tool-capable local model before assuming the config is wrong. Local Ollama can be great, but AgentTools asks a lot of the model because it needs reliable structured tool calls.

Hi Ryan! Will this, or something, talk to Visual Studio Code via Continue and Ollama? (I have LLMs locally). I am still trying to get my head around what is possible for site development with AI and Processwire - not helped that I am so out of date now!!! Joss

Hi everyone! Just wanted to get a general feel on the documentation pages of the new website, is anyone else finding troublesome that the main sections of the documentation are now collapsed? Weren't these sections "less collapsed" or maybe I an hallucinating (i know it's in fashion) ? Wouldn't it just be better to have all of this expanded, in a big chunk of text? I really feel it makes it hard to use the documentation pages, wouldn't it just make more sense to have submenus under the API variables? Here's a quick mockup of what I think could be a more pragmatic layout:

Revisiting this topic again... I want to use vanilla CSS as much as possible moving forward, but I'm trying to find a "base" from which to start. This base would come with an opinionated way of organizing files, a reset, breakpoints and perhaps stub-out certain components and use all the latest CSS features. I can't seem to find anything like that and that's also pretty recent. Any suggestions?

👍Then use "Schlagwort / Schlagwörter".

Hmm, interesting. Thanks @pideluxe I actually have Tags reserved for a different part of the Module. So just to recap Tags = used for front end display like you probably already understand. Tagging images in an images field. Labels = similar purpose but used for Library organisation in the admin area

Actually, we use "Etiketten" just for physical labels. One could use "Schlagwort / Schlagwörter" or "Tag / Tags" for more tech-savy users.

Thank you in advance! Nothing is urgent, of course :)

I'll change that as soon as I've time.

BTW is this the best translation for Label and Labels? Google seems to suggest a few variations Label → Etikett Labels → Etiketten P

Hi If you are using 1.19.50 Beta, you may have experienced 2 translation issues. These are fixed and scheduled for the official 1.19.50 release, but if you're stuck, please DM me. German language CSV import fails with 'Undefined array key' warnings German translation: glossary fix — Label → Etikett, Labels → Etiketten Vielen Dank fürs Lesen, i believe 🙂

ok... it seems that this is not the problem, and we've moved on.

I am trying to learn php and "proper" dev practices (terminal, git, staging). My background is in no-code apps, but I have a solid knowledge of HTML and CSS. I started building a personal site on Neocities, very nice, but I realised that I needed a CMS. ProcessWire has been fabulous so far, while I've been creating files on my live hosting (LOL). I'm using Ai to help guide me through the "proper dev" practices, and honestly, it's been great. But now we're stuck. I'm trying to load my site locally. I've been getting various errors, blank screens. Ai insists that I need bootstrap.php and I need to get a fresh install of PW. When I look at the files in PW, there is no bootstrap.php. This page https://processwire.com/docs/front-end/include/ mentions bootstrapping, but no mention of the "missing" bootstrap.php file. Any ideas?