ProcessWire 3.0.97 core updates

This is an extra short blog post so that I can make a reasonably sized screenshot.

New on the dev branch this week is ProcessWire 3.0.97. The main difference between this version and 3.0.96 master is that 3.0.97 contains bug fixes for various minor things. There's nothing major here, so if you are already running 3.0.96 master without issue, it's perfectly fine to wait until this version hits the master branch. That'll likely be a week from now as version 3.0.98. But if you like to run on the dev branch with the latest version, then 3.0.97 is worth upgrading to, as always. At present, the master and dev branches are equally stable, and that'll likely be the case until we get back into adding-features mode.

Upcoming attractions

For whatever reason, the electricity (and internet) has been on and off today, so I'm going to keep this post short. But next week I'll have a post that covers version 3.0.98 (likely master) and also introduces a version of ProCache (3.1.8) with a new feature, buster. No I'm not calling you buster, I mean the feature is called “buster”, as in a browser cache, buster.

Over the next couple of weeks I plan to continue working on master branch updates, and then we'll get a closer look at recent PRs for inclusion on the dev branch. We'll take a break at version 3.0.100 (or thereabouts) to focus on redoing this website that you are reading now. We are long overdue for a new site, and we may need some of your skills and expertise too, we can talk more on that soon. But once we've got a new site, ProcessWire 3.1 will likely follow soon after. There's lots of good stuff on the way.

Thanks for reading! Have a great weekend and keep up-to-date at ProcessWire Weekly.

Comments

  • laikmosh

    laikmosh

    • 4 years ago
    • 00

    hello, im considering getting pro cache but i want to be sure it will work for me, curretly i use the built in $cache API like this:
    i make a loop of pages, inside the loop i try to get a chached version of this element like:
    $this Cache = $cache->get("markupName_$this->id");
    then if $thisCache exists i render that, if not I do the process to generate the markup inside an output buffer and then cache that
    later i create a hook to delete that cache when the page is edited/trashed

    my doubt id, when i see the ProCache API available at https://processwire.com/store/pro-cache/ i notice that pro cache data is linked to $page, while built in $cache is linked to a custom cache name, that means 1 cache per $page and probably means that each $page must have a template file, which i currently dont need, is there any way to take advantage od Pro Cache while keeping the flexibility of built in $cache?

 

PrevWhat to do after upgrading to the latest master

7

With everything running smoothly on the new master version, we wanted to recommend a few additional steps that will help you take advantage of some of the new features. Plus a look at developing for and with ProcessWire. More 

Twitter updates

  • New TinyMCE 6.2.0 Inputfield released for ProcessWire— More
    28 October 2022
  • This week we take a look at a new rich text editor for ProcessWire, why we chose it, some highlights, screenshots, and why we think you’ll like it— More
    21 October 2022
  • This week we have ProcessWire 3.0.206 on the dev branch and a new version of the ProDevTools UserActivity module, which we'll take a closer look at in this post— More
    7 October 2022

Latest news

  • ProcessWire Weekly #447
    In the 447th issue of ProcessWire Weekly we'll share the latest core updates, introduce a new third party module called RockVideoThumbnailGrabber, and more. Read on!
    Weekly.pw / 3 December 2022
  • New rich text editor for ProcessWire
    This week we take a look at a new rich text editor for ProcessWire, why we chose it, some highlights, screenshots, and why we think you’ll like it.
    Blog / 21 October 2022
  • Subscribe to weekly ProcessWire news

“The end client and designer love the ease at which they can update the website. Training beyond how to log in wasn’t even necessary since ProcessWire’s default interface is straightforward.” —Jonathan Lahijani