2.9.8 - September 29th, 2022

• Enhancement: New pods_config_for_field function helps to set up consistent field objects when custom arrays are used. (@sc0ttkclark)
• Enhancement: The pods_config_for_pod function now handles basic Pod arrays as well. (@sc0ttkclark)
• Enhancement: New Whatsit object now runs the pods_whatsit_setup and pods_whatsit_setup_(pod|field) actions during setup so the objects can easily be overridden. (@sc0ttkclark)
• Enhancement: New Field::is_separator_excluded() method to help determine if current field is excluded from separators using pods_serial_comma(). (@sc0ttkclark)
• Tweak: Minor code and performance optimizations. (@sc0ttkclark)
• Fixed: Resolved PHP error registering code-based taxonomies. (@naveen17797)
• Fixed: Resolved cache that wasn't getting cleared when a Template was saved. (@sc0ttkclark)
• Fixed: oEmbed fields are editable again after fixing an issue with the readonly option. (@sc0ttkclark)
• Fixed: Help to prevent magic tag helpers from causing fatal errors when they are used improperly. (@sc0ttkclark)
• Fixed: Resolved issue with getting field values from Pods::field() for code-based relationships that have no ID. (@sc0ttkclark)

2.9.7 - September 23rd, 2022

• Enhancement: You can now toggle every checkbox at once on the Packages > Export screen instead of just by section. (@sc0ttkclark)
• Enhancement: The Field object now has a new is_file() method to determine whether the field is a recognized file field type (file or avatar). (@sc0ttkclark)
• Tweak: Post Type Objects and Taxonomy Objects are now available through Relationships and have been moved from the Advanced Relationships component. (@sc0ttkclark)
• Fixed: Resolve issue with some sites having an asset issue with the Pods Template editor. #6924 #6921 (@JoryHogeveen)
• Fixed: Code-based file fields now work correctly with the plupload AJAX handler. (@sc0ttkclark)
• Fixed: Code-based relationship fields now lookup their data correctly in more places like in Pods::field(). (@sc0ttkclark)

2.9.6 - September 22nd, 2022

• Fixed: Resolve issue with autocomplete nonce check and autocomplete method. #6919 (@sc0ttkclark)

2.9.5 - September 22nd, 2022

• Fixed: Resolved reported issues with Pods Templates saving and loading values incorrectly for Restrict Content fields. #6916 (@sc0ttkclark, @JoryHogeveen)
• Fixed: Color fields are no longer forced as a read only input. #6915 (@sc0ttkclark)
• Fixed: Settings forms are no longer out of sync between the form and fields on which form instance they belong to. #6915 (@sc0ttkclark, @JoryHogeveen)

2.9.4 - September 21st, 2022

