Macrura

Hey @ryan - just wanted to chime in and pledge my support to you and PW.... Sending vibes. I'm probably also one of the people here who "live" PW. I mean right now it's like 30 hrs a week (probably underestimated) in PW - concurrently 10 sites? ... and in peak seasons, it's like i'm conceptualizing site structures, modules while walking around with a voice recorder. Looks a bit crazy. Anytime you need help it's a zoom call away! On a positive note i see a bright future for the project and from my side, have a some very nice and useful modules cooking, which could only attract more interest in the project (hopefully)

@joaomota Debugging it on a live site could be tricky and risky. Probably the first thing i would do is download the database and hand it to Claude Code or similar to take a look at for any obvious issues. If you updated PHP, check to see if the MySQL host version changed; You can also check the database collation, connection and that sort of thing. You could go into something like PHPMyAdmin and check, optimize or repair tables; Check the codebase to see if there are any PHP compatibility issues. Take backups of the database at each step before you do anything.

Not answering authoritatively here, but I would simply assess whether you need page paths. I enabled it on a site and it also led to some problems – in my case I have pages that render under custom URLS, and use a hook to change the path to those pages (so that I can for example use the View button, but also so that those "virtual pages" have a URL). In any case once page paths is installed it doesn't know that the paths are fake and being processed by a custom resolver, so they all got added to the page paths table and the PW thought they were real pages, so the went 404 and never reached the resolver; Took a while to figure that out; I only enabled it because it was required for the Verify Links module that i wanted to use.

Some amazing updates, the new video import feature is excellent.. testing this all out now!

update: those pages are now accessible, may have been a temporary issue. Will use this thread as a log for any future blocks.

Hopefully this can be solved; Almost every page: 403: https://processwire.com/talk/discover/content-started/ 403 https://processwire.com/talk/discover/unread/ 403 https://processwire.com/talk/discover/ i guess some type of blocker being overly aggressive, but this is false positive.

Thanks, i just built something similar! Great to have a lot of options.

@BigRed You could download the last version from here: https://github.com/trk/WireMailPHPMailer/releases Or if you upgraded using the upgrade module, then the old version would still be in your modules directory, with a dot. You can just delete the latest and undot the last one.

Edit - i just checked the modules directory and the repo still points to owzim, but it lists @horst as the owner. I'll continue to pursue the matter and see if we can get this module back in action.

I have forked it and updated it. https://github.com/outflux3/pw-inputfield-ace-extended I will put in a request to change the Github repo for the module to the newly forked version. Note that this inputfield is not compatible with the new ProcessWire UiKit admin theme, so you should be using the original theme when using Ace code editor.

if you are still using this module, one way to get around the aforementioned error is to copy the class into a new file (from the Fieldtype module) and then put this at the top of the inputfield module: if(!class_exists('ProcessWire\RuntimeMarkupUtilities')) { include_once __DIR__ . '/RuntimeMarkupUtilities.php'; } i haven't extensively tested it yet but so far it seems to work. I couldn't import any fields as the admin would crash and this has now allowed importing fields without this module showing the "class "RuntimeMarkupUtilities" does not exist error."

We had one site that was struggling under the strain of AI bots (the admin became almost unusable); The hosting support confirmed they were getting hit massively by AI bots. They ended up implementing apache level blocks. Then we had 2 other sites (running on Digital Ocean droplets) which started to get hit and were crashing, hitting 100% CPU. I have since installed WireRequestBlocker on those 2 sites (and had to up the memory, CPU and storage) On one of them we are now seeing a lot of activity, and IPs being blocked, and have been running smoothly since. In the meantime i'm trying out the ai.txt which can be generated here: https://site.spawning.ai/spawning-ai-txt Has anyone else tried it?

@pmichaelis thanks for the report. ok let me see if i can make this change and commit soon, might take a couple of days.

@gornycreative, thank you, very impressive and interesting to see how you set this up.

Yes - thank you 0.5.2 has resolved the issues.