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

    • 3 months 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

  • ProcessWire 3.0.133 adds a useful new Page::meta() method for a new type of page-specific persistent data storage, adds the ability for users to create their own bookmarks in Lister, and has a handy and time saving update for the asmSelect input type— More
    14 June 2019
  • New post: This week we’ll take a look at 3 different WEBP image strategies that you can use in ProcessWire 3.0.132+. Then we’ll dive into a major update for the Google Client API module, and finish up by outlining some useful new updates in FormBuilder— More
    31 May 2019
  • New post: This week we've added WEBP support in ProcessWire thanks to a GitHub pull request from Horst Nogajski. This enables you to have highly optimized image output in PW and I think you’ll really like the difference it makes— More
    24 May 2019

Latest news

  • ProcessWire Weekly #266
    In the 266th issue of ProcessWire Weekly we're going to take a closer look at ProcessWire 3.0.133 (dev), introduce a third party module called Repeater Images, and highlight a recently released site belonging to the Australian Antarctic Division. Read on!
    Weekly.pw / 15 June 2019
  • ProcessWire 3.0.133 core updates
    ProcessWire 3.0.133 adds a useful new $page->meta() method for a new type of page-specific persistent data storage, adds the ability for users to create their own bookmarks in Lister, and has a handy and time saving update for the asmSelect input type. Read on for all the details, examples and screenshots.
    Blog / 14 June 2019
  • 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