Recently Updated Topics

Hello ProcessWire Team and Community, We are excited to announce that we have developed a new module, SkynetAccessibility Scanner, specifically for the ProcessWire CMS platform. Learn more about our solution: https://www.skynettechnologies.com/accessibility-scanning-and-monitoring GitHub Repository: https://github.com/skynettechnologies/SkynetAccessibilityScannerProcessWire About the Module: SkynetAccessibility Scanner is a powerful accessibility testing and scanning module built for ProcessWire. It helps organizations, agencies, and government entities proactively scan, monitor, and remediate accessibility issues across their websites. It works as both an Accessibility Checker and Accessibility Compliance Testing Software, built directly for the ProcessWire ecosystem - automated scanning, detailed reporting, and continuous monitoring, without touching your site's design or performance. This is a dedicated compliance solution, not a design utility - it identifies real accessibility gaps rather than adjusting visual presentation. Key Features: Automated accessibility scanning Detailed auto-generated reports with severity levels, issue descriptions, and remediation guidance Sitemap-based scanning and monitoring Scheduled scans: weekly, monthly, or quarterly Scanning support in 190+ languages Integrates with the All in One Accessibility dashboard for centralized management Standards Supported: WCAG 2.0, 2.1, 2.2, ADA, Section 508, EAA EN 301 549 (EU), UK Equality Act, Australian DDA, Canada ACA, Ontario AODA, California Unruh, Israeli Standard 5568, Germany BITV 2.0, France RGAA, Spain UNE 139803, Italy Stanca Act, Indian RPD Act, GIGW 3.0, Brazilian LBI 13.146/2015, and Japan JIS X 8341. We would love to have this module listed on the ProcessWire modules directory to help more developers and site owners proactively manage accessibility compliance. Please let us know the next steps or if there's any additional info required from our side. Looking forward to your feedback! Best regards, Rajesh Bhimani Skynet Technologies USA LLC

I also get 403 very often.

Hi as the textformatter module was updated 9 years ago... i would personally be a little careful in my case, i use tinymce codesample plugin (which uses prism too) and then, for the frontend i use the last version of prism with the theme i've chosen and it works very well have a nice day

Hi all, We're a Dutch coaching and leadership institute based in The Hague (Coachcenter, coachcenter.nl). Our current developer is quitting and we're looking for a new party to take over maintenance, hosting and design of our website. The site is built with ProcessWire as the backend CMS, combined with an Ember.js frontend (headless/decoupled setup via REST API). We're not looking for a rebuild, we want someone who can take over the existing codebase and continue from there. We're ideally looking for a developer or small agency based in the Netherlands or Belgium, with proven experience in both ProcessWire and Ember.js. If this sounds like your stack, or if you know someone who fits this profile, we'd love to hear from you. Please reply here or reach out directly at sofie@coachcenter.nl Thanks in advance! Sofie Klerkx

@PWaddictAs per your suggestion I tried renaming, but I am still facing the same issue:

@adrianThanks, i will do it.

Hey everyone. Much to my surprise, my favourite publication on Saturday - ProcessWire Weekly - has a small feature on SeoNeo. I've been reading ProcessWire weekly every Saturday since Issue #1 and never expected to see my own Module mentioned. Thanks @teppo or anyone else who made this happen. I'm not sure what the criteria process is. If you would like to try SeoNeo, any bugs, feedback, praise or abuse is welcome. Github https://github.com/PeterKnightDigital/SeoNeo Official docs https://www.peterknight.digital/docs/seoneo/1.x/ Question, abuse, support, general flattery peter@peterknight.digital Cheers P

Both — the payload is random, the prefix is configurable, and the overall structure is fixed: Format: PREFIX-XXXX-XXXX-XXXX-XXXX — a prefix plus a 16-character payload in dash-separated groups of four. Prefix: configurable per product via the gs_license_key_prefix field (2–16 uppercase letters/digits, no dashes). If left empty it falls back to the module default PGSHOP. Payload: 16 characters drawn from random_bytes() over a confusion-resistant alphabet (ABCDEFGHJKMNPQRSTVWXYZ2345 — no 0/O/I/1/L/U, so hand-typed keys don't get misread), with rejection sampling to avoid modulo bias. That's ~75 bits of entropy. The block layout, separator and alphabet are fixed in code, only the prefix is a per-product knob. If you need a genuinely different scheme, the generator sits behind a LicenseKeyGenerator interface (RandomBytesLicenseKeyGenerator is the default impl) — you can drop in your own without touching the issuance logic. Yes, guaranteed at the database level, not by in-memory bookkeeping: gs_license_keys.license_key carries a UNIQUE index. Issuance inserts the key; if MySQL returns a duplicate-entry error, the service generates a fresh key and retries up to 5 times (LicenseIssuanceService::persistNewKey). This is deliberately a race-safe atomic insert + retry, not a check-then-insert (which would have a TOCTOU gap). At ~75 bits of entropy a real collision is astronomically unlikely, but the guard is there and correct even under concurrent checkouts.

Hey. Nothing wrong with wiggly bananas! I just installed it on one of my own new sites in development. It's much more impressive looking in real life than in the video. I normally don't like any type of design studios within Modules but you've made something very polished and flexible and I can see there are over-rides. So all looking really good. Will get around to the nitty-gritty of the compliance stuff hopefully next week.

@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!

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…