All Activity

But there is one thing we can all agree on, and that is the new design is quite controversial. And as far as I can tell, one either likes it a lot or does not like it a lot. And I don't think that such a controversial look is good in general. As for being "contemporary"? I started my designer career in 1997 and back then everyone used QuarkXpress, Aldus Freehand, and Color Studio (later Photoshop 2.5+). Because Macs were not too powerful, most designs were put together in QuarkXpress only. Why am I bringing this up? Because the current processwire.com design does look like "QuarkXpress only designs" from about 1995-2002. For this reason, to me, this is vintage.

Hi when it comes to a "select" just install the select options module which is in pw by default and then when adding a new field you'll be able to choose when it comes to images, having a close look at the full article from which the image you show comes https://processwire.com/blog/posts/pw-3.0.142/ you'll see that it relies on a template you create witjh a given naming convention --- quote--- Rather than trying to come up with some new way of defining custom fields, you define the custom fields for your file/image field with a Template. Simply create a template having the name "field-[name]" (replacing "[name]" with the name of your file/image field), add fields to it, save, and that's it. It's okay to add fields that might duplicate those already on your regular page template, as the fields for files/images are properties of each file/image rather than properties of any page. ------- not only will you be able to use radio button but nearly any kind of fields you would like to associate to the image hope it helps a little 🙂 have a nice day

How can I use a radio button with multiple options (as shown below in the image under “license”) in an image field? Is this also possible with a select field? Which fields can I use?

I disagree. As a designer and developer, I think the new design is much more professional, contemporary, and appropriate. Compare it to the Dupal or WordPress website. Do you think they are better positioned? What information do you think is missing for customers?

I burnt some credits on Seedream v4. (BTW, Our grandchildren will surely ask us: Grandma, Grandpa, is it true that your image generators were so stupid back in your day?)

Recommended read: https://www.smashingmagazine.com/2025/10/the-grayscale-problem/ Quote: "Colour seems an appropriate place to start. When given the choice, try something audacious rather than safe. The worst that can happen is that it doesn’t work. It’s not like the sunk cost of painting a room; if you don’t like the palette, you simply change the hex codes. The same is true of fonts, icons, and other building blocks of the web."

Hello, A few days ago I could add videos to a body field on pages using a basic-page-like template (file). And the videos can still be seen now (in Vivaldi and Firefox Developer on Linux Mint Mate Edition). But I've just tried now to add 2 different videos on 2 pages using the same template (file), and they are not displayed in Vivaldi or other chrome-based browsers, even though I see the embedded code with the web deveopment tools. In Vivaldi I see this error message: "["name" from Parameters from the page where the video is]/:69 Unrecognized feature: 'web-share'." But I can see them without any problem on Firefox Developer (even though I see other error messages that seem related to youtube "embed". I cleared the cache in the module and not just one time (I changed from 720p to 1080p - and tried back with 720p -, and had tried the GDPR option). I even erased the compiled files in Modules -> Site. I cleared all the website's cache, and also the browser's cache, several times. Any idea(s)? Thanks in advance! Edit: I don't see them anymore in Firefox.

Thank you Jurgen. By comparing your template with my code I see what I did now. I copied a template you created on 15.02.2023 but somehow I'd deleted the line '<p>[[TITLE]]</p><ul> from $body. Dur! Thanks again.

Hi all, first of all I'm sorry this is going to sound a bit negative. But ever since the new website launched I feel like it's increasingly difficult to convince clients that have never heard of ProcessWire to use it. Have any of you experienced the same? I'm not a designer, but I feel like the content and the design have been made to target developers. That's valid, but if our client's don't want to use the system, neither can we, at least professionally. In my opinion at least the homepage would need a design and content overhaul to streamline the first impression and explain to non-techies why ProcessWire is awesome.

What module are you talking about?

Fix confirmed. Thank you!

Hi @David Karich this is awesome news. Thank you for all your hard work on this!

@Jonathan Lahijani, I've released a new module that provides an overview of field access settings:

Field Access A Process module that provides an overview of field access settings, including template overrides. Usage The table has a sticky header so that the columns can be understood when the table is scrolled. The empty space underneath the table is to allow scrolling to the bottom of the table. There are fields for filtering the table by field name or by template name. The field names link to the Access tab of the field settings, and the template names link to edit the access settings for the field in the context of that template. A collapsed field at the top of the page has information about the meaning of the table column headers, and tips for understanding the values in the table: Table column headers Control: Is access control enabled for this field? View: Roles that can view the field Edit: Roles that can edit the field Show: Show field in page editor if viewable but not editable (user can see but not change) API: Make field value accessible from API even if not viewable Overrides: Overrides of the field access settings in template context Tips If the guest role has view access then it means that all roles have view access. You can hover the guest role in the View column to see a tooltip with all the role names if you want a reminder of those. Overrides: when access control is enabled as a template override, the Control, View, Edit, Show and API columns only display settings that are different from the field access settings. If a column is empty it means the field access setting applies. https://github.com/Toutouwai/ProcessFieldAccess https://processwire.com/modules/process-field-access/

