Leaderboard

Good question. Actually, yesterday I started to consider getting the 20-core GPU version (the most expensive one), but only if I decide to get into 3D seriously once and for all. I'm giving myself some time to think about that, as it would mean a lot less web development work, which I love with ProcessWire. As long as Ryan is around, I don’t think I will ever leave PW, but if I switch my main focus, then obviously I won't have as much time to work on ProcessWire-based projects. As for web development, I am pretty sure that even the cheapest M4 Mac mini would be just fine. My daughter's original base model M1 MacBook Air is at least twice as performant as my current 2019 Intel MacBook Pro in almost all respects, and the latter is still perfectly fine for DTP and web development. So why spend the extra money on features I do not use? However, I still want to replace my current Intel Mac, as I would like to make more homemade videos from our family footage recorded over the years, and any M series Mac is a lot better for that than my aging Intel CPU based laptop.

For years I have had a hop-on/hop-off relationship between Windows and Linux. I am not and was not a Windows guy, coming from then SGIs desktops and their GUI. in the meantime I've had years of different hardware with many Linux distros (from Slackware, Debian to Suse to RedHat, Mint and many more), but also the very consistent OpenBSD and FreeBSD also as a desktop. With all these unixoids, I kept missing some of the necessary, even proprietary software, for school or my business, for which I had to run on a separate Windows box then becasue of hardware dongles. VM was not a seamless solution. The desktop applications and VMs of unixoid OSes are good, stable and fast today, hardware support is also good. But I had the feeling that it was often only about being able to configure everything, down to the last window, and often only to use an OS without software costs. That's good, but at some point I didn't liked configuring and system administration any more. I simply wanted a system that gave me a good GUI with a unixoid shell, basically a modern BeOS/Haiku OS. Then bought a mac, a macbook, then an imac. After that I tried it out again with a Win10 box. I didn't work quite as smoothly as with macos, but it also progressed. Hardware crashes with an AMD processor and a popular collaboration suite were difficult to solve as a lecturer during the pandemic. I solved this with a quick buy of a mac mini m1 and it still runs around with sensationally low power consumption (max. 36W). Almost green;-) And now 4 hardware steps further, lets see. Mac is not that only alternative, but it is also a usable one.

Here's my next ProcessWire build. After dipping my toe in the ProcessWater with a simple holding page ( https://www.threehills.farm/ ) followed by a blog ( https://www.eltikon.online/ ) that I shared here, this time I have focussed on a site that uses the Repeater Matrix to manage blocks of content, in order to see how easy it is to transfer my WordPress "Advanced Custom Fields Flexible Content" approach to ProcessWire. Result: it's really easy once you get the hang of it. Site: https://www.zigpress.com/ This is my business site, and is a single-page site (plus 404 etc) where each section of content is managed in a Repeater Matrix. Modules installed: AdminStyleRock (so I can use my Nord admin stylesheet!), Pro Fields Repeater Matrix, Seo Maestro, FrontendForms, Less, Redirects, my own ZP Traffic module, and Wire Mail SMTP. I also included Perishable Press's 7G Firewall. I still have more testing to do now that it's live, but it seems to be behaving OK so far. All feedback welcome, including criticism/bugs/whatever.

Three of my favorites are: Vivaldi - Four seasons This one Enigma (older) Or even chill from Hozuki:

Hi, the simplest way i can think about would be to create a role (named editor for example) to which you only give a few peremissions, you'll end with this kind of admin menu adding only those permissions juste an example of what can be done in the adminknowing onluy super user, say... you 😂 have the setup/module/access menus in case it helps have a nice day

The interesting part is actually steps 1 and 2. Step 3 is just a check by the user that all the data entered is correct Step 4 is the confirmation that the information has been saved. I have created a small mockup here, I think you can see what the form does.

Hey @zoeck thx for your question! Sure 🙂 RockCommerce is built like ProcessWire. You have several modules that help you build what you need, but you need to put your pieces together yourself. That means more work upfront, but you can build exactly what you need. Just like building a website with ProcessWire - you don't need pagination? Don't add it to your site... You don't need payment? Just don't add that step to RockCommerce. But it sounds like the product and cart functionality plus the (multi-step) checkout via RockForms could save you a ton of time already. Nonetheless please be sure to check the minimum requirements in terms of all possible features like shipping, variations, stock keeping etc. and check if RockCommerce supports all that (yet). BTW: We'll launch my first real-world RockCommerce project today 😍🔥 I'll then try to work on the docs to make it as easy to understand and use as possible! Official launch should then be end of November. If you need something earlier let me know. Hey @Sanyaissues that looks great! Didn't even think to display the cart side by side with the products but great to see that you are able to use the module in your own way!! 🙂

