All Activity

Yes, that's great, I have used that, thanks. I'm particularly interested in managing 100s to 100s of references.

Hi, if your page reference field is used for a single page selection, you may choose "page auto complete" in the input->input field type select, it is ajax powered and works very well 🙂 the only big difference is that you have o know at least 2 or three letters of the page title you're looking for it works great too with a hook (custom php code) allowing you to select several parents, templates and so on if needed have a nice day

I just wanted to check this is okay before I roll it out. I'm pretty sure it is but I wanted to be sure. Let's say you have: Parent page [template=parent] Child page [template=child] In the back end site tree if I want Child page to be viewable and editable by the current user but I don't want Parent page to show in the site tree. If I remove all view permissions for template=parent but allow for template=child, will they still be able to view Child page and edit it (if I supply them with the direct link)? I stupidly asked AI this question and it's adamant permissions are inherited regardless so if you can't view a parent there's no way at all to view the child. 🤔

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.

From a database perspective page reference fields should scale quite well and there's always the option to build a custom table managed with hooks if you need something ultra fast so you have control of the indexes. But, in the admin, is there any field type that scales well? I've tried them all out and from what I can see, all page reference field types and input types, do not have the option to show your page references in a searchable, paginated lit loaded by AJAX; they all go in a single list. I can imagine this getting problematic once the number of page references gets moderately big. Is there such a thing? What do you do if you have 100s of references, 1000s of references or more? At what point are the standard page reference fields no longer an option?

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 @tcnet I have a fix request for Login Fail Notifier 1.0.4: fix Undefined array key "SERVER_NAME" under CLI getDefaultData() reads $_SERVER['SERVER_NAME'] unconditionally, and since the module is autoload, __construct() calls it on every bootstrap. On a web request that key always exists, but under CLI (php index.php …) there's no request, so it's undefined, hence I get a lot of PHP Warnings: Undefined array key "SERVER_NAME" on every CLI run. With display_errors on it also lands on stdout and breaks tools that parse CLI output (e.g. JSON). Fix for line 79: 'notification_subject' => 'Failed login attempt at '.($_SERVER['SERVER_NAME'] ?? ''), I applied that fix to the module on my sites, but could you please also apply it? Thanks in advance!

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

Stunning work @maximus How the preorder works in digital products? Is the buyer receives automatically an email with a download link during the release date of the product? Also, can we create and integrate more payment methods?

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

I'm using PW 3.0.255 but I'm not getting the "open:wire" message but it seems it has been fixed on PW 3.0.258. EDIT: It happens only with PHP 8.4.

Related? https://github.com/processwire/processwire-issues/issues/2203

This is probably triggered from a module you have installed.

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

Thanks Peter. Yes, that is a very good point. Mercato currently supports digital downloads, download links, limits, expiry, and order-linked access, but license key management is not included in the first public testing release yet. It is definitely something I am considering for digital products, especially for software/plugins/templates where the download itself is only one part of the purchase. The shape I have in mind is something like: generate or assign license keys after payment store license keys against the order/customer/product show them on the public receipt/order status page expose hooks so developers can provide their own key generator optionally add a small validation API later I would like to keep this flexible rather than build it around one licensing model only. So short answer: not in 1.0.0 yet, but yes, it fits the direction of Mercato and I would like to support it.

Hi @marie.mdna Thanks for your feedback and the great suggestion! I can see the need for group bookings (like workshops or classes where multiple people join one slot). However, implementing this directly into WireBooking would be quite difficult. The module's core architecture and database structure are designed for single-appointment bookings (one slot = one person). Adding group capabilities would require a major rewrite of the booking logic and slot validation. I think this would actually make an excellent idea for a separate, dedicated module (e.g., WireGroupBooking or WireEvents), as the requirements for managing capacities, waiting lists, and group check-ins are quite different from a lightweight appointment scheduler. I will definitely keep it in mind for future ideas, but for now, WireBooking will focus on staying lightweight and tailored for 1:1 appointments. Best regards, Markus

This is such an interesting module, love that it is GDPR compliant 🙂 I was wondering, did you consider group booking? Such as day long events with a maximum of participants/day/event?

I stand corrected. Module versions are not tracking anymore.

Congrats Maximus. Always a great feeling to solve your own problems. I didn't see a mention of license keys, but is that something you are considering supporting for digital downloads?

Hi, i am just curious: Why PW shows a "open:wire" message on login and what does it mean? PW 3.0.255.

Thank you so much for your kind and thoughtful feedback! It really means a lot, especially coming from someone with your experience in both ProcessWire and professional e-commerce. The main reason I started developing this shop system was exactly because I felt there was a gap in the ProcessWire ecosystem. I also spent some time looking at PWCommerce, but as you said, the documentation made it very difficult to work with. I also ran into issues with commercial rounding quite early on, and even after quite a bit of tinkering I couldn't really get it to a point where I'd feel comfortable using it for the German market. You're absolutely right about the long term challenge. Building the shop is one thing, but keeping it up to date with changing legal requirements, security updates and everything else that comes with e commerce is probably the biggest task. That's definitely something I'm aware of, and I'll do my best to keep the project actively maintained. Development is still moving forward. I actually added customer accounts to the demo shop just a few minutes ago, so it's slowly growing feature by feature. Thanks again for taking the time to write such detailed feedback. Comments like yours are really motivating and reassure me that building this for the ProcessWire community was the right decision.

Hi @eutervogel! I am extremely surprised and impressed. This shop "module" basically came out of nowhere and solves a huge "black hole" in the ProcessWire community: A functional, up-to date and all-in-one shop solution. I made a shop with Padloper (Version 1) years ago which was one of my first PW projects ever. And in my main job I am working for one of germanys biggest e-commerce shops. Coming that way I now what immense work setting up, developing and not least maintaining an online shop is nowadays. You have tons or regularities that you have to take care of and each year something is added. For example: Last year all bigger online shops had to be be overworked due to the German Accessibility Improvement Act now the latest "addition" was the integration of the "electronic cancellation button". If you offer a shop solution for a client based on an existing system or "custom made" - you have to be in constant awareness of the legal changes and act immediately. Then you have to design the landing page, category pages, product pages, the checkout pages, search pages and the whole customer backend. Not to mention many many e-mail templates. Because of that the last shop that I set up for a client was actually a Shopify solution. That still was a ton of work, especially if you consider the countless hours for reading the developer docs and becoming familiar with the Shopify CLI and the whole template/development system (and so on!). So it's nice to see that there is a PW alternative now. I like the fact that everything is integrated and the documentation seems to be extremely well planned. I can remember that there was another shop module for PW around that looked promising but offered little to no documentation at all. What a bummer.

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.