We are releasing Pods 2.6.5.2 (along with 2.6.5.1 overnight and 2.6.5 yesterday afternoon) which include fixes to the problem with Pods not clearing cache upon updating (actually included in 2.6.4). This particular issue had been impacting folks displaying Custom Taxonomy after updating Pods, which was easily fixed by Clearing the Pods Cache after updating. We’ve incorporated the Cache clearing properly into the Pods Update process so this should no longer be an issue.
2.6.5 includes fixes to Polylang Compatibility with Pods provided by @JoryHogeveen. Many thanks to him for helping us remain compatible with this excellent multilingual plugin.
2.6.5 also includes a fix for Pods names that had underscores in them inadvertently changing to hyphens upon saving or making changes to the Pod. This bug was introduced into the wild with Patch 2.6.3 to fix an issue with hyphenated names changing to underscores. We are very grateful to our GitHub users @lkraav and @remkocalf for helping us track down and isolate these two issues. We seriously appreciate our loyal Pods Community being so diligent with reporting any bugs to our GitHub repository so we can track down the problems and correct them quickly.
2.6.5.1 was released overnight to address a problem with seeing the Additional Field Options when editing a pod field.
2.6.5.2 was released this morning to address a Polylang compatibility issue which could cause a Fatal error on some sites running both Pods and Polylang.
If you are on 2.6.3, please make sure you update to 2.6.5.2 in order to fix any underscore to hyphenation naming issues. It is recommended you only use underscores in your Pods name to comply with WordPress Naming Conventions in Coding Standards, but we know several plugins out there create Custom Post Types and Taxonomy that do not follow these rules and patch 2.6.5 makes sure we don’t break any work you’ve done with Pods and those particular Custom Post Types or Taxonomy.
It wasn’t our intention to have so many maintenance releases back-to-back but we believe our users matter more than our pride. We wanted these issues squashed and dealt with quickly and out to you immediately.
As always you can read the entire Change Log for Pods at the WordPress.org Repository.