• Feature: New block alert! "Pods Single Item - List Fields" opens the doors towards listing a list of fields in variety of format styles automatically for you. You don't have to write any HTML, just specify the field(s) you'd like to show and let the block do the rest for you. The block will display the Field Labels and the Field Values in a nice readable format. Display formats available include: ul, ol, dl, p, div, and table. Want to show all but a few fields? Just specify which fields to exclude if that's what you're after :) (@sc0ttkclark)
• Feature: New {@_all_fields} magic tag (or $pod->field('_all_fields') call) will automatically output all field values for the current Pod item in the specified format which includes showing the Field labels. Specify the format using this syntax: {@_all_fields.ul} (default is ul, but ol, dl, p, div, and table are also supported). (@sc0ttkclark)
• Feature: New {@_display_fields....} magic tag (or $pod->field('_display_fields....') call) will automatically output all field values for the current Pod item in the specified format which includes showing the Field labels. Specify the format using this syntax: {@_display_fields.ul.field_name|another_field|related_post:post_title} (default is ul, but ol, dl, p, div, and table are also supported) -- Separate your fields with a pipe "|" character and then if you need to traverse into any relationship field then just traverse each level with a colon ":" character between those fields. (@sc0ttkclark)
• Feature: New pods_data_field() function allows you to get special data fields directly instead of requiring you to use a full Pods object. (@sc0ttkclark)
• Feature: New Repair tool on the Pods Admin > Settings > Tools page helps to repair Pod, Group, and Field configuration issues that can be annoying to deal with or would normally require Database access to resolve. (@sc0ttkclark)
• Feature: You may not have known about it before but we've expanded our existing Pods DFV JS API, you can access it through the window.PodsDFV object. Methods include: getFields( pod = '', itemId = 0, formCounter = 1 ), getField( pod, itemId, fieldName, formCounter = 1 ), getFieldValues( pod = '', itemId = 0, formCounter = 1 ), getFieldValuesWithConfigs( pod = '', itemId = 0, formCounter = 1 ), getFieldValue( pod, itemId, fieldName, formCounter = 1 ), setFieldValue( pod, itemId, fieldName, value, formCounter = 1 )
• Enhancement: You can now choose what field mode you would like to use for REST API fields. The default mode is raw values, but you can choose to return rendered values or both raw+rendered values as an object to work with. #5198 (@sc0ttkclark)
• Enhancement: You can now specify a custom display separator for repeatable fields to use when rendering. #6892 #6890 (@JoryHogeveen)
• Changed: Resetting a Pod has been removed from the Pods Admin > Edit Pods page, instead of clicking "Delete All Items" there, you can now access this directly from Pods Admin > Settings > Cleanup & Reset as the new "Delete all content for a Pod" option. You can specify the Pod you want to delete content for and it explains exactly what you can expect from running it. (@sc0ttkclark)
• Tweak: Updated Pods Admin > Help page now lists more add-ons and where to get them / get support for them. (@sc0ttkclark)
• Fixed: Properly convert accents when creating a new pod and using the label to generate the pod name. #6874 (@sc0ttkclark)
• Fixed: Relationship/file fields that are hidden on the screen will now have all field values referenced instead of only the first value when multiple is enabled for that field. #6913 (@sc0ttkclark)
• Fixed: pods_query_arg() now correctly excludes all $_GET parameters when passing a manual URL into the function. (@sc0ttkclark)
• Fixed: Legacy WP-CLI commands for Pods are now showing up again, however they will be replaced in a future release with a more comprehensive solution. In the meantime, you can use those commands by calling wp pods-legacy and wp pods-legacy-api.
• Fixed: Prevent conflicting filter calls when filtering things other than post_title in the Display Field in Selection List option. #6909 #6907 (@therealgilles, @sc0ttkclark)
• Fixed: The autocomplete field now lets you click the "X" delete icon properly instead of starting drag-and-drop event. #6905 #6878 (@JoryHogeveen)
• Fixed: Resolved saving multiple files to a Media pod which would result in only the first file being saved. #6450 (@sc0ttkclark)
• Fixed: Resolved TinyMCE media button handling in some cases so that it checks the correct place in the field configuration. #6569 (@sc0ttkclark)
• Fixed: Resolved overflow issues in small screens for relationship field List View. #6542 (@sc0ttkclark)
• Fixed: Resolved issue with some TinyMCE scripts not being included on certain screens that use the TinyMCE WYSIWYG field. #6525 (@sc0ttkclark)
• Fixed: Pod/Group/Field configurations being saved now get their null-ish values (from empty select fields) sent as empty strings so they are not reverted to the previously saved value on next load. #6558 (@sc0ttkclark)
• Fixed: Pod/Group/Field configurations being saved now get their checkbox boolean options properly enforced as 0/1 and sent so they are not reverted to the default value on next load. #6485 (@sc0ttkclark)
• Fixed: Fields added manually through the older pods_group_add() function now get their field types properly recognized. #6381 (@sc0ttkclark)
• Fixed: Field config overrides for requiring a field when outputting via PHP are now properly recognized by DFV JS logic for validation and form submission prevention. #6352 (@sc0ttkclark)
• Fixed: Autocomplete field AJAX calls are now able to correctly reference the field object for code-based registered fields. #6896 (@naveen17797, @sc0ttkclark)
• Fixed: Display of the buttons in the list fields now properly aligns to the right side. #6894 #6893 (@JoryHogeveen, @sc0ttkclark)
• Fixed: Date range validation now validates based on the internal format instead of only on the display format. #6882 #6881 (@JoryHogeveen)
• Fixed: Number field type with slider inputs now use the correct number references. #6885 #6884 (@JoryHogeveen)
• Fixed: Currency field type now appears correctly on non-HTML5 fields. #6887 #6886 (@JoryHogeveen)
• Fixed: Resolved read-only fields functionality which was initially missing from the Pods 2.8+ DFV functionality. #6875 #6583 (@zrothauser, @sc0ttkclark)
• Fixed: Resolved issue where fields can disappear while being dragged from one group to another. #6873 #6867 (@zrothauser)

