ProcessWire 3.0.59, module updates and more

ProcessWire 3.0.59

Working from dev to master

The latest version of the core dev branch is 3.0.59, and this version brings us one step closer to the new master version. While there aren't any major new features in this version, it does continue with minor bug fixes, tweaks and documentation improvements, consistent with the latest couple of weekly versions.

A big thanks to those that have been helping to test and report issues on GitHub. While there are always things to tweak and adjust, there haven't been any major issues to arise thus far, so if that continues another week it may be that 3.0.60 could be our next master version–we'll have to see how it goes. If you've upgraded an existing installation to the current dev branch and everything works well, we'd like to hear from you too – perhaps just reply here if you get a chance. Thanks again for helping us to test.

Pro module updates

Several of the Pro modules have had new versions released this week. This includes the following:

For details on changes to each of these modules, see the dedicated support boards or changelog files included with each release. For the most part, there aren't major features to announce with these versions, but rather these are maintenance releases that are focused by fixing bugs and making optimizations. Note that new versions are typically released with a beta tag, which we remove a few weeks later.

New versions of ProCache and ProFields Table are also in progress and should be out as soon as this month. ProDrafts is receiving a major update, which is why it's taking a little longer than planned, but wanted to let you know progress continues there as well.

Working with PW and AWS

This last week I've been collaborating with Jan VandenHengel on moving moving several related mission critical ProcessWire installations to run on Amazon Web Services (AWS). You might remember Jan is the one that helped us with our hosting configuration last year and continues to help us maintain our web server. I know very little about AWS myself, but because these installations are moving to a redundant environment across multiple load balanced servers, my job is to make sure the ProcessWire core side of it works with scalable features provided by AWS that Jan sets up, in addition to getting everything upgraded.

These particular installations have been running ProcessWire for about 10 years, starting with ProcessWire 1.0 back around 2007, and working through the 2.x versions over the years. Though they are still running relatively old versions, with the newest being on 2.6. We're going to try and get them upgraded to the latest, along with updating them to serve assets via Amazon's CloudFront CDN with ProCache. Because the sites are quite large, and the upgrades are major, I'll likely be working on this with Jan for another couple of weeks.

I mention the above for a few reasons. It's a great opportunity to learn about ProcessWire in an environment I've not spent a lot of time with yet (AWS), and it may be an excellent case study opportunity for a future blog post here… I look forward to sharing what I learn. It may also reveal new opportunities for us to optimize for larger and larger scale with the core and with ProCache. Lastly, because I expect this to keep me a bit busy until we finish it, it may temporarily slow me down in other areas for a week or two, but luckily it's all about ProcessWire.

I hope that you all have a great weekend and remember to stop by the ProcessWire Weekly for the latest news and updates.


  • Nikolaus Rademacher

    Nikolaus Rademacher

    • 2 years ago
    • 60
    Hi Ryan,

    we are using PW in an AWS environment as well, so I would love to read about it in a future blog post. If our setting is interesting for you, I'm happy about any sparring.

    It would also be interesting to hear about best practices regarding deployment in cloud environments. One thing that could help sure is the page import/export I guess you mentioned in onr of your last posts.

    Anyway, I love to see ProcessWire evolve. Keep up the good work!


  • Pascal Raszyk

    Pascal Raszyk

    • 2 years ago
    • 40
    Sounds lovely,

    imho ProcessWire could really benefit from additional cloud hosting support for AWS and/or Azure and the like.

    I'm thinking about the following:

    - storing files and images in a AWS S3 Bucket especially when using cloudfront and procache together.

    - AWS lambda Integration for resource intensive tasks

    And as always, thank you for keeping this blog so interesting :)

  • Rudy Affandi

    Rudy Affandi

    • 2 years ago
    • 00
    Having PW assets served from Cloud/S3 without retaining a copy locally would be nice. It makes running PW on a load balancer an easier effort without having to worry about content replication.

Twitter updates

  • We added WebP image support this year and many have been adopting it in existing projects. We look at a process used for migrating existing websites to WebP images— from preliminary considerations to implementation & testing, w/lots of tips & tricks too: More
    16 August 2019
  • Core version 3.0.137 on the dev branch adds the ability to hook multiple methods at once, in a single call. This post details how it works and provides a useful example of how you might put it to use in your development environment— More
    2 August 2019
  • ProcessWire 3.0.136 updates our CKEditor version and adds a new backtrace() method to the core Debug class— More
    26 July 2019

Latest news

  • ProcessWire Weekly #275
    In the 275th issue of ProcessWire Weekly we're going to walk you through the new features included in ProcessWire 3.0.138, cover some WebP related stuff, and highlight recent forum posts and online resources. Read on! / 17 August 2019
  • WebP images on an existing site
    In this post we’ll look at a process used for migrating an existing website to use WebP images. We’ll cover everything from preliminary considerations to implementation and testing, with lots of tips and tricks along the way.
    Blog / 16 August 2019
  • Subscribe to weekly ProcessWire news

“We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH