3.0.3 - September 22nd, 2023

• Fixed: Settings pods handling for relationships for Pods that are registered by DB / Code / File now normalize as necessary for relationships stored in the wp_podsrel index table for which item ID is used to relate from. (@sc0ttkclark)

3.0.2 - September 21st, 2023

• Feature: You can now disable the Add New forms for a Post Type pod under the Advanced tab. (@sc0ttkclark)
• Fixed: Bi-directional field saving has been restored after breaking in Pods 2.9.x. #7172 (@sc0ttkclark)
• Fixed: More PHP notices/warnings/errors with PHP 8+ addressed. #7170 #7171 (@sc0ttkclark)
• Fixed: Settings saving for simple relationships fixed when using a setting pod registered by code/file. #7169 (@sc0ttkclark)
• Fixed: Settings forms would sometimes say the save failed when it was successful. (@sc0ttkclark)
• Fixed: Fix relationship rendering in tables for Advanced Content Types. #7173 (@sc0ttkclark)
• Fixed: Potential SQL errors when a Pod does not exist but it's still set a relationship object for a field. (@sc0ttkclark)
• Fixed: Pod config data is now correctly passed in all instances of pods_meta_default_box_title filter so it's uniform in usage. (@sc0ttkclark)
• Fixed: Bypass "@" prefixed items from being processed in file-based configs. (@sc0ttkclark)
• Fixed: Removed extra line in array for post type definition where can_export was set two times. (@sc0ttkclark)
• Fixed: Resolved some cases where boolean return types were treated as filters in `Store::find()`` calls. (@sc0ttkclark)
• Fixed: The Pods\Blocks\Types\Base::in_editor_mode() method resolves PHP issue with current screen reference. (@sc0ttkclark)
• Fixed: Ensure code/file based configs do not overwrite DB configs to avoid potential issues where duplicate configs get pulled up in lookups. (@sc0ttkclark)
• Fixed: Some relationship field options were not showing their available options to select from when editing a field on the Edit Pod screen. #7176 (@sc0ttkclark)

3.0.1 - September 13th, 2023

• Fixed: Custom Settings Pages no longer have the error when saving that was introduced by changes made in Pods 3.0. (@sc0ttkclark)

3.0 - September 13th, 2023

Compatibility warning

New minimum required versions have been updated as follows which includes notices to let you know if you need to update something:

• New minimum WP version required: WordPress 6.0+ (previously: WP 5.7+)
• 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 currently the lowest version actively supported by The PHP Group.

Changelog

• Feature: Conditional Logic for Fields - You can now choose to show or hide a Pods field based on the value of another Pods field. More will be expanded into this functionality in the future. #609 (@zrothauser, @sc0ttkclark, @Shelob9)
• Feature: Support for the new Command Palettes feature added in WordPress 6.3. This will allow you to contextually go to the Edit Pod screen for the matching Pod configuration of that post type directly from the Edit Post screen. (@sc0ttkclark)
• 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. (@sc0ttkclark)
• Added: When importing and exporting Pods packages, they now include the list of active components. (@sc0ttkclark)
• Fixed: Media saving issue has been resolved when the Media Modal fields are disabled, it now saves fields as expected. #7158 (@sc0ttkclark, @pd-cm)
• Fixed: Improved compatibility with Polylang. #7139 #7140 (@JoryHogeveen)
• Fixed: Redirects after deleting a Pod now send to the current site dashboard instead of hardcoded /wp-admin/ link. #7137 #7162 (@JoryHogeveen)
• 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. #6350 (@sc0ttkclark)
• Fixed: Resolved problems with saving the featured image from frontend forms when a post type supports featured images. (@sc0ttkclark)
• Fixed: Don't show SQL errors when getting relationship data for forms if the debug display is disabled in WP. (@sc0ttkclark)
• Fixed: Improved tooltip appearances with better color contrast. #7119 #7118 (@heybran)
• 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. (@sc0ttkclark)

2.9.19 - June 28th, 2023

• Fixed: Ensure that cache modes are validated correctly to prevent transients / static cache / etc from being forced into persistent cache which could fill caches up. (@sc0ttkclark, props to Björn Hasselberg for helping debug and find this)

2.9.18 - June 23rd, 2023

• Tweak: Abstract all container calls for Tribe Common library to Pods specific functions. (@sc0ttkclark)
• Fixed: Prevent fatal errors with our service provider classes that was caused by a new version of The Events Calendar / Event Tickets plugin from a change to the Tribe Common library that they made. #7105 #7106 (@JoryHogeveen, @sc0ttkclark)

2.9.17 - June 22nd, 2023

• Performance: Allow disabling showing fields in the Media Library modals for sites that experience heavy performance issues from large media grids in the admin area. This new option is available in Pods Admin > Settings > Performance. (@sc0ttkclark)
• Tweak: Optimize single item lookups in the PodsAPI for post type configurations. (@sc0ttkclark)
• Fixed: Normalize the calls to the list of pod types that were coming from multiple places so they come from PodsAPI::get_pod_types(). (@sc0ttkclark)
• Fixed: Resolve issues where pod may not specifically be saved as extended but should be treated as extended for custom pod type objects. (@sc0ttkclark)
• Fixed: Don't save the newer options for PodsAPI::save_pod() as actual pod config options. (@sc0ttkclark)
• Fixed: Ignore more internal post types / taxonomies from plugins like Elementor and WooCommerce to prevent conflicts. (@sc0ttkclark)
• Fixed: Resolve potential PHP errors when Wisdom options aren't an array as expected. (@sc0ttkclark)

2.9.16 - June 10th, 2023

• Tweak: Allow bypassing table schema updates and overwriting table schemas in PodsAPI::save_pod() with the new parameters bypass_table_schema and overwrite_table_schema. (@sc0ttkclark)
• Tweak: Support passing the full WP object (post/term/etc) into pods( $wp_object ) and use the ID associated with it instead of only the get_queried_object_id(). #7094 #7095 (@JoryHogeveen)
• Fixed: The Pods repair tool was overwriting the storage type for table-based pods to meta, now it uses the proper logic there and also uses a new abstracted method Pod::get_default_storage() for defaults when empty. The tool now also won't overwrite the table schema for each Pod to prevent unintended problems. (@sc0ttkclark)
• Fixed: Resolved PHP error when using WordPress versions prior to 6.1 which did not have the did_filter() function that was called. (@sc0ttkclark)
• Fixed: Resolved issues when using Content Types only mode (no custom fields) in the Pods Settings so that Components like Pods Pages and Pods Templates will continue to have their fields shown. (@sc0ttkclark)

2.9.15 - May 30th, 2023

• Added: Now showing text notices to explain where performance may be improved for Relationship single/multi select fields when relating to dynamic content which direct the admin to use Autocomplete or List View instead in certain circumstances. (@sc0ttkclark)
• Added: Add repair tool that can help recover any Pods that have an invalid pod type / storage. (@sc0ttkclark)
• Tweak: Make the default as Dropdown for single select relationship fields again after seeing some reported issues. (@sc0ttkclark)
• Fixed: Resolved more PHP 8.x compatibility issues for strlen() usage. (@sc0ttkclark)
• Fixed: Set default as Dropdown for relationship field configs across Pods. (@sc0ttkclark)

2.9.14 - May 29th, 2023

• Added: New component: Migrate: Import from the Advanced Custom Fields plugin -- It allows importing the Custom Post Types and Custom Taxonomies from ACF. Note: This does not migrate custom fields or field groups. (@sc0ttkclark)
• Tweak: List View is now the default for Relationship fields that are single select. (@sc0ttkclark)
• Tweak: Updated Site Health info for Pods to include what Pods settings someone has and included memory limit with current memory limit for easier reference. (@sc0ttkclark)
• Tweak: Default the "Watch WP Metadata calls" setting to off by default for Pods 2.9.14+. (@sc0ttkclark)
• Fixed: Always default the Pods setting for metadata_integration to off for new Pods installs when WooCommerce is detected to also be installed. (@sc0ttkclark)
• Fixed: Validate cache mode used across Pods to ensure unknown modes do not trigger PHP errors. (@sc0ttkclark)
• Fixed: Resolve PHP errors when registering ACTs via code/JSON. (@sc0ttkclark)
• Fixed: Ensure the parent post ID gets set in more cases when uploading files via a Pod uploader. (@sc0ttkclark)
• Fixed: Set default display filter as empty and avoid strlen PHP errors. #7076 #7075 (@JoryHogeveen)
• Fixed: TinyMCE on frontend would sometimes not show line breaks as paragraphs. #7051 #7049 (@sc0ttkclark)
• Fixed: Allow HTML5 date fields to allow empty values. #7063 #7016 (@Shelob9)
• Fixed: Resolved more PHP 8.x warnings and notices. #7074 (@sc0ttkclark)
• Fixed: Configurations registered via JSON/YML that include field groups are now working as expected to register each group and corresponding fields. #7062 (@sc0ttkclark)
• Fixed: Removed the extra DB call to get registered Pods blocks from the DB that can be re-enabled via a filter pods_blocks_api_get_blocks_bypass_post_type_find. (@sc0ttkclark)