2.9.3 - August 18th, 2022

• Fixed: Resolve additional issue with WPGraphQL on some PHP configurations. #6868 (@sc0ttkclark)
• Fixed: Code field and others that do not support repeatable inputs are now forced to show non-repeatable inputs even if the setting was saved as on. #6855 (@sc0ttkclark)
• Fixed: TinyMCE WYSIWYG fields are now no longer showing as repeatable since they are not fully supported. Quill Editor remains supported for repeatable input. #6855 (@sc0ttkclark)
• Fixed: A development build has been resolved which broke the Code editor field. #6870 (@JoryHogeveen, @sc0ttkclark)

2.9.2 - August 16th, 2022

• Tweak: Improve the repeatable field UI elements so they blend in more. #6853 #6854 (@JoryHogeveen, @sc0ttkclark)
• Tweak: Use a popover UI for color fields. #6858 #6859 (@JoryHogeveen)
• Tweak: Use a popover UI for date, date/time, and time fields. #6857 #6389 #6860 (@JoryHogeveen)
• Fixed: Resolve conflicts with Restrict Content Pro to deal with how it uses the shared Common library. (@sc0ttkclark)
• Fixed: Resolve issues with taggable relationships not saving string values. #6862 #6863 (@JoryHogeveen, @sc0ttkclark)
• Fixed: Resolve formatting issues with saved date/time field variations on save. #6389 #6860 (@JoryHogeveen)
• Fixed: Resolve error with WPGraphQL on some PHP configurations. #6865 (@sc0ttkclark)
• Fixed: Resolve error in the field settings for Files with Gallery enabled. #6864 (@sc0ttkclark)

2.9.1 - August 10th, 2022

• Fixed: CodeMirror compatibility updated after some packages in the build caused Code fields to not show in the Pods forms. #6580 #6584 (@zrothauser, @sc0ttkclark)
• Fixed: Resolve potential fatal errors when interacting with WP_Filesystem by reading files using normal PHP functions and bypassing those edge cases. #6581 #6582 (@sc0ttkclark)

2.9 - August 9th, 2022

