Leaderboard

https://github.com/processwire/processwire/archive/refs/tags/3.0.123.zip

I have found the issue: This only happens if the ID and name attribute are exactly the same on a single upload field. If there is a difference, everything works as expected, so I have added an additional suffix to the ID attribute of a file upload field to prevent this behavior. display-change.MP4 Now everything should work fine! Module version is updated, so please test if everything works now as expected.

@BFD Calendar Make sure you've got /site/config.php setting $config->debug = true; just so you can see errors. You may want to set it so that it's only in debug mode for your IP address, i.e. $config->debug = $_SERVER['REMOTE_ADDR'] === '123.123.123.123'; Keep an eye on the files in /site/assets/logs/, especially errors.txt. If you have shell access, you can "tail errors.txt" in that directory to see what the latest error messages are. You don't need to be able to login to the admin to view these logs, you can just locate them on the file system. Most of the time they will reveal whatever the issue is. If it's not clear, then post the last few log entries here to see if we can identify anything from it. The errors you mentioned may be expected, as it looks like they are trying to access something related to cgi-bin or a .well-known file, which are specific to your hosting and not to ProcessWire. So if your host blocks those addresses, then you'd expect to see this in the apache error log. Basically, I don't think those error messages are related to whatever is preventing your site from running.

Had a similar nightmare today. Nothing to do with PW itself. Some files were corrupted during upload to the site. Fix was to do a manual PW upgrade, ie: rename wire dir to .wire-3.0.xxx (whatever version) and do the same for index.php upload clean wire directory and index.php To be on the safe side, I also re-uploaded site files I knew were clean Everything then worked 100% as expected. Hope this helps

Thanks to both of you. I did not see the custom paths module. This may work indeed, I will test it, as this is fortunately not a multi-lingual site. And yes, the name property is an option, I could rewrite the navigation module. But knowing the client, I am sure he will want exception for this flat url approach.

Hi, well actually, as when displaying breadcrums i use <?php foreach($page->parents() as $parent): ?> i think that while looping through the parents array, something like <?php foreach($page->parents() as $pid => $parent) { $position = $pid + 1; //except if you want your position starting by 0 } ?> would do the job $pid being different from $parent->id of course hope it may help 🙂 have a nice day

Good luck to the Craft team, but to me it looks like they need to reinvent the wheel every now and then. Luckily, we have our own genius, Ryan, who figured that reinventing the wheel is not for everyone. At least not for us ;)

It will be a BIG mistake if we make Processwire a commercial platform No it won´t. Opensource with paid support and paid modules/forms/templates etc. works perfectly. Providing paid professional support, modules, templates, etc. etc raises respect and attracts different clients. Commerical modules for who? Shops, pro seo, pro templates, billing systems, order tracking, renting, bookings, real estate, etc. etc. It´s a big world out there. Also check processwire jobs => https://processwire.com/talk/forum/22-jobs/ Let's take Linux, is the BEST operating system and is free, there is a small fee for support but that's all. Ever seen the linux support from red hat, oracle, ibm, ubuntu etc. ? And let's organize a Donation online event, Donating doesn´t work, I will spare you the reason why. We should thank Ryan and his coding team for releasing processwire with the level as it is today for free. I would go for this: Leave it for free for what it is today but: a) paid future upgrades to the core b) paid pro modules/forms/templates/etc. c) paid support

When a client asks for "a website" with "easy management", explaining that ProcessWire is "an awesome framework for building just about anything" feels plain wrong and is unlikely to yield desired results. On the other hand, when client (or fellow developer) does mention the need for "an application", "framework" or "software platform", it's good to be able to match those needs too. Personally I really like the fact that ProcessWire has the ability to be both and would like to avoid emphasizing either *too much* over the other. If I needed a CMS, there would be a huge amount of other options available, and if I simply wanted to build an application I could (for an example) turn to Zend Framework and get the job done.. and so on. What ProcessWire brings into this equation is a well-balanced combination of features from both worlds. Each part supports the other, eventually making it more than the sum of it's parts. I especially love how easy and fast built-in admin makes mocking up data structures -- in fact it's such a smooth experience that the times I've built mock data manually for HTML wireframes etc. have been almost nonexistent lately. I find it faster to make fully functional features using ProcessWire than writing dummy directly with editor. And that, in my opinion, is why it's so damn good. Not that I really needed to explain it to anyone here, but my point is mostly that I don't see ProcessWire simply as a CMF or CMS or application framework or whatever. It's all of these combined.. and that's a good thing. I hope we don't get stuck discussing which one it is when that question can't (and shouldn't) have one single correct answer