Yeah, that would be nice to have for sure. Since all M4 Mac Minis come with 16-core Neural Engine cores, I guess* they will be equal in this regard. Checking out M3 Mac reviews available out there might help you determine which M4 chip variant can be good enough for running local LLMs. *Edit: I could be mistaken, and other cores are also important to have. Having an Intel CPU based Mac, I have not yet dived into this topic just yet.

I see, thanks. In my case, the consideration is mainly if it can run an LLM locally without 'much fuss'.

Hello Bernhard, I have a question about RockCommerce. I think I actually need exactly the possibilities that RockCommerce offers, i.e. ordering items and offering a price with information etc. But the customer should not pay for it. That sounds strange, but I would like to use the shop for an internal self-service portal 😉 Is that possible?

With the new version everything works again, thank you @bernhard 🙂

@bernhard I was aware of RockForms' existence but just by name, but never took the time to read more about it. I just finished reading the docs, and man, that module is a beast! hats off!

When you’re feeling lost and already halfway to uncharted waters, there’s only one man to call: The Captain Hook.

M4 Pro beyond your budget or you have no need for the beast?

Congrats @DrewPH!! Now you will need to ask your clients to update the feedback comments so people can know you are one of the best wordpress ProcessWire developers in Malta.

Playing with the new toy! 🚀👕 Screen recording 2024-10-29 15.50.20.webm

wire()->addHookBefore("InputfieldFile::renderItem", function(HookEvent $event) { $pagefile = $event->argumentsByName('pagefile'); if ($pagefile->field->name === 'yourFileField') { $pagefile->description = 'Communiqué de presse'; $pagefile->page->save($pagefile->field->name); } }); Try this @TomPich.

Hehe, ProcessWire Weekly #546 RSS just dropped into my Reeder app and it seems ZigPress is site of the week! 😊 I'm extremely flattered and honestly quite surprised considering the high standard of sites in the showcase... thanks to whoever made the choice.

The PW forum is a place of the most friendly and helpful people I ever interacted with in web based CMS/CMF forums so far. What I learned from other forums is, that showing as much code you already tried (e.g. I put this code xxx into /site/templates/myfile.php) and asking a single question closely related to your code example (e.g. I expected to get x, but instead I see y) would help all involved people to better grasp each others standpoint and to provide better replies to specific questions. Cheers cwsoft

