This week we've got a really nice improvement to ProcessWire's page tree, something that I believe everyone that uses the ProcessWire admin will appreciate. Also a big focus this week was on ProDrafts and wrapping that up so that we can release it and make it available to you. More on both of these below!
ProDrafts is a module I've had in development for quite some time. It enables you to maintain separate live and draft versions of any page. The draft version can be manipulated, viewed and compared separately from the live version.
While ProcessWire itself can provide drafts of unpublished pages, ProDrafts can provide drafts of published pages, enabling you to make as many edits as you'd like before deciding to publish them to the live version of the page. This also enables greater workflow possibilities as it's now possible to have users propose edits to pages, while someone else can approve them.
Once things really got going with ProcessWire 3.0, I took my focus off of ProDrafts for a bit to dedicate as much focus as possible to PW3. Especially since some things in PW3 could affect our approach in ProDrafts. But now that I think PW3 is really getting pretty solid, I'm back on ProDrafts and spent the last week working to wrap things up. In fact, so much progress was made this week that I think we'll be ready for our first beta release next week, and I'm very excited about that.
In the interest of releasing it sooner rather than later, I decided to scale back the plans for version 1 and make it focus exclusively on drafts (per the original intention, rather than both drafts and versions). Versions will still be coming in the next version, and actually all the code to manage them is already present in ProDrafts. But they are disabled in version 1 since I feel the versions feature is more "alpha" state, while the drafts feature is more "beta" state. I'm comfortable releasing a Pro module initially in a beta state, but not in an alpha state. I didn't want the versions feature to hold things up, since most are more interested in the drafts feature. So the versions feature will be delayed for a bit while I do further testing and development to work out any possible kinks. Though it should be noted that even at present, the versions feature works quite well, so it's really not far off.
Like we've done with the initial beta release of most Pro modules, the price of ProDrafts will be discounted with a coupon code until we are officially out of beta and/or have the versions feature ready. We will likely use a pricing model similar to ProFields since we think ProDrafts is one of those modules you'll likely want to use on many sites you work with, unlike modules like FormBuilder that you might only need for 1 site at a time. If your experience is the same as mine, once you start using ProDrafts, you'll find you want it in a lot of places.
This week's ProcessWire version is 3.0.8 and introduces a really useful addition to our page list / page tree. The concept is simple. Wherever you last left the page tree is where it will be when you return to it.
What this means is that if you've drilled down to several pages in your page list (thus making them "open" in the tree), they will remain open until closed… regardless of where else you navigate to in the meantime. You will never lose your spot, nor do you have to wait for the tree to load. Simply click the "Pages" tab and you will immediately return to where you left.
You might be familiar with the concept of pre-opened pages already, as it's essentially the behavior you get if you click a breadcrumb item at the top of the page editor. But there's actually a big difference here too, in that there is no more waiting for the page tree to open each page. It now does it all in one shot... no more multiple-ajax calls to render an opened tree. Meaning, no more waiting to get to where you want to go. This is the case regardless of whether you click a breadcrumb in the page editor, or click the "Pages" tab in your admin.
Some of you with lots of pages in your site are aware that when it comes to pagination in the page tree, there has never been an easy way to return to the spot where you left it. If you had edited a page on the 50th pagination of a page list, then you could get back relatively easily to the parent, but would still have to navigate through all the pagination to get back to where you were.
That's all changed in ProcessWire 3.0.8. The smarter page tree remembers your last pagination too:
I've been using this update locally for the last couple of days and think it's such a nice improvement that I'd never want to go without again. I'm interested to hear what you think too. That's all for this week. Hope you all have a great weekend and remember to read the ProcessWire Weekly.
This week we have another new ProcessWire 3.x version for you that includes several updates and optimizations. We've also greatly expanded upon the field rendering with template files, with lots of info covered in this post. More
This week's version of ProcessWire adds several new UI enhancements to the admin. We also have a new version of ProDrafts, now with Live Preview! More
“Indeed, if ProcessWire can be considered as a CMS in its own right, it also offers all the advantages of a CMF (Content Management Framework). Unlike other solutions, the programmer is not forced to follow the proposed model and can integrate his/her ways of doing things.” —Guy Verville, Spiria Digital Inc.
Sevarf2
- 9 years ago
- 100
★★★★★This tree update rocks. I run several websites with paginated tree and this is a really big improvement!
Reply
Yannick Albert
Opened an issue on GitHub https://github.com/ryancramerdesign/ProcessWire/issues/1749
Reply
Adrian
Cool additions to the Page Tree - just wondering if it might be nice to have a way to actually collapse everything back up though.
I can see it becoming messy on some sites where you have delved deeply and just want to close everything up.
What about if clicking Home twice would collapse everything? The first click would actually collapse all branches, and when you click again, it would open with just the top level parents open - like the default view. Or something like that?
Reply
Adrian
Just wanted to thank you for adding the ability to collapse the tree via the Home button in PW 3.0.13 - https://processwire.com/blog/posts/processwire-3.0.13-selector-upgrades-and-new-form-builder-version/#option-to-collapse-pagelist-tree
Reply
thetuningspoon
Great enhancements! This will definitely be a major workflow improvement, and something I've been wishing for for a while. Thanks Ryan!
Reply