Recently Updated Topics

Hi I want to display some code samples in my TinyMCE field. Is the best approach to enable TinyMCE codesample in the Plugins or is https://processwire.com/modules/textformatter-prism/ a better option? Thanks. A bit rusty on this but I am moving over 200 pages of documentation from a React based app into Processwire.

Hey Peter, thanks a lot — good timing then! On both points you flagged: GTM — Cookie ships with Google Consent Mode v2 built in (toggle it on under Integrations). It fires the denied-by-default signals before your GTM/gtag snippet loads, then updates them live on every consent change — so GTM just sees the standard Consent Mode API and behaves correctly without any custom wiring on your end. Only gotcha: keep your GTM snippet loading after the module's own output so the default signals are already in place when it initializes. Reporting — there's a Consent log (Setup > Cookie > Consent log) with CSV export — timestamp, consent version, granted categories, salted IP hash, configurable retention with auto-purge. On top of that there's a small stats dashboard (accept-all vs. only-necessary vs. custom %, per-category acceptance, a 30-day volume chart) if you just want the at-a-glance numbers without digging into raw export data. Honestly, the Design Studio is the part I'm most proud of. I don't particularly enjoy digging into code just to customize something visually, so I built the whole widget to be styled entirely from that live-preview builder — colors, fonts, layout, icon, dark theme, all of it — no CSS overrides needed. For agency work with multiple client sites that each need slightly different branding, that's probably the bit that saves the most time. (And yes, one of the 7 icon choices is a banana that wiggles when you hover it. No compliance value whatsoever, purely for fun — but I couldn't resist leaving it in. 🍌) Would genuinely love to hear how it goes on your test site — especially if you run it against a client's actual GTM setup, since that's the scenario it matters most for. Feel free to open an issue on GitHub if anything doesn't line up with how your clients have things wired.

@ryan - On a slightly different note, I have just installed the qwen-2.5-32b instruct, and it is running fine on my system via ollama (better at balancing tham LM Studio, it appears). But I have been setting it up for gramma checking, using modelfile to customise it. Basically, it tells it to act as an editor, not to get too creative, then gives some specific instructions over strange words, grammar, etc. It then creates a model for just that purpose. Could something similar be run for AgentTools so that the actual model has specific hard-wired PW knowledge in advance? I don't know enough to say if this would speed things up or anything like that. But it certainly helps with Word as it knows in advance character names etc, without it having to be prompted at the time.

I casually do this with my HERMES (https://hermes-agent.nousresearch.com/) instance, just to train it against my habbits. Or at least I try to. I also become angry, or let it know when I am angry, or whatever about a topic, plan, schedule we had planned or working on. Depending on the model in the background the success rate is mixed - at best. Being more fun and enjoyable sticks way better with HERMES at least. OpenClaw (or whatever its name is nowadays) didn't work out for me at all. HERMES is running on all my office machines (settings are synced via Syncthing) so I can query any of them via Telegram. At least one device is online and reachable from whereever I am all the time. I was curious with HERMES and started chatting with it, like it was someone I met the first time at the bar/office/gym/whereever. We chatted, exchanged details, interests, projects, HERMES also knows my love for TV shows (https://log.nerd.to/tvshows/) and movies - and has access to the repo so whenever I mention something in those regards, HERMES updates that list with new shows or ratings. 🤯 I can ask for recommendations or chat about the latest episode of FROM. I wouldn't do that with OpenCode, Pi, Grok, Droid, Cline, Kilo, or any other agent... but HERMES. It's built for that.

[ah-sht-here-we-go-again-meme.jpg] The current progress of ProcessWire reminds me of the fun I had back when I first discovered ProcessWire. All the features and things I was able to enjoy with ProcessWire I missed in all other tools back then. No limitations or restrictions in terms of templates, fields, pages, content, and everything. I really enjoy it. I love it. 🫡 Thank you, @ryan!

@Joss it definitely sounds like a glitch in the forum. I logged into the admin earlier this week and it's not happy about the php version, it apparently wants 8.2 and we have 8.3, I think. So it could be that. But once I get back to the computer I'm going to see if I can figure out how to get it working.

Ah cool, I have to take a look about that! Thx!

@Didier B. module updated

hi, that sound a litlle logical as it looks a bit difficult to display the pages as a site tree, think about a tree, If you cut off a branch, you also cut off all its twigs 🙂 have a nice day

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

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?

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.

Thankyou @pideluxe

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

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

Nice! Thanks for the quick implementation! I'll give it a try and test a bit.

hi, wow, being french, a night later, i was about to say well the solution would be to create a custom field relying on pw getSelectablePages and something like tom select that allows lazy loading in the select but what @Jonathan Lahijani made is simply awesome!!! have a nice day

For the record: this seems an issue that started occuring in 3.0.265. All previous versions have not resulted in this problem. We are now sticking to the master branch only.

A Jumplinks successor would be awesome…

@Peter Knight Yes, the monitors are at an angle so that whether I'm looking at the left one or the right one, they are always directly in front of my line of sight with no angle. I think it looks more angled than it actually is because I used my phone's 0.5 wide angle lens, which is also why the coffee mug looks a bit stretched.

Hi @eutervogel! I just wanted to tell you that I spent quite some time in the demo shop, testing everything out, and I am pretty impressed with the work you've done! Of course I lack the experience of Stefanowitsch in this matter, but I ckecked out all the other shop solutions for PW and all of them are not suited for EU use. This is something I could work with and/or suggest to a client. In the past I had to refuse all requests for a shop... If you are short of testers? I am more than willing to help! Bernd

Thank you both, @elabx, yes should be disappear soon... 😉

Hi @markus-th I'm glad I saw this as I was just recently looking for something similar. Thanks for making it. WIll check it out soon.Will

WireWall 1.6.0 Released: Traffic History, AI-Ready Logs, and Dashboard Redesign Hi everyone, I’ve released WireWall 1.6.0, a new update for the ProcessWire firewall/security module. This release focuses on better traffic visibility, AI-assisted analysis, and a cleaner admin dashboard. What’s new AI-friendly traffic history WireWall can now save public request history as daily JSONL files: /site/assets/WireWall/traffic/traffic-YYYY-MM-DD.jsonl Each row contains structured request data such as: time allowed / blocked status block reason IP country city / region when available ASN method URL path and query referer User-Agent selected request headers This is separate from the normal ProcessWire log and is intended for later traffic analysis, including feeding recent traffic into AI tools. New setting A new option was added: Save Traffic History It is enabled by default and can be managed from the WireWall module settings. Dashboard redesign The Admin > Setup > WireWall dashboard has been redesigned with: clearer status header protection/logging indicators improved KPI cards better active bans view cleaner top reasons/countries/IPs sections more readable recent events table traffic history status and path display Agent-readable documentation This release also adds AGENTS.md, describing how AI agents and Olivia-style assistants should safely work with the module, including configuration keys, safe/risky operations, and website blueprint guidance. Version Current version: 1.6.0 Release: https://github.com/mxmsmnv/WireWall/releases/tag/v1.6.0 Repository: https://github.com/mxmsmnv/WireWall Feedback, bug reports, and configuration ideas are very welcome.

Hi everyone, I’ve released a new ProcessWire module: Oidc. Oidc adds lightweight OAuth 2.0 and OpenID Connect login to ProcessWire sites. It is meant for projects that need social login or company SSO without a full front-end account-management suite. Repository: https://github.com/mxmsmnv/Oidc What it does Adds OAuth/OIDC login buttons to ProcessWire templates Supports Google, GitHub, LinkedIn, Microsoft, Yandex and Yahoo out of the box Supports custom OIDC providers via discovery URL Works with providers such as Okta, Auth0, Keycloak, authentik, Azure AD and Dex Handles callbacks automatically on frontend pages Supports auto-registration of new ProcessWire users Preserves return URLs through the login flow Includes silent mode for SSO-only sites and intranets Provides hooks for identity resolution, login, registration and provider definitions Verifies OIDC id_token claims with nonce, issuer, audience, expiry and RS256/JWKS checks when available Basic usage After installing and configuring providers, render login buttons in a template: $oidc = $modules->get('Oidc'); echo $oidc->renderButtons(); The page that renders the buttons is also the callback page. Set that URL in the module settings and register the same URL in your OAuth/OIDC provider app. Example use cases Add “Continue with Google” or “Continue with GitHub” to a member area Use Okta/Auth0/Keycloak for company SSO Protect an intranet or private section with silent SSO Auto-create ProcessWire users after successful provider login Add custom rules through hooks, for example restricting registration to a company email domain Documentation The README gives the overview, and the repository includes detailed documentation and agent-readable integration notes: README: https://github.com/mxmsmnv/Oidc Documentation: https://github.com/mxmsmnv/Oidc/blob/main/DOCUMENTATION.md Agent guide: https://github.com/mxmsmnv/Oidc/blob/main/AGENTS.md Requirements ProcessWire 3.0.200+ PHP 8.1+ curl openssl The module is MIT licensed. Feedback, bug reports and suggestions are very welcome.