Recently Updated Topics

Thanks @Roych - much appreciated. I have another couple of PRs for you: - fix tab querystring so now you can reload or share the URL to a tab - added another bot filter to better exclude bots probing for URLs that don't exist, with an option to still display them in the 404 panel if you want (for attack path visibility).

Hey folks, Quick question, is there anything you usually do to the database before pushing a project to a live server? Any kind of cleanup, optimization, that sort of thing? The reason I'm asking is that during development it's pretty common to install/uninstall modules, add and remove fields, rename things, test content... and after all that back and forth I'm a bit worried about leftovers sitting in the database that I might not even be aware of. Orphaned fields, stale module data, log entries, sessions, you name it. Do you have a checklist you follow? Any specific things you always make sure to clean up? Cheers.

Hi @kixe, with the current version 1.2.6, I get the following error message: Error: Class "DirectoryIterator" not found in /site/modules/CronjobDatabaseBackup/CronjobDatabaseBackup.module:351 As a result, the cleanup didn't work and it had filled up the storage to its limit. Could you have a look, please?

Hello Horst, is there an update regarding the OAuth compatibility? We need to connect to an microsoft office mail server which does no longer support basic smtp auth. I saw this issue on your github page: https://github.com/horst-n/WireMailSmtp/issues/22

We just tracked SystemNotifications down as the cause of extreme slowness in our system (30 seconds wait while logging in/out or redirecting). On login and redirects there's a database query to clear the field_notifications table for page_id 41 (the admin user), and then in our case insert approximately 13,000 rows back into the the field_notifications table. These rows record every login/logout to the system since its installation many years ago. So in total we were generating about 14,000 database queries for every ProcessWire login, which is why it was so slow. Going into the SystemNotifications module admin and clearing the tick boxes for all three "Active automatic notification hooks" fixed the problem. I'm tempted to uninstall the module, but I'm not sure if it supports any other function we rely on. Having users notified when someone else is editing the same page is very handy, for example.

Fantastic! I'll be using this a lot. Thanks @adrian

Ok, I could not find the cause for this problem (likely some tag nonsense introduced during the editing), but I could find one workaround solution: I just have to copy the content of the rendered field in question, open the page for editing (backend), delete its content and paste the content I copied previously. After that, the frontend edit works fine.

Hi @Stefanowitsch, I'm waiting for the modules to be approved so I can post the link here. We've hit a bit of a loop: to request publication of a module, you have to publish a post and include that link—but I don't actually have the link to the module at the time I'm publishing the post. I'm planning to edit the posts later to insert the link once the module has been approved.

Hi everyone, Building a package forwarding platform means dealing with phone numbers from dozens of countries. US customers, European recipients, warehouse staff - each expects a different format. Storing a raw string and hoping for the best doesn't work. This fieldtype does it properly. GitHub: https://github.com/mxmsmnv/FieldtypeTel What it does Powered by intl-tel-input v28 - bundled locally, no CDN dependency. Country flag picker with search Stores four formats per number: e164 - +12025550123 - for tel: links and shipping APIs intl - +1 202-555-0123 - for international display national - (202) 555-0123 - for local display country - us - for filtering and selectors echo $page->phone; // (202) 555-0123 echo $page->phone->e164; // +12025550123 echo $page->phone->country; // us // tel: link echo "<a href='tel:{$page->phone->e164}'>{$page->phone}</a>"; // Selector — find all Australian numbers $pages->find("phone.country=au"); Restrict countries, set preferred countries, per-field defaults Auto-format as user types AdminThemeUikit themed - light and dark mode via --pw-* CSS variables Requirements: ProcessWire 3.0.200+, PHP 8.2+ MIT License.

Thanks @adrian, working great now. Yes, love this feature here, and in the Tracy Console too. Thanks for adding it!

A background job queue for ProcessWire. Push tasks onto the queue from any template or hook, and let LazyCron process them automatically in the background — with priority levels, delayed execution, automatic retry with exponential back-off, and your choice of file or database storage. https://github.com/wirecodex/SimpleQueue Alpha — v0.1.0. This module is in early testing. The API may change before a stable release. Feedback and bug reports are welcome.

A WireQL-powered query engine for ProcessWire that makes building API endpoints effortless. Execute explicit CRUD operations, apply collection modifiers, sanitize field output, and cross-reference query results — all in a single expressive request. https://github.com/wirecodex/SimpleQuery Alpha — v0.1.0. This module is in early testing. The API may change before a stable release. Feedback and bug reports are welcome.