Thanks for reporting this @BrendonKoz. It should be fixed in v0.1.4

I quite agree with your two points above. "Section for practical code examples." They could be added to the method descriptions, and not just sample code strictly related to a given method, but code showcasing typical scenarios with related methods and often used techniques, "coding patterns". "Currently a lot of core features are very fragmented and hard to find if you don't know they exist in the first place." So true! I have some notes of some important settings, which I often set up differently from the defaults, but having to look through them just to find something is time consuming. Some sort of clever way of gathering information and providing it in a categorized and digested way would help, I think.

Thanks @BrendonKoz! Will check this out.

The FieldtypeMeasurement module might be another option (I haven't used it myself yet, but it appears to offer time conversion). It may need some massaging to allow the interface to behave the way you want, but I'd think it would assist you quite a bit. I saw in the module's README that it has second, minute, hour, day; I just don't know if it offers (out-of-the-box) microseconds. The combination input values might not default to the formatting you'd want to provide end-users. Honestly, I'd probably just use a text field and handle the calculations myself, unless they have strict database requirements or comparisons that you'd need to do in the future. Just in case this is useful for your project (referencing a now-fixed rounding issue with Float values in PW):

Hi Robin! I haven't yet identified how/where this is occurring, other than that it is. In a repeater field utilizing a TinyMCE-enabled textarea field, the (I assume) JavaScript injected icon and tooltip seem to be rendered twice. I'm seeing this in both ProcessWire v3.0.246 and v3.0.256 on PHP v8.2 with module version 0.1.3. Not a big deal, just thought I'd report it.

The following is written in somewhat hurry, but I'm sure most of you get what I mean. What Processwire really needs is: Section for practical code examples. Searching through the forum gets tiresome and sometimes it can take hours to find what you're looking for. The API is good, but sometimes very opaque if you don't already posses good deal of knowledge about it. Admin needs some kind of "settings" page that puts things like "password strength" in one easy to reach place. Basically everything the core modules do, should be here. Then if you want to edit something, it will point you to the right module. Currently a lot of core features are very fragmented and hard to find if you don't know they exist in the first place. I think them being in the modules is great, but one page that gathers all that information is easy to digest form would make it better.

Hi all, no ideas so far? I copy the JS from the above mentioned codepen here: window.addEventListener("load", initGallery); function initGallery() { const triggers = document.querySelectorAll(".trigger"); let popImg = document.querySelector("#mypopover img"); triggers.forEach((trigger) => { trigger.addEventListener("click", () => { let popImgUrl = trigger.dataset.full; popImg.src = popImgUrl; popImg.alt = popImgUrl; }); }); } Any help much appreciated! ottogal

Is there a way to enable/disable page protection programmatically? With a hook?

Although I never thought of this use-case, it should be possible as the module uses (IIRC) the MySQL Time type which does have fractional second support.

AgeWire is a powerful, fully customizable age verification module for ProcessWire, built with modern web standards and powered by Tailwind CSS. Perfect for sites requiring age gates (alcohol, tobacco, adult content, etc.). Key Features Two Verification Modes: Simple Yes/No buttons Date Picker with separate MM/DD/YYYY inputs (bot-resistant) 13 Stunning Themes: Modern, Dark, Classic, Minimal, Gradient, Neon, Elegant, Corporate, Vibrant, Nature, Sunset, Ocean, Purple 4 Smooth Animations: Fade In, Slide Up, Zoom In, Bounce In International Date Formats: MM/DD/YYYY (US) DD/MM/YYYY (EU) YYYY/MM/DD (ISO) Advanced Security: Secure, HttpOnly, SameSite cookies Configurable lifetime (1 day to 6 months) Bot protection via manual date entry Smart Exclusions: Skip verification on specific templates or pages Admin pages auto-excluded Privacy & Compliance: Optional Terms & Privacy Policy checkbox Custom links to your legal pages Fully Responsive – Mobile-first design Custom CSS support Tailwind CDN integration (no build required) Installation Download from GitHub Place AgeWire folder in /site/modules/ Go to Modules > Refresh Install AgeWire GitHub: https://github.com/mxmsmnv/AgeWire Download: https://github.com/mxmsmnv/AgeWire/archive/refs/tags/v1.0.9.zip Perfect for: Wineries & breweries Vape & tobacco shops Adult content sites Age-restricted events Feedback, bug reports, and pull requests are welcome! If you like AgeWire, please ⭐ star it on GitHub! Made with ❤️ for the ProcessWire community.

Thank you very much for your detailed answers @jploch, I really appreciate it. In fact, it concerns more PW topics, such as how these are seen and used for page grid. I thought that site profiles and page grid interact with each other, but I wasn't sure, hence my question, including the one about pro cache. When you come from other CMS systems, it's always a matter of ruling out multiple interferences. Thank you for your explanation on the homepage about how I can configure this.