Pods 3.0 Feature Release: Conditional Logic for Fields

Watch the Conditional Logic feature highlight video for a quick overview of how it looks and works.

What’s new in Pods 3.0?

Conditional Logic for Fields – You can now choose to show or hide a field based on the value of another field. More will be expanded into this functionality in the future. 🎉
Command Palette support for WordPress 6.3+ – You can now contextually go to the Edit Pod screen for the matching Pod configuration of that post type directly from the Edit Post screen.

New minimum WP version required: WordPress 6.0+ (previously: WP 5.7+) — We will continue to support at least the last two major WP releases on each major feature release of Pods but we made an exception for this release.
New minimum PHP version required: PHP 7.2+ (previously: PHP 5.6+) — Hey! You should take the time to update to PHP 8.1+ because that is the lowest version actively supported by The PHP Group.

Added: Set up backward compatible updates to our prior depends-on and related logic for internal conditional logic prior to Pods 3.0 so they now properly translate over to the new format required.
Added: When importing and exporting Pods packages, they now include the list of active components.
Fixed: All known PHP 8.x compatibility issues have been resolved
Fixed: Media saving issue has been resolved when the Media Modal fields are disabled, it now saves fields as expected.
Fixed: Improved compatibility with Polylang.
Fixed: Redirects after deleting a Pod now send to the current site dashboard instead of hardcoded /wp-admin/ link.
Fixed: When extending a post type or taxonomy it will now use the associated post type or taxonomy label when setting up the pod so it matches.
Fixed: Resolved problems with saving the featured image from frontend forms when a post type supports featured images.
Fixed: Don’t show SQL errors when getting relationship data for forms if the debug display is disabled in WP.
Fixed: Improved tooltip appearances with better color contrast.
Removed: The Tribe Common library has been removed from Pods and it will alleviate conflicts from plugins like The Events Calendar and Event Tickets going forward.

Pods 3.1 – In the short term, we are working on a feature that came up after doing extensive research into a flexible solution to better manage and explain user capability access to the WordPress core content types. This feature will be released in the coming weeks as it was not quite ready for the 3.0 release timeline we initially hoped for.
Docs focused release cycle – We are doing something different with our following release cycle for Pods 3.2. Instead of immediately moving onto Pods 3.2 development, we will be entirely focused on Documentation, Tutorials, and Video content.
Pods 3.2 – Before that next release cycle ends in Spring 2024, we will send out notifications to all donors with a link to vote on the next Pods 3.2 feature that we will build.

Want to help keep Pods on track? None of Pods 3.0 would have been possible without the help from our Friends of Pods.