• Feature: Simple Repeatable Fields offers the ability to turn almost any field into a repeatable field. With repeatable fields, you can add multiple values for a field. You can use repeatable fields with the Pods template tag [each your_repeatable_field] to easily loop and display information with {@_value} Supported field types include: Plain Text, Website, Phone, Email, Password, Date / Time, Date, Time, oEmbed, Plain Paragraph text, WYSIWYG, Plain Number, Currency, and Color Picker. Supported Pod Types include: Post Types (meta-based), Taxonomies (meta-based), Users (meta-based), and Comments (meta-based). #1095 #6304 (@sc0ttkclark, @zrothauser)
• Feature: Register Pods configurations with JSON/YML files in your theme when stored in pods.json, pods/pods.json, pods/templates.json, etc. Custom paths can be registered to support third party plugins as well. Register new paths using pods_register_config_path( $full_directory_path ) that contain a /pods/ directory to automatically pull from or use pods_register_config_file( $full_file_path, 'json' ) to register a specific file. #4856 (@sc0ttkclark)
• Feature: The initial integration for WPGraphQL has been merged from the WPGraphQL Integration Add-On for Pods Pro by SKCDEV. The Add-On itself will continue to be developed with new features that are focused on Advanced Content Types and other enhancements in the future that will still remain outside of Pods core. (@sc0ttkclark)
• Feature: Drag and drop fields from one group to another. #5937 #6114 #6123 #6456 (@sc0ttkclark)
• Feature: Support importing and exporting Pods Settings in Pods Packages. #6455 (@sc0ttkclark)
• Feature: Website fields can now be set to output links with rel="nofollow" on them. (@sc0ttkclark)
• Feature: Full support for DB (Post Types), Code (PHP), and File (JSON/YML) configurations on the Pods Admin > Edit Pods screen. If you have configurations for multiple sources, you will see a new Source column (with file path) and you can filter by source. Pods with non-DB sources currently do not have Edit/Duplicate/Reset Content/Delete links. (@sc0ttkclark)
• Feature: The file field can now support any image, video, or audio mime types that are supported by WordPress. #6577 #6578 (@sc0ttkclark, @JoryHogeveen)
• Enhancement: New \Pods\Pod_Manager class allows reusing Pods instances when working with the same Pod across many areas of the code. (@sc0ttkclark)
• Enhancement: Added PodsAdmin::check_requirements() helper method. (@sc0ttkclark)
• Enhancement: Migrate Packages component is now enabled by default on new Pods installs. (@sc0ttkclark)
• Tweak: Removed special logic intended for PHP 5.3 and earlier. (@sc0ttkclark)
• Tweak: Improved performance when getting Pods configs from post type storage. #6561 #6562 (@JoryHogeveen)
• Fixed: Set the default sort to Pod Label now that more sources are supported on Pods Admin > Edit Pods. (@sc0ttkclark)
• Fixed: Prevent potential issues with $wpdb->prepare() when a related object does not have an index field set. (@sc0ttkclark)
• Fixed: Resolve issue with not reading cache when no ID is passed into Pods objects for Settings pods. #3582 #3583 (@pcfreak30, @sc0ttkclark, @JoryHogeveen)
• Fixed: Don't show the edit link in PodsUI if access is restricted, previously going to edit would show the access message but now the link won't show at all in those restricted cases. (@sc0ttkclark)
• Fixed: Resolve issues with Media modal fields showing duplicate fields. #6564 (@JoryHogeveen)
• Fixed: Handle processing the Pods display tags in a more dynamic way for attributes and passing them down to the tag handlers. (@sc0ttkclark)
• Fixed: Enable media buttons for the post_content field like they should so that forms outside the admin screen continue to function as expected. #6525 (@sc0ttkclark)
• Fixed: Resolve issues with values that are objects and convert them to arrays for relationship value formatting in DFV field renders. #6566 (@sc0ttkclark)
• Fixed: Show the Add Media button in forms that use the post_content field. #6569 (@sc0ttkclark)
• New minimum WP version required: WordPress 5.7+ (previously: WP 5.5+)
• No minimum PHP version changes (currently: PHP 5.6+) but please be aware that PHP 7.2+ will be required for the Pods 3.0+ feature release. You should take the time to update to PHP 8.0+ because there’s major speed improvements to be had 🙂

2.8.23 - July 4th, 2022

• Tweak: Added support for exporting post types and taxonomies to PHP for debugging purposes. While logged in as an admin, add ?pods_debug_register_export=1 to expose textareas on the page to get the code. (@sc0ttkclark)
• Tweak: Added support for new {@_current_page} calculation value. (@sc0ttkclark)
• Tweak: Added support for calculation values in conditional display tags like [if field="_position" value="2"]. #6513 (@sc0ttkclark)
• Fixed: Resolved revision issues when revisions_to_keep_limit is set to 0 in the post type. It was supposed to see 0 and use the default revision limit. Instead, it was disabling the revisions for that post type. #6499 (@sc0ttkclark)
• Fixed: Resolved potential PHP warnings on certain sites by preparing SQL queries separately from other string processing. #6556 #6555 #6554 (@JoryHogeveen, @sc0ttkclark)
• Fixed: Resolved potential PHP notices when getting table information in PodsData::table(). (@JoryHogeveen)
• Fixed: Resolved potential PHP type conversion warnings by passing SORT_REGULAR to `array_unique()`` in the File field saving process. (@JoryHogeveen)
• Fixed: Pods Auto Templates defaults for some fields were set to "true" and that is now treated as empty. The default for those fields are now empty as intended. This resolves notices on the Edit Pod screen about templates being used for Archives when Archives are disabled, but there was no template intentionally set for Archive. (@sc0ttkclark)