Leaderboard

This week my kids are out of school on fall break, meaning I've also been off work this week (in part at least), so it's been a quiet week for development. Nevertheless, an issue report has been resolved (thanks to matjazpotocnik), two feature requests have been added (here and here), and a bunch of minor core code improvements have been added. While there's not much more to report this week, more is on the way next week. Have a great weekend!

In general: Apache servers are case sensitive. A request for /directory/file will be treated as a request for a different file than one for /Directory/File. Search engine’s are case sensitive. They’re going to view /directory/file and /Directory/File as the locations of two different documents In processwire: https://processwire.com/talk/topic/23223-allow-upper-case-in-url/ https://processwire.com/blog/posts/page-name-charset-utf8/

Hello everyone. I'm a relatively novice Processwire user so apologies if my query is easily resolved or if there have been previous posts. Can someone tell me why uppercase letters are not allowed in path names? Thanks in advance for your help.

This is just a general question really as I'm intrigued, but can't seem to figure out if it's possible. I have my own customer accounts using LoginRegister module. Now I could use custom customer form for confirmation, but currently I'm just rendering the in built customer form whilst I'm doing some development and I'm wondering if you can pass initial values to to order customer fields. In my case I could populate the billing and shipping fields with the customer who is logged in then. As I say, just intrigued if it's possible with the inbuilt form. Cheers

I wrote that last post on a Saturday and I needed to have the new site up and running on Monday, so I ended up just using .htaccess to separate traffic into en and pt subdirectories and PHP files to create the pages. Which works, but at some point I'd still like to figure out how to do this using Processwire. Additionally I realized that in some cases the page names were the same for the two languages, whereas in others they were not (e.g., map and mapa). So I would have needed to futz with that detail as well, which didn't seem insurmountable but was another example of "square peg != round hole." Since one of the main reasons that I wanted this site in PW was to allow others to make edits and it turns out that no one else has shown any interest in doing that, I'm putting this on the shelf for a while. Thanks very much for the suggestions and info!

Out of curiosity, which version of PW are you using? PW auto-corrects the rotation, and some issues related to this were fixed in version 3.0.197. Just wondering if updating to the latest stable version (3.0.200), for an example, would resolve this problem. My understanding is that PW doesn't remove EXIF data from uploaded image, just resized images — though I could be wrong here! One exception at least is that if you have configured a max image size for your image field, then it will be automatically resized after being uploaded, which means that PW no longer has any version of it with EXIF data in place. Anyway, I'm not sure which one you're talking about here: original uploaded image, or a PW generated size variation of it? If it's the latter, then currently there's no way to retain EXIF data, but the image should still be automatically rotated according to what was in said EXIF data. (There is an open issue about keeping EXIF data, at least in some cases, but no clear solution yet: https://github.com/processwire/processwire-issues/issues/1055.)

PHP is for me unfortunately something that does not come very inuitive (so, I guess you know now I am by no means a hardcore developer). So it´s always time consuming with lots of trial and error to find (forum, google) code snippets that do what I want to do. Since I started using LATTE thanks to this thread and thanks to @bernhard and his RockFrontend module, it seems like a gamechanger for me. Processwire has become extremly more usefull and inutitive for me since. Thank you! I am currently rebuilding my code templates I use as starter-kits for new projects and convert them to LATTE. Does anyone have and is willing to share a skeleton template to build a nav-tree menu (mulitlevel) with LATTE? Something that produces similar HTML code like this: <ul class='navbar-nav'> <li class='nav-item active'> <a href='/processwire/' class='nav-link'>Home</a> </li> <li class='nav-item dropdown'> <a href='/processwire/kontakt/' class='nav-link dropdown-toggle'>Kontakt</a> <ul class='dropdown-menu'> <li class='nav-item'> <a href='/processwire/kontakt/kontakt-unterseite-a/' class='dropdown-item'>Kontakt Unterseite A</a> </li> </ul> </li> <li class='nav-item'> <a href='/processwire/seite-b/' class='nav-link'>Seite B</a> </li> </ul>

I like a little bit of chaos personally. Can I stick a vote in for NTS Radio - they have a fantastic range of music.

This week we have ProcessWire 3.0.205 on the dev branch. Relative to 3.0.204, this includes 23 new commits including several refactored classes, issue resolutions, several pull requests and various new features. While there's no single major new feature to write a blog post around, there's still a lot here so for full details see the dev branch commit log. This week there's also a new module released in the ListerPro board called PageActionCrawl. This is a ListerPro PageAction module that crawls all pages sent to it. You can use this to crawl your entire site, some portion of pages within it, or even crawl external URLs referenced in URL fields. This is useful for any number of things such as priming caches, finding errors, quality assurance, doing security testing and more. Features include: Supports crawling with GET, POST or HEAD requests. Supports optional query strings and/or URL segments. Reports the HTTP response code and render time for each URL. Highlights error URLs (http code >= 400) in red. Optionally supports crawling of multiple URL variations per page. Supports inclusion of custom POST variables in POST requests. Supports page URLs or URLs stored in FieldtypeURL fields. Supports success and error hooks for custom behaviors on crawled URLs. Speaking of ListerPro actions, I've moved all of the 9 ListerPro action modules into their own new subforum of the ListerPro support board, so if you subscribe to ListerPro be sure to look for the new ListerPro Page Actions board in there. That's also where this new PageActionCrawl module is posted. Thanks for reading and have a great weekend!

Also related:

https://methodsanalytics.co.uk/ What makes this project cool: We integrated an impossible geometry concept using 3D, Three.JS - Shown in main concept and used for Error 404 concept. We allow the client to create impossible geomerty in the ProcessWire CMS. We created the 3D editor which loads in with a process module. Custom front-end design and UI and full content management across evey aspect of the site. Modular system for page content providing maximum flexibility on page construction. Health check feature looking for broken links and lorem ipsum, page scanning tool. SEO module with global editing section across all pages. Global shared content modules. Methods-Analytics.mp4

The ID of trash is 7, not 49. Depending on your need, you could do: $untrashedPages = $pages->find("template=some-template, status<" . Page::statusTrash); //$untrashedPages = $pages->find("template=some-template, has_parent!=7"); //$untrashedPages = $pages->find("template=some-template, has_parent!=" . $config->trashPageID); FYI, statusTrash = 8192