Leaderboard

This week I’m glad to report the development progress on the new ProcessWire.com website is ready for preview and I’ve placed it in a subdirectory for testing. You can find it here: https://processwire.com/newsite/ Of course, this is just version 1 of the new site, but it’s now got quite a bit more updated content than the existing site, so I don’t want to wait much longer to replace the existing site. I’m still working out a few small details, but it should be 99% functional. I expect to replace the existing main site early next week. If you have a chance to test it out, please let me know how if you come across anything that isn’t working or any browser/platform specific issues. Thanks for taking a look and testing it out. I’ll have more details next week, along with a new core version on the dev branch with several updates currently in progress. Have a great weekend!

That's very sad to hear.. I used to use Linux during my university days (15 years ago) because for computer science, it just made the most sense. Later, I used Windows mainly because I was forced to do so at work (in the past). So finally, I decided to again move away from Windows right about when Microsoft really added an unbearable amount of bloat and tracking bulls*** with Windows 10 and later on 11. I first went with Manjaro because I thought it was an easy introduction to the "Arch way" but that was a mistake: Manjaro is still very opinionated and does a few things which didn't work for me. So this isn't any different to just using Ubuntu with pacman. So I took the courage and went full Arch. Installation isn't too bad if you know your way around the command line. Since I was using WSL on Windows and used to run Linux for years before, this isn't a problem for me. I must say, I have never looked back. Arch isn't very plug-and-play, that's true. But also, it doesn't stand in your way. Back then, I even moved my work PC to Arch after a few weeks because I got very confident with using it at home. There also, I never looked back: Everything is just faster and especially when your machine is idling, it is actually not doing anything. Ever. Gone are random "jetplane takeoffs" and slowdowns (search indexing, updates, antivirus). Also, on my Laptop, the battery lasts forever longer than with Windows. Right now, I am using a simple GNOME desktop environment on top of Arch. I am using PHPStorm and Docker CE for local development. All of these are just a few package installs away. No need to mention that web development is just so much easier on Linux. For my work scenarios: Printers are basically plug-and-play with Linux (much more than Windows!). Same for SMB shares on the network. Microsoft 365 has 99% of it's features in their web apps these days (Outlook, SharePoint, Excel, Word, ...), even Teams works perfectly as long as you are not using Firefox. What am I missing? Basically nothing important! There are a few very small things. One example: We have a Miracast thing in the conference room to share our screens to which just doesn't work for Linux. No biggie, because there is also a HDMI cable 🙂

@bernhard I'll take a second look once I get past this deadline 😵‍ and report back with more info. The good news is that there's no error if I don't check that box, so it's not holding anything up 👍

thanks @bernhard for this module! it makes my code so much more organized & the content easier to maintain. but i am not able to setup an ajax endpoint: i get a 404 error in return. file lives in /site/templates/ajax/ i am logged in as a superuser. URL has no trailing slash. also the modules settings says: "No endpoints found." what am i doing wrong? PW 3.0.240, RockFrontend 3.21.2, RockPageBuilder 5.8.0

That's why I built RockLanguage. Yes, that means users have to install RockLanguage. I can't do anything about that unless the same functionality is in the core, which I'd prefer. But it's extremely light-weight and does not do any harm. https://github.com/baumrock/RockLanguage/blob/79bd3f996e3850361f2b41b149933a1a7bf20881/RockLanguage.module.php#L115-L121 Even if we had a way to export all CSV at once that would mean that every user using your module had to re-install translations whenever your module has new translations. Which is - again - tedious and time consuming. I simply don't like this approach and therefore will not build anything to support it. Imagine having 20 rock (or other) modules on a project (I often have more). Using CSV that would mean I'd have to install translations for 20 modules. Having 3 languages? Install 60 languages... Pulling updates for all modules? Install languages again... Using RockLanguage. Define the mapping once and you are done. I built RockLanguage because I think it's a far better workflow both for developers and for users. Thanks for trying it out and confirming that it works.

This week there’s new $pages->saveFields() and $page->saveFields() methods on the core dev branch. You might already be familiar with the $pages->saveField($page, $field); method which lets you save one field from a page, or $page->save($field); which does the same. This is useful when you only need to save one field from a page, rather than the entire page. Now we have a plural version of that method, which lets you specify multiple fields on a page to save: $pages->saveFields($page, [ 'title', 'body', 'summary' ]); Below is the same thing, but on a $page object, so you don't need to specify a $page argument: $page->saveFields([ 'title', 'body', 'summary' ]); You can also use a string if you prefer: $page->saveFields('title,body,summary'); In my case, I needed this method for a project I'm working on, and I also needed it to save without updating the 'modified' time or user, which you can achieve by specifying the 'quiet' argument. Though note, the 'quiet' argument is available for all the page saving methods and has been around a long time. But I'm not sure how widely used it is, so I'll mention it. $page->saveFields('title,body,summary', [ 'quiet' => true ]); This week the API methods for Select Options fields have also been updated to add more convenience for getting, adding and removing options to an existing selection. Let's say we have an Options field of checkboxes named "colors". Each selectable option has an ID, optional value, and title. Now you can get, add, or remove by any of those properties. Previously you had to work directly with SelectableOption instances, which wasn't as convenient. // add by title of option 'Blue' $page->colors->addByTitle('Blue'); // remove the option with value 'orange' from colors field $page->colors->removeByValue('orange'); // get SelectableOption instance of option with title 'Red' $red = $page->colors->getByTitle('Red'); echo "ID, value, title: $red->id, $red->value, $red->title"; // check if colors has an option with value 'purple' if($page->colors->hasValue('purple')) { // it has purple } The methods added to SelectableOptionArray (not yet reflected in linked docs page) include: getByID($id) getByValue($value) getByTitle($title) addByID($id) addByValue($value) addByTitle($title) removeByID($id) removeByValue($value) removeByTitle($title) That's all for this week. There likely won't be any core updates next week, as I'll be out of town again. Thanks for reading and I hope that you all have a great weekend and great week ahead.

RockFrontend v3.21.1 Several improvements in the docs Added support for nested AJAX Endpoints (see video below)

The concept of this module is indeed based on that in Drupal. If you have any suggestions or functionality requests, please feel free to let me know.

Looking good Ryan. One thing I noticed is the last dropdown menu "Docs" should open the same direction/way as the "Download" menu item but it doesn't. It opens off screen causing horizontal scrollbars. When viewing on Chrome. Edit: it looks like jmartsch beat me to it. Please consider giving the light grey and other muted text more contrast for accessibility. See https://contrastrebellion.com/ for humor. #666 for body copy gives AA, but #565656 gives AAA for example. Chrome's inspector now includes a contrast accessibility checker when you click on the color swatch/square. The curved line represents what passes the AA or AAA rating. After reading the API examples, I want to know more about it. I think we need a link or outlined button below the examples "Get started with the API" or "Learn more" so they can continue reading. Now that I look at it more, maybe each homepage section needs it own call to action button below. At first it wasn't entirely obvious that the headers on the homepage were links. Ex. Blog posts - might need a button below that say's "View all" or something similar. Same for the Processwire Showcase and Shop. - This might actually motivate new users to join the forums as well. Those are just a few of the first things that come to mind when viewing the site. Hope that helps