Lets see if we can get a quick-start tutorial going here. We'll start with something really simple and then work up from there. Tell me when something makes sense and when it doesn't and we'll adjust as we go. My thought is that we'd make a tutorial that plays on the 'hello world' phrase and lists information about planets in the solar system, starting with Earth. To keep it simple, we'll assume that the basic site profile is installed, as that's what comes with ProcessWire (so there's no need to uninstall anything). But we won't start using any of it's files tat this stage. Instead, we'll start out by creating our own files. STEP 1 – Create a template file Create a new file called: /site/templates/planet.php, and copy+paste the following HTML into that file: <html> <head> <title>Earth</title> </head> <body> <h1>Earth</h1> <h2>Type: Happy planet, Age: Millions of years</h2> <p>Earth (or the Earth) is the third planet from the Sun, and the densest and fifth-largest of the eight planets in the Solar System. It is also the largest of the Solar System's four terrestrial planets. It is sometimes referred to as the World, the Blue Planet, or by its Latin name, Terra.</p> </body> </html> The above is just a plain HTML file with nothing specific to ProcessWire. We will use this as the starting point for our template, and we'll go back and modify it later. STEP 2 – Add a template to ProcessWire Login to ProcessWire admin and go to Setup > Templates. This page shows a list of templates currently in the system. Click the Add New Template button. On the next screen that appears, you'll see it found your "planet" template file. Check the box next to the planet template and click Add Template. You may ignore any other options that appear on this screen. STEP 3 – Creating a page using your template Your planet template is now in the system and ready to use, but it's not being used by any pages. So lets create a page that uses the planet template. In the ProcessWire admin, click Pages in the top navigation. This is a site map if your page structure. We want to create a new page under the homepage, so click the new link that appears to the right of the home page. The next screen has 3 inputs: title, name and template. Enter "Earth" for the title, and the name should populate automatically. For the template, select planet. Then click Save. Now you have created a new page using the template that you added. You are now in the page edit screen and you should see your title field populated with "Earth". Click the View link that appears on this page edit screen. You should see the output of the HTML from step 1. Click the back button in your browser to return to the edit screen. STEP 4 – Creating a new field Now you know how to create a template and a page using that template. You could create more pages using the same template if you wanted to. But that wouldn't be particularly useful – this template file is just a static HTML file. Lets make it dynamic by creating some fields and adding them to it. We are going to create 3 fields to represent the pieces of data that currently appear in our static template. These include the planet's type, age in years, and a brief summary. We will call these fields: planet_type, planet_age and planet_summary. In ProcessWire admin, click Setup > Fields. This screen shows a list of fields currently in the system, most of which are general purpose fields for the basic profile. For the purposes of this tutorial, we are going to ignore those and create our own. Click the Add New Field button. On the next screen, enter "planet_type" for the Name, select "text" as the Type, and enter "Planet Type" for the Label. Then click the Save Field button. Now that your field is saved, you are on the Field Edit screen. At this point, your field is created and ready to be added to your planet template. Optional: While editing your field, click the details tab where you'll see a select box for Text Formatters. Select "HTML Entity Encoder" – this ensures that characters like "<", ">" and "&" will be converted to HTML entities and not confused as HTML tags. While not required, it's a good practice for text fields like this. After you've done that, click the Save Field button. STEP 5 – Creating more new fields In step 4 we created the planet_type field. Now we want to create the planet_age and planet_summary fields. So in this step, you'll want to do the same thing for the remaining two fields: Create the planet_age field exactly like you created the planet_type field, but enter "Planet age in years" for the label. Create the planet_summary field exactly like you created the planet_type field, but chose "textarea" as the Type and enter "Planet summary" for the label. Note that a "textarea" field is just like a "text" field, except that it can contain multiple lines of text. STEP 6 – Adding new fields to your template Now that you've created 3 new fields, you need to add them to your planet template. In ProcessWire admin, click Setup > Templates > planet. You are now editing your planet template. In the Fields select box, choose planet_type, then planet_age, then planet_summary. You will see each added to the list. Cick the Save Template button. STEP 7 – Editing a page using your template Now that you have new fields added to your template, go back and edit the Earth page you created earlier and populate the new fields that are on it. In ProcessWire admin, click Pages at the top, then click the Earth page, and click the edit button that appears to the right of it. You are now editing the Earth page you created earlier. You should see the new fields you added, waiting for text. Enter "Terrestrial planet" for Planet Type Enter "4.54 billion" for Planet Age in Years Paste in the text below for Planet Summary and then click Save. STEP 8 – Outputting dynamic data in your template file While still in the page editor from step 7, click the "View" link to see your page. Note that it still says "Happy planet" for type (rather than "Terrestrial planet") and "Millions of years" rather than "4.54 billion years". That's because the page is still being rendered with just the static data in it. We need to update the template file so that it recognizes the fields we added and outputs the values of those fields. Edit /site/templates/planet.php and replace the static text in there with tags like this, replacing field_name with the name of the field: <?php echo $page->field_name; ?> If supported by your server, you may also use this shorter format which some people find easier to look at and faster to enter: <?=$page->field_name?> Here is the /site/templates/planet.php file updated to output the content of the page using tags like the above: <html> <head> <title><?php echo $page->title; ?></title> </head> <body> <h1><?php echo $page->title; ?></h1> <h2>Type: <?php echo $page->planet_type; ?>, Age: <?php echo $page->planet_age; ?> years</h2> <p><?php echo $page->planet_summary; ?></p> </body> </html> After making these changes, save your planet.php template file. Now view your Earth page again. You should see it properly outputting all of the content you entered on the page, including "Terrestrial planet" for Type and "4.54 billion years" for age. Any changes you make from this point forward should be reflected in the output. STEP 9 – Creating more pages, reusing your template For this last step, we'll create another page (for Jupiter) using the same template just to demonstrate how a template may be reused. In ProcessWire Admin, click Pages and then click the new link to the right of the home page. Enter "Jupiter" as the Title and select "planet" for the Template. Click Save. Now that you are editing the Jupiter page, enter "Gas giant" for Type, enter "4.5 billion" for Age in Years, and copy+paste the following for Planet Summary: Click the Publish button and then View the page. You should now see your planet template being used to output the information for Jupiter rather than Earth. CONCLUSION In the above, we covered the basics of how to develop in ProcessWire, including the following: Creating templates and their associated template files Creating basic text fields and adding them to templates Creating and editing pages that use your templates Outputting the values of fields in template files If all of this makes sense so far, I thought we'd follow up next with a tutorial to take this further: Adding and outputting photos for each planet Creating navigation that lists all the other planets that have pages in the system …and we'd keep building upon the tutorial from there. If you all think this tutorial is helpful, then perhaps this can be a draft for a real tutorial we'll put on the site, so all of your help is appreciated in making this as good as it can be.