A fluent HTTP response builder for ProcessWire with full HTMX support, redirects, cookies, and content negotiation. Build JSON APIs, send HTML fragments, manage headers, and handle redirects with an elegant chainable interface. https://github.com/wirecodex/SimpleResponse Alpha — v0.1.0. This module is in early testing. The API may change before a stable release. Feedback and bug reports are welcome.

A modern HTTP request handler for ProcessWire that provides an expressive, type-safe API for accessing request data. Handle form inputs, headers, files, cookies, JSON payloads, HTMX requests, and client information with an elegant, fluent interface - all while maintaining ProcessWire's philosophy of simplicity. https://github.com/wirecodex/SimpleRequest Alpha — v0.1.0. This module is in early testing. The API may change before a stable release. Feedback and bug reports are welcome.

A modern, fluent HTTP client that makes consuming APIs effortless. Send HTTP requests, handle responses, upload files, manage authentication, execute concurrent requests, and download remote files - all with an elegant, chainable interface. https://github.com/wirecodex/SimpleClient Alpha — v0.1.0. This module is in early testing. The API may change before a stable release. Feedback and bug reports are welcome.

That's huge. Obviously not a full solution as manual testing is (even with AI, so far) still required, but a big burden can be mitigated right at the start. 👌 Same for the SEO, but even moreso for the template file security scan. ❤️ Always happy for good documentation that PW is known for.

@elabx - that's what Claude suggests. It looks more like a poor implementation in InnoDB itself to me but I'm sure there's reasons for why it behaves the way it does. Either way, I'd definitely be interested to hear what @ryan thinks.

@markus-th Good catch! That was a formatting bug — PHP was rendering very small values in scientific notation (9.0E-6 kg) instead of human-readable units. Fixed in v1.7.0: the dashboard and DOCX export now auto-scale to µg / mg / g / kg depending on magnitude, so your total will show as e.g. 9 mg instead. Thanks for spotting it! @Peter Knight Love this idea — just shipped it in v1.7.0! Each bar is now colored by the average CO₂/request for that hour: green = Grade A (<100 mg), yellow = B, orange = C, red = D. So when you optimise a heavy page or compress images, the next day's bars literally turn greener. Tooltip also shows avg mg/request and Grade on hover. A/B/C/D legend sits above the chart. Looking forward to hearing how it goes when you try it!

@ryan - I just did some more testing and I get the same error even if I just instantiate another PW instance in a regular template file. No other code after that, just: $ca = new ProcessWire('/var/www/othesite.com/html', 'https://othersite.com');

Wow!!

Some time ago, I decided to install xdebug on my development server, but I never really needed it or used it. TracyDebugger is enough for what I'm doing. I didn't notice it then because my app was not highly developed at the time, but it really causes speed issues especially if you're working on a sophisticated site with a lot of business logic. For a long time, I thought it was just ProcessWire itself being slow, my app being slow due to some optimizations I hadn't done yet, my database being very large, combined with my low spec dev server, but it turns out disabling xdebug, which I had long forgotten about, made things much faster. Just a heads up if you're having speed issues!

Hi @maximus, Thank you for taking my request into consideration, I have updated Ichiban and I can confirm that in my case {combo.field} and combo.field is working as expected and og:image is showing as intended, the only detail is when I’m using combo fields as source for OG image URL, Ichiban doesn’t show the resolved path and social preview doesn’t show up, but it’s still rendering the correct URL in the source code. In pages that have a unique image field {image} shows the correct resolved path and the social preview image

A router layer over URL segments API that replaces complex if/elseif chains with clean, expressive route definitions. Supports named parameters, type aliases, regex constraints, optional segments, wildcards, and HTTP method matching — all wired directly into ProcessWire's template system via page hooks. https://processwire.com/modules/simple-router/ Alpha — v0.1.0. This module is in early testing. The API may change before a stable release. Feedback and bug reports are welcome.

A tiny ProcessWire admin utility. Hold a modifier key and click any Inputfield toggle to copy the field's machine name to the clipboard — without collapsing the field. Useful when building templates, writing selectors, or debugging: no more hovering to read the name in the title attribute. Github: https://github.com/dlzi/FieldNameCopier

This module provides a ProcessWire Admin UI (“bridge UI”) for the ProcessWire Console ecosystem. It does not re-implement Console features itself; instead it integrates with: trk/processwire-console (required for most features) trk/processwire-boost (optional; status/info only) Module repo