Blog

Pods 2.5 Is Here: Full Of Bug Fixes and Optimizations

pods_circle_only_dark_bg_1200x1200Today we released Pods 2.5 on WordPress.org. This release encompasses a large number of bug fixes and performance updates from the Pods team and Pods community. This release introduces no new features, it is simply less buggy and more performant than Pods 2.5. The new version, which is fully tested with WordPress 4.1, is available via our WordPress.org page and the plugin admin in the WordPress dashboard.

This release has been extensively tested, and is our first to be developed using our unit testing suite. We now have 1,858 tests with a total of 13,420 assertions covering every combination of content type and field that we could imagine with relationships multiple levels deep. As always we encourage bug reports, and feature requests, as well as pull requests at our Github repository.

The Pods team would like to extend a special thanks to a volunteer contributor James Golovich, who was a major contributor to this release and led the optimizations that have dramatically improved the performance of Pods. We’d also like to welcome newcomer Nikhil Vimal, whom you may recognize from elsewhere in the WordPress community.

For a full breakdown of the changes, please see the changelog.

6 thoughts on “Pods 2.5 Is Here: Full Of Bug Fixes and Optimizations”

  1. If anyone is wondering about Pods 3.0, I thought I’d add a quick note here that we’re still going forward with it. It includes loop fields and CMB2 has already been integrated into the build I’m working on. Pods 2.5 was primarily the result of other developers and contributors, while I’ve kept my continued focus on Pods 3.0. So props to the team for helping make it happen while my eyes are elsewhere!

  2. Oh, also, @sc0ttkclark I’m really excited for 3.0! Will it be a direct upgrade or will there be some migration work that will need to be done to implement 3.0 into current projects?

    • There are no migrations or code changes. However, if you are calling Pods classes manually, you will need to follow the new Pods_ABC format instead of PodsABC for class names. We have backwards compatibility here already though, so you shouldn’t be penalized much (in performance) by old code left around.

Comments are closed.