wbmnfktr

Well... what's your setup? Laragon on Windows works perfectly fine without issues like that. MAMP on Mac in most cases as well - as far as I know. Managed servers (root, vServer, Cloud Server) should in most cases be fine as well. At least at good hosting companies. Local Debian/Ubuntu servers with a LAMP stack need only a few tweaks to work perfectly fine. So... depending on what you use you either want to ask your hosting company or login via SSH to enable mod_rewrite or look into your Laragon/MAMP config. Maybe you have to enable an option or two there (which I really doubt actually).

You're welcome! I wish I could help more.

I don't know if this could be the reason. I know that there is one project - I maintain - with a Cloudflare -> Nginx -> Apache setup. Maybe I'll find the time to play around with it on the weekend. For the moment... ¯\_(ツ)_/¯

Kind of... Works with some automation pretty nice and easy.

That's wild... why is there such a different behaviour? Nonetheless... it's working now. ?

Good advice. For the record: In my testing site namespace wasn't set. Just added it. Works the same. No difference.

3.0.140 works fine in this case. Just tested it here with wire404Exception(). PageNotFoundException() doesn't work - tested that as well. Can you please doublecheck $catPage. Maybe... I don't know... there is a glitch.

The 3.0.140 brought some issues with 3rd party modules and I try to avoid the DEV version at the moment for that reason. Therefore this was just a guess but maybe the DEV version also affects core features like this. Try the latest Master (3.0.123) if possible. If that's the fix we have found the suspect. By now your code snippet seems fine to me - at least the modified (other if statements and Wire404Exception) version works as expected here.

So... I just played with it a bit. Does NOT work: throw new PageNotFoundException(); Does Work: throw new Wire404Exception(); Tested it on a ProcessWire 3.0.133 installation. Are you maybe running the DEV 3.0.140 version?

You use PageNotFoundException() while I only know and see Wire404Exception() in examples. Does it make any difference? Additional sidenote: Very old (2010 and 2013) thread but still... interesting.

Have you seen this tutorial/guide? https://processwire.com/docs/front-end/how-to-use-url-segments/#best-practices

I get paid by the hours so... oh wait. ? Good to hear it worked for you! ?

Whenever I had issues with databases in Laragon I re-used a database name. Means... I deleted a database, created a new one with the exact same name and afterwards I ended up in things like that. Maybe it was the reason here as well.

At this point I'd like to open this issue to someone who is way more into hooks and custom functionality than I am. Maybe @bernhard or @adrian or @szabesz or @dragan ... they know a lot more about hooks and ProcessWire than I do. They will have a solution for this.

Broken records were source of so many great samples in modern music. Just sayin'. ?

Nothing is shared yet but will (hopefully) come very soon. Some insights can already be seen over at github. The client itself still exists but that business alliance for restaurants (my client, a friend of him and a 3rd party) didn't match that well so they stopped it almost right after the start. Let's see if it will be a cool profile. As stated above it's almost only data management with some nice additions. There will be no frontend that tries to be a theme or anything like that. Nonetheless... sharing seems to be the best option here. Or at least a nice option.

Hard to tell for me as well. Maybe you could post some of your code here and tell us more about the overall setup. And details like ProcessWire version, the hook(s) you use, where they are placed (ready.php, a module, ...). That would help us to give more help and tips.

First of all I'd test it without mandatory fields (first, middle, last name) to ensure everything else is working as expected. If that's the case I'd start with one mandatory field to check it's behaviour. Never done a similar thing in the past - so it's just a recommendation or workflow I'd try.

Where do these pages come from? Their names are either randomly generated or as I assume created by a module - maybe even a repeater or pageTable field. Is your user a administrator/super user? Who deleted those pages/put them in trash? How did they end there? Manually deleting, API or module? Are these pages somehow locked? (can be seen in their settings tab) What templates do these pages use? Are these templates somehow special?

I stumbled across this solution a few times. There is/was a bug in CKeditor which affected those multiple class setups.

?????

Try adding the classes in alphabetical order. { name: 'Left Aligned Photo', element: 'img', attributes: { 'class': 'float-md-left img-fluid' } }, { name: 'Right Aligned Photo', element: 'img', attributes: { 'class': 'float-md-right img-fluid' } }, { name: 'Centered Photo', element: 'img', attributes: { 'class': 'img-fluid w-100' } },

Or this https://modules.processwire.com/modules/pagefield-pairs/

// Source: https://processwire.com/talk/topic/3553-handling-categories-on-a-product-catalogue/?do=findComment&comment=37833 $manufacturers = new PageArray(); foreach($pages->findMany("template=carTemplate") as $car) { // add manufacturer from car page to manufacturers array $manufacturers->add($car->manufacturerField); }; // do whatever you want with the $manufacturers pages Something like this?

I guess it's still too early for an issue response on Github. Let's compare the things we can compare: ProcessWire 3.0.132 PHP 7.2 Cloudflare Free Plan (default settings) webP Strategy 1 htaccess: non-www Redirect htaccess: https Redirect pagefileExtendedPaths NOT set As you don't have access to the Cloudflare settings... is there someone who can look into it? Maybe they use a load balancer, built in whatever. Maybe the site is still cached. Cloudflare CDN is sometimes bit of a PITA. Dev-Mode or DNS-by-pass would be nice to test out. Maybe there are even custom page rules that are image related. There is a lot of stuff someone can do there.