Leaderboard

This opens up so many possibilities for example for working with htmx or alpine.js. Thank you Ryan.

There hasn't been a lot of activity on the core this week, as I've been wrapped up in a ProcessWire-based client project (same one as last week). I'd like to put in a few more updates before bumping the version number, which will likely be next week. This week I also released a new module to accommodate a feature that had been requested more than once, but since it's not that commonly needed, I thought it was better to put it in a module rather than the core: Custom Inputfield Attributes for ProcessWire This module enhances both the interactive and API configurability of fields in ProcessWire (both admin and front-end). It can add custom attributes to Inputfields in ProcessWire, FormBuilder, or other Inputfield forms. Custom attributes can be configured interactively in the admin, or they can be added via this module’s API method. Custom attributes can be added to the <input> element of an Inputfield or they can be added to the wrapping .Inputfield element. You can add any attribute that you want (with a few exceptions), whether replacing or appending existing attributes, adding data-* attributes or any other named attribute. This module is available for download now on GitHub with more details on the module info page. Thanks for reading and have a great weekend!

before i can find this parse error, something funny is this knowing the there are two othr files in this same field, a rar and a pdf, this 404 error sounds really funny i'll test the same thing once on the domain instead of the subdomain (which is in the config.php file of course) but i hardly understand this error exclusively for this zip file... i've tried with another one and it worked filename of the guilty dossier-de-presse.zip - press-kit in french so no filename issue and dossier-de-presse.rar (same content) took a second to be uploaded) i'm wondering if it's a problem with the file content, images with very long names that pw tries to read when it can't in a rar, well, i should stop or i'm going to wonder if the earth is really rounded ??? have a nice end of day

@everyone (how annoying would it be if that actually worked...) If you've got a Github account and want to support ProcessWire and the community, why not go give this icon PR a ?? Great way to show the icon repo maintainers that there are people out there who love the platform. https://github.com/devicons/devicon/pull/1905 And while you're at it, go give the ProcessWire repo a ⭐ as well! https://github.com/processwire/processwire

Hello ngrmm I just found a workaround based on your input. class blogPost { const statusUnapproved = '16385'; } $page->addStatus(blogPost::statusUnapproved); if ($page->hasStatus(blogPost::statusUnapproved)) { echo "Unapproved"; } else { echo "Not Unapproved"; } Thank you for the help!

You can either provide the shortcut (works for DE and FI) or the full url to the zip file

Why don't you just put line 14-19 into /site/migrate.php ? Then you can run "php site/modules/RockMigrations/migrate.php"

If you are willing to use Rock Migrations 3rd party module, it has a special method for that.

@ryan Out of curiosity, and of it's possible to share publicly, were you working in something in particular in the PW admin where you needed to add custom attributes?

Hi @ryangorley! Not sure if you've taken at this old but still very relevant post: I'd say the best way is the one that fits your use case and in that sense ProcessWire has no rules about categorization. The tags can exist under their own parent separate from the "News > Blog Item 1" tree branch: /tags/tag-1 And be linked through the tags inputfield, it's pretty much the same case for categories. To my own personal taste I always tend to go with an structure like this: - ? News -- ? Tags ---- ? Tag 1 ---- ? Tag 2 -- ? Categories ---- ? Category 1 ---- ? Category 2 -- ? News Item 1 -- ? News Item 2 I like this because it keeps everything in the context of the "News" for the editors, and also the following URL structures which makes sense to me (not so sure about SEO but have had no complaints lol): /news/tags/tag-1 /news/categories/category-1 /news/news-item-1 The only part I'm not a huge fan of is that it requires a bit of code using hooks to keep the right sort underneath the "News" page, since the actual news items share a parent with the tag/categories parent, sorting the News children by published reversed, will (most likely) send the Tags and Categories to the bottom. But it ain't that big of a deal and if the problem arises to you I'll gladly share my solution. Also, to my own taste, I use a custom field for publish date, this lets me have more control over it and handle the visibility of the actual post with the hidden/unpublished status depending on what I want to achieve. Now for archive pages i'd suggest you take a look at what @ryan did in this old but also still relevant blog profile: https://github.com/ryancramerdesign/BlogProfile/blob/master/site-blog/templates/archives.php In all fairness this is not the clearest example and it's one of those part you'd expect to be built by default in a CMS, but I always think these details are worth the effort as a sacrifice for the flexibility PW gives you in terms of data structure/relation.

any news on that?

You have done it again. I need a feature for a site and there you go and add it. Have a good weekend Sir.

@ryan Can ProCache be refactored in such a way that SCSSPHP and the other compilers are optional extensions, along with the ability to define our own compilers (ie, DartSass and TailwindCSS CLI)? You mentioned something along those lines in a conversation we had in the ProCache forum and I think this would be a step in the right direction given how fast things in frontend web development move.

I'm quite sure you did, but just in case: Did you check if there is a plugin that can fix your issue?

Here are the step by step to install and setup ProcessWire with the help of a server management tool - https://cloudstick.io/ 1. Create your Vultr compute. 2. Select the Operating system Ubuntu 16.04/18.04/20.04 LTS >> Enter your server root password then click on Deploy now! 3. Create an account in CloudStick and connect your server: Click on connect server >> Enter your server login details >> Add this server. 4. Your server setup will be done in couple of minutes - The setup will finish less than 8 minutes. Then select your server: 5. Create an account to host/upload ProcessWire: Click on Accounts >> Create an account >> Create Custom Web application: 6. Enter the web application details, such as the email address which you would like to receive the SFTP login details >> web application name >> Domain name >> username then >> select the web application stack >> nginx + apache >> then create web application. 7. Now select the web application then install SSL: 8. Open your email account, and find the login details to connect the server over SFTP >> then upload the source code of ProcessWire: 9. Let us open the domain in browser once the upload finish. 10. Select the profile and click next: 11. Click next to proceed further: Now, you will see an incompatibility issue with PDO-Mysql which can be install in 2 clicks. 12. Go back to the summary page >> Click on easy PHP >> Select the PHP version of your web account: 13. Then it is time to enable PDO_Mysql, scroll down and enable it: 14. Go back to to the ProcessWire installation URL and click on check again >> You can see no incompatibility issue after enabling PDO_Mysql: 15. Click on Next and now it is time to enter the database credentials: 16. let us create the database, db user and grant privilege's to the db user - it is just matter of few clicks and very easy! Click on the menu Accounts >> Select your web account of ProcessWire >> Click on App Database then create the a database: 17: Click on create database and enter the database name: 18. Create the database user: 19: Go back to the database page and click on Grant user then grant permission: 20. Go back to the ProcessWire installation URL and enter the database credentials you have created in CloudStick dashboard. Now, it is time to setup your admin user credentials and setup admin area URL: 21. Then you are done: