All Activity

I too like Krystal. One of the few good cPanel hosts out there and ideal for UK based clients. As they use Litespeed you get the performance of NGINX with full support for Apache .htaccess.

Ryan, thank you for clarifying. This totally makes sense now :-)

@gebeer Throttling is what enables us to allow the AI bots, rather than having to block them for taking over the sites resources. So long as the bots adhere to the rules established in the robots.txt they'll never get throttled. But if they ignore the crawl delay, then those requests get throttled with a 429 error. We even include a retry-after header telling them when they can try again. I used to have to block these bots outright in order to preserve the resources for you and me. Now they can crawl as much as they like, so long as they follow the speed limit. The throttle feature provides a way to enforce the speed limit.

Hi @gebeer While I understand your concern about blocking AI bots but what I get from Ryan's post is that he doesn't completely cut off AI bots. It is because they come too often. He just want to limit their visit rate. I think it is ok because I don't think the document part changes every few seconds. Gideon

Hi @ryan, maybe I'm misreading this. But actually you would want bots to collect training data for PW, especially for the API reference part. This website does not publish content that is protected IP. It offers information that aims to attract developers and decision makers to use PW for their business. IMHO, blocking these bots is contra-productive. You are cutting yourself off from a growing number of developers that build projects with AI tools to boost their productivity. In the near future we probably will not be able to compete if we do not use these tools. The more accurate training data and context these AI assistants have for PW, the better they can perform and produce actually usable, production ready code. I would give the current approach of blocking these bots a second thought.

Hi @ryan, This new version of WireRequestBlocker has a breaking change relative to the previous version in that it now requires PHP >= v8, due to the use of str_starts_with(). Because pro modules are not upgradable via the PW admin users don't see notices about requirements before upgrading (and the PHP 8 requirement isn't stated in getModuleInfo() in any case). Could you please highlight the PHP 8 requirement somehow, or change the code so it has the same requirements as previous versions of the module? Thanks.

@bernhard I'm always interested in making updates to the modules directory, but over time as bandwidth is available to do so. So currently the modules directory does require a populated README.md in your GitHub repo. I'm definitely open to supporting more options, but short term you'd want to make use of what the modules directory currently supports. Any module missing a populated readme shows that message. For paid modules, that's a category called "premium modules", so if you add your module to that category it should show up as a paid module. The "since" date is the date it was added to the direcgtory.

I like your suggestions for maintance plans. I could create plans based on that and add some things. When it comes to improvments, my e-commerce projects almost always require regular updates and new features. In contrast, simple marketing websites usually need far fewer changes. I am working on 2 smaller websites in Processwire right now. Ecommerce is something I am stll not sure which platform to use. But that is separate discussion.

Many websites these days are the feeding ground for AI bots. Especially this site! In this post we look at a tool for taming all the hungry crawlers and bots… https://processwire.com/blog/posts/throttling-ai-bot-traffic-in-processwire/

Bit late to this topic but it is an interesting subject. I work a lot with WordPress and hoping to do more ProcessWire. I'd suggest the maintenance covers a client's general web needs. For example, content support, troubleshooting, on-going improvements such as new features, performance monitoring, site reviews etc. Updates can still happen and I'm sure they'd want re-assurance this is covered, but it isn't always the top priority like it is with WordPress. I'm sure clients would rather have their developer work on improvements than installing updates. Even if a client does not need that, it will free up more time for new builds. With WordPress I do so much maintenance I have less capacity for new projects.

Actually, those assets are not necessary just to view the documentation, only the ones in the help directory are needed. I'm not sure why it tries to load them (will look into later), but it should not affect the display of the help.

If this is the source of the documentation website, https://github.com/MetaTunes/Metatunes.github.io/tree/main/DbMigrate, then I don’t see those assets.

I doesn't work for me in Chrome, Edge, or a simple wget. wget https://metatunes.github.io/wire/modules/Jquery/JqueryCore/JqueryCore.js --2025-09-12 08:35:37-- https://metatunes.github.io/wire/modules/Jquery/JqueryCore/JqueryCore.js Resolving metatunes.github.io (metatunes.github.io)... 185.199.109.153, 185.199.108.153, 185.199.110.153, ... Connecting to metatunes.github.io (metatunes.github.io)|185.199.109.153|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2025-09-12 08:35:37 ERROR 404: Not Found. Maybe it has something to do with the CDN github uses? I'm from the netherlands.

Hi @spoetnik. Could you give more context for that? Versions, browsers etc. I can't replicate the problem.

Hi @bernhard, I tried again to change the permissions, but had the same issue with 755. So I set it back to 775 and live with that. This is also recommended by the web host.

News: "...npm got rocked by a record-breaking exploit..." https://youtu.be/QVqIx-Y8s-s And self-driving cars, AI agents, refrigerators, cat feeders, and who knows what else are and will be based on code written by who knows who...

The logs directory definitely does NOT need 775. See https://processwire.com/docs/security/file-permissions/#permission-755-for-directories-and-644-for-files 755 is the least restrictive recommendation and as ryan notes if it can be locked down further its recommended to do so. If it only works for you with 775 that's a good and a bad news: good: you know that permissions are the issue bad: you should fix it properly to make it work with 755 ...which should be the case if the webserver runs as the same user that owns the directory and log files. You might want to talk to your hosting company if you are not hosting it yourself.

Scripts and stylesheets aren't loading

Hi@bernhard, thanks for your hint. I played around a little with the permissios and found: the logs-directory needs 775, the files stay at 644. Now everything is fine.

This means that only the owner of the file can write to it. Does it have the correct owner?

It's working fine for me!

I've tried the competition out and now I'm back to try this one again to compare 😁 Is there an issue with your docs page at the moment though? It seems to be loading with no/minimal CSS which just makes it a bit rough to read.

Hi @matjazp, thanx for your reply and explanation. I really did not use the FieldtypeSelect module and could delete it without any disadvantage. I started with PW ten years ago with two projects. After a learning phase and a lot of help from this forum, everything ran without problems until I decided to update this website http://malabu.de. I found some old modules and problems with the current PW version. And again I found help. So I have to say thanx to this beautyful forum and this great CMS. Günter

FieldtypeSelect is very old module from 2013 that "produces a drop down list (via a "select" input) that would allow you to define a list of options in the field's configuration from which to select a value. After installing, you'll have a new "Select" fieldtype that will allow you to define the items you'd like in the drop down. You'll be able to define these options in a text box on the field's configuration screen. Just put each option on it's own line." Github Repo: https://github.com/Hani79/Processwire_FieldType_Select_Drop_Down My fork: https://github.com/matjazpotocnik/Processwire_FieldType_Select_Drop_Down You should use FieldtypeOptions nowdays. Can't answer that, see if the fieldtype Select is used in any template?

Thank you very much @Robin S I modified the code a little bit to fit my needs and now it is a rally simple but very effective solution for handling global media / file management in ProcessWire.