PluginProbe ʕ •ᴥ•ʔ
Pods – Custom Content Types and Fields / trunk
Pods – Custom Content Types and Fields vtrunk
trunk 1.14.8 2.7.31.3 2.8.23.3 2.9.19.3 3.0.10.3 3.1.4.1 3.2.0 3.2.1 3.2.1.1 3.2.2 3.2.4 3.2.5 3.2.6 3.2.7 3.2.7.1 3.2.8 3.2.8.1 3.2.8.2 3.3.0 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9
pods / readme.txt
pods Last commit date
classes 4 months ago components 3 months ago deprecated 4 months ago includes 1 month ago sql 4 months ago src 4 months ago ui 1 month ago vendor 4 months ago changelog.txt 1 month ago init.php 1 month ago license.txt 10 years ago readme.txt 1 month ago
readme.txt
309 lines
1 === Pods - Custom Content Types and Fields ===
2 Contributors: sc0ttkclark, zrothauser, keraweb, jimtrue, quasel, nicdford, jamesgol, ramoonus, pglewis, dan.stefan, Desertsnowman, mgibbs189, Shelob9, clubduece, curtismchale, mikedamage, jchristopher, pcfreak30
3 Donate link: https://friends.pods.io/
4 Tags: pods, custom post types, custom taxonomies, content types, custom fields
5 Requires at least: 6.3
6 Tested up to: 7.0
7 Requires PHP: 7.2
8 Stable tag: 3.3.9
9 License: GPLv2 or later
10 License URI: http://www.gnu.org/licenses/gpl-2.0.html
11
12 Pods is a framework for creating, managing, and deploying customized content types and fields for any project.
13
14 == Description ==
15
16 Manage all your custom content needs in one location with the Pods Framework.
17
18 * **Create content types** including Custom Post Types, Custom Taxonomies, and our special Advanced Content Types (ACTs get their own custom tables)
19 * **Extend and customize content types** including Posts, Pages, Categories, Tags, Users, and Media with one easy click
20 * **Create custom settings pages** easily within seconds
21 * **Add custom fields** to *any* content type
22 * **Conditionally show fields** based on the value of other fields with Conditional Logic
23 * **Group your fields** however you'd like into their own sections and add additional headings to help organize
24 * **Show your fields** anywhere using our [blocks](https://docs.pods.io/displaying-pods/pods-blocks/), [shortcodes](https://docs.pods.io/displaying-pods/pods-shortcode/), [widgets](https://docs.pods.io/displaying-pods/pods-widgets/), or the non-coder [Pods Template](https://docs.pods.io/displaying-pods/pods-templates/) approach along with our [automatic theme integration](https://docs.pods.io/displaying-pods/pods-templates/auto-templates/)
25 * **Create connections** between any of your content with [relationship fields](https://docs.pods.io/fields/relationship/) to keep your content organized
26
27 Let Pods help you grow your development and site building skills so that you can manage content beyond the standard WordPress Posts & Pages.
28
29 Want to check it out? Give Pods a test drive with our new [One-click Demo](https://pods.io/demo/).
30
31 Check out our [Documentation](https://docs.pods.io/), [Support Forums](https://wordpress.org/support/plugin/pods/), and our [Live Community Slack Chat](https://support.pods.io/chat/) for assistance building your dream project with Pods.
32
33 = Introduction =
34
35 [youtube https://www.youtube.com/watch?v=0WqKZr2gPZY]
36
37 = Content types that evolve with your needs =
38
39 Create any type of content that you want -- small or large -- we've got you covered. Every content type created with Pods gets all the love it needs to grow up big and strong. You'll get an easy-to-use interface that lets you manage field groups, custom fields, and how your content type will look or function.
40
41 = Create new content types =
42
43 With Pods, you can create entirely new content types and settings pages.
44
45 = Every Field Type, FREE =
46
47 If you choose to use Pods for your custom fields, you'll get every field type you need, free of charge. Pods works great alongside [other custom field plugins](https://comparewp.org/cck) like [Advanced Custom Fields](https://wordpress.org/plugins/advanced-custom-fields/) too.
48
49 We have an extensive collection of over [25 different input types to choose from on 20+ different field types for any content structure](https://docs.pods.io/fields/). Each field type comes with their own additional options to help you customize content entry and display.
50
51 You can also control visibility by role/capability and [other advanced options](https://docs.pods.io/fields/settings-advanced/).
52
53 * **Repeatable Fields:** Turn almost any field into a repeatable field with multiple values
54 * **Text:** Plain Text, Website, Phone, Email, Password
55 * **Paragraph:** Plain Paragraph Text, WYSIWYG (Visual Editor), Code (Syntax Highlighting)
56 * **Date / Time:** Date and Time, Date, Time
57 * **Number:** Plain Number, Currency (30+ international currencies)
58 * **Relationships / Media:** File / Image / Video (Media library and basic upload options available), Avatar (for extended Users), oEmbed, Relationship (Dropdown, Multi Select, Autocomplete, Checkboxes, Radio Buttons, and List View available)
59 * **Checkbox** (Yes / No)
60 * **Color Picker**
61 * **Layout Fields:** Heading text, HTML content
62
63 = Relationships to rule the world with =
64
65 The power is in your hands with our comprehensive support to **relate your content to anything**.
66
67 * **Custom defined lists** of text options
68 * Relate to any **Post Type or Taxonomy** posts / terms
69 * Relate to any **User** profile
70 * Relate to **User Roles or Capabilities**
71 * Relate to any **Comment**
72
73 And many other relationships are also available including:
74
75 * **Image Sizes**
76 * **Navigation Menus**
77 * Relate to content within **any Database Table**
78 * **Countries** (predefined)
79 * **US States** (predefined)
80 * **Canadian Provinces** (predefined)
81 * **Calendar - Days of Week** (predefined)
82 * **Calendar - Months of Year** (predefined)
83 * And many more!
84
85 = Optional Components to do even more =
86 You can enable some of our included components to extend your WordPress site even further:
87
88 * **Types-only Mode** - On our Pods Settings page, you can choose to disable creating custom fields for a performance boost if you only want to use Pods for content types or you plan on using it alongside of other custom field plugins
89 * **Pods Templates** - Use our [template engine](https://docs.pods.io/displaying-pods/pods-templates/) to create templates that can be handed off to clients for care-free management
90 * **Markdown Syntax** - Parses [Markdown Syntax](https://www.markdownguide.org/basic-syntax) for Paragraph Text / WYSIWYG fields
91 * **Advanced Relationships** - Add even more relationship objects including Database Tables, Multisite Networks, Multisite Sites, Themes, Page Templates (in the theme), Sidebars, Post Type Objects, and Taxonomy Objects
92 * **Table Storage** - Enable table-based database storage for custom fields on Post Types, Media, Users, and Comments
93 * **Roles and Capabilities** - Create or edit Roles for your site and customize what they have access to
94 * **Advanced Content Types** - Create entirely custom content types that have their own database table, and they will exist outside the normal WordPress context avoiding meta database tables
95 * **Pods Pages** - Create custom pages that function off of your site's URL path with wildcard support and choose the Page Template in the theme to use -- most useful paired with Advanced Content Types
96
97 = Plugins that integrate with Pods =
98
99 * [Advanced Views Lite](https://wplake.org/advanced-views-lite/?ref=5) - Lets you build templates (views) and queries (cards) so that you can manage your content rendering with less code. (Disclaimer: We have an affiliate link to them to help support our project)
100 * [Bricks Builder](https://bricksbuilder.io/)
101 * [Codepress Admin Columns](https://wordpress.org/plugins/codepress-admin-columns/) using premium [Admin Columns Pro](https://www.admincolumns.com/pods/) Pods integration
102 * [Conductor](https://conductorplugin.com/)
103 * [Elementor Pro](https://elementor.com/pro/)
104 * [Polylang](https://wordpress.org/plugins/polylang/) has direct integration in Pods itself
105 * [Timber](https://wordpress.org/plugins/timber-library/)
106 * [WPGraphQL](https://wordpress.org/plugins/wp-graphql/) has direct integration in Pods itself
107 * [WPML](http://wpml.org/) has direct integration in Pods itself
108 * [YARPP](http://wordpress.org/plugins/yet-another-related-posts-plugin/) has direct integration in Pods itself
109
110 = Themes that integrate with Pods =
111
112 * [Genesis](https://www.studiopress.com/themes/genesis/) (StudioPress) has direct integration in Pods itself
113
114 = Extend Pods with Free Add-Ons =
115
116 * [Pods Beaver Themer Add-On](https://wordpress.org/plugins/pods-beaver-builder-themer-add-on/) - Integrates Pods with [Beaver Themer](https://www.wpbeaverbuilder.com/beaver-themer/)
117 * [Pods Gravity Forms Add-On](https://wordpress.org/plugins/pods-gravity-forms/) - Integrates Pods with [Gravity Forms](https://www.gravityforms.com/)
118 * [Pods Alternative Cache Add-On](https://wordpress.org/plugins/pods-alternative-cache/) - Speed up Pods on servers with limited object caching capabilities
119 * [Pods SEO Add-On](https://wordpress.org/plugins/pods-seo/) - Integrates Pods Advanced Content Types with Yoast SEO
120 * [Pods AJAX Views Add-On](https://wordpress.org/plugins/pods-ajax-views/) - Adds new functions you can use to output template parts that load via AJAX after other page elements
121
122 = Extend Pods with Free Third-party Add-Ons =
123
124 * [Paid Memberships Pro - Pods Add On](https://wordpress.org/plugins/pmpro-pods/) - Integrates Pods with [Paid Memberships Pro](https://wordpress.org/plugins/paid-memberships-pro/) to extend PMPro objects with custom fields added by Pods
125 * [Panda Pods Repeater Field Add-On](https://wordpress.org/plugins/panda-pods-repeater-field/) - Lets you add groups of fields that repeat and are stored in their own custom database table (Advanced setup required)
126
127 = Pods Pro by SKCDEV Premium Add-Ons =
128
129 * [List Tables Add-On](https://pods-pro.skc.dev/downloads/list-tables/) - A new block and shortcode to list/filter content from Pods in a table format
130 * [Page Builder Toolkit Add-On](https://pods-pro.skc.dev/downloads/page-builder-toolkit/) - Integrates Pods with [Beaver Builder](https://wordpress.org/plugins/beaver-builder-lite-version/), [Beaver Themer](https://www.wpbeaverbuilder.com/beaver-themer/), [Conditional Blocks Pro](https://conditionalblocks.com/), [Divi Theme](https://www.elegantthemes.com/gallery/divi/), [Elementor](https://wordpress.org/plugins/elementor/), [GenerateBlocks](https://wordpress.org/plugins/generateblocks/), [Oxygen Builder](https://oxygenbuilder.com/), and [Stackable Blocks (premium)](https://wpstackable.com/premium/)
131 * [Advanced Relationships Storage Add-On](https://pods-pro.skc.dev/downloads/advanced-relationship-storage/) - Advanced options for relationship storage
132 * [TablePress Integration Add-On](https://pods-pro.skc.dev/downloads/tablepress-integration/) - Integrates Pods with [TablePress](https://wordpress.org/plugins/tablepress/)
133 * [Advanced Permalinks Add-On](https://pods-pro.skc.dev/downloads/advanced-permalinks/) - Advanced permalink structures and taxonomy landing pages
134
135 == Installation ==
136
137 1. Unpack the entire contents of this plugin zip file into your `wp-content/plugins/` folder locally
138 1. Upload to your site
139 1. Navigate to `wp-admin/plugins.php` on your site (your WP Admin plugin page)
140 1. Activate this plugin
141
142 OR you can just install it with WordPress by going to Plugins >> Add New >> and type this plugin's name
143
144 == Frequently Asked Questions ==
145
146 = Where do I go for Support on your plugin? =
147
148 Our primary Support is handled through our [Support Forums](https://wordpress.org/support/plugin/pods/). For the fastest support, you can contact us on our [Live Community Slack Chat](https://support.pods.io/chat/) in the #support channel. We do not staff our Slack channel 24/7, but we do check any questions that come through daily and reply to any unanswered questions.
149
150 We do have a community of Pods users and developers that hang out on Slack, so you're sure to get an answer quickly. We answer our Forum questions once a week with follow-up during the week as we're prioritizing resources towards restructuring and improving our documentation.
151
152 = Where do I report bugs or request features? =
153
154 If you’ve encountered a bug or have an idea for a new feature, we kindly request you to create an Issue on our GitHub Repository at [https://github.com/pods-framework/pods/issues/new](https://github.com/pods-framework/pods/issues/new). Please be very specific about what steps you did to create the issue you’re having and include any screenshots or other configuration parameters to help us recreate or isolate the issue.
155
156 = Will Pods work with my Theme? =
157
158 Most likely the answer is yes. We don't require any special CSS or display attributes to use Pods with your theme, so you should have little to no difficulty showing your content in your theme. If you encounter any issues, contact your theme developer and ask them about their support for the standard WordPress theming functions and how to use [WordPress Template Hierarchy](https://wphierarchy.com) with their theme.
159
160 == How can I translate Pods into my own language? ==
161
162 Many thanks go out to the fine folks who have helped us translate the Pods plugin into many other languages.
163
164 Join us in further translating the Pods interface on the official [Translating WordPress dashboard](https://translate.wordpress.org/projects/wp-plugins/pods)
165
166 We are also available through our [Live Community Slack Chat](https://support.pods.io/chat/) to help our translators get started and to support them on the process.
167
168 Are you looking to translate your Pods and Fields themselves? You'll want to enable the "Translate Pods" component from Pods Admin > Components.
169
170 == Screenshots ==
171
172 1. Create new content types or extend existing ones
173 2. Add groups of fields and manage your content type
174 3. Add fields of many types with individual options for each
175 4. Creating or extending a Post Type will add groups of fields to the Post Editor
176 5. Creating or extending a Taxonomy will add groups of fields to the Term Editor
177 6. Extending Users will add groups of fields to the User Profile and Edit forms
178
179 == Contributors ==
180
181 Pods really wouldn't be where it is without all the contributions from our [donors](https://friends.pods.io) and [code/support contributors](https://github.com/pods-framework/pods/graphs/contributors).
182
183 == Changelog ==
184
185 = 3.3.9 - May 20th, 2026 =
186
187 * Security: Resolve a XSS vulnerability in the Pods UI forms in the admin area. Props to Bonds through Patchstack for responsibly reporting this. (@sc0ttkclark)
188
189 = 3.3.8 - March 19th, 2026 =
190
191 * Feature: Reuse the same UI that Repeatable Fields use for the Relationship fields using "List View" list items. The UI is now consistent and Pods 3.4 will include the same UI treatment for the File fields. (@sc0ttkclark)
192 * Fixed: Resolve issue with reordering repeatable fields and prevent rendering incorrectly when typing in the field which causes focus to be lost. #7498 #7499 (@pdclark, @sc0ttkclark)
193 * Fixed: Resolve problems with reordering Relationship fields using "List View" list items. (@sc0ttkclark)
194 * Fixed: Resolve issue with Migrate PHP component not placing magic tags on the correct separate new line of the file header. (@sc0ttkclark)
195 * Fixed: Prevent conflicts with ACF/SCF when ACF compatibility functions are enabled.
196
197 = 3.3.7 - February 25th, 2026 =
198
199 * Fixed: Resolve issues using `WP_Filesystem` to check session paths before starting a session. (@sc0ttkclark)
200 * Fixed: Prevent deprecated notices with non-strings being passed to `strpos`. (@sc0ttkclark)
201
202 = 3.3.6 - February 25th, 2026 =
203
204 * Fixed: Resolve a fatal error with `WP_Filesystem` usage. (@sc0ttkclark)
205
206 = 3.3.5 - February 24th, 2026 =
207
208 * Minimum Requirements Notice: Pods 3.4 coming in 2026 will require new minimum versions of WordPress 6.8+, PHP 8.0+, and MySQL 5.7+
209 * Feature: Added support for showing fields as "Read Only" in forms when a user does not have edit access to them while allowing admins to continue editing them. You can find this under the Edit Field modal in Advanced > Visibility > UI Access. (@sc0ttkclark)
210 * Enhancement: When detecting malformed shortcodes broken by `<` or `>` characters within the `where` clause, Pods now shows a helpful notice with workaround instructions instead of just breaking. #7451 #7482 (@sc0ttkclark)
211 * Enhancement: New replacements within Pods shortcodes clauses for replacing `__LESS_THAN__`, `__LESS_THAN_OR_EQUAL__`, `__GREATER_THAN__`, and `__GREATER_THAN_OR_EQUAL__` with their corresponding `<`, `<=`, `>`, and `>=` characters to work around broken WP shortcodes. This is also available in the `[if]` Pods template shortcode `compare` attribute. #7451 #7482 (@sc0ttkclark)
212 * Enhancement: New option for conditional logic that will allow saving conditional field values even when the field is hidden. #7475 #7484 (@faisalahammad, @sc0ttkclark)
213 * Enhancement: New setting at Pods Settings > Performance that allows you to "Limit autocomplete search results in Relationship fields" to specify larger numbers if needed. #7454 (@sc0ttkclark)
214 * Enhancement: PodsUI > Implement `pods_ui_after_heading` hook for additional UI customizations. (@sc0ttkclark)
215 * Enhancement: PodsUI > Move restricted() checks before callbacks to prevent additional unnecessary calls when user doesn't have access. (@sc0ttkclark)
216 * Enhancement: Add `pods_v_bool` that uses `pods_is_truthy` to enforce boolean values on variables from various sources. (@sc0ttkclark)
217 * Enhancement: Add Manage link to the Navigate section of the Pods content admin forms. (@sc0ttkclark)
218 * Enhancement: Underlying code support for multiple condition checks for Conditional Logic. (@sc0ttkclark)
219 * Tweak: Remove trim from `pods_is_truthy` and `pods_is_falsey` functions. (@sc0ttkclark)
220 * Tweak: In the Edit Field modal, under the Advanced > Visibility section -- the Restrict Access and UI Access are now separate checkbox groups. (@sc0ttkclark)
221 * Tweak: Pods now follows WP Admin Theme color schemes more closely using dynamic CSS color references to the scheme colors. (@sc0ttkclark)
222 * Fixed: Shortcode unit test issue resolved. #7472 #7473 (@devlamconstructie, @sc0ttkclark)
223 * Fixed: Loading a form with WYSIWYG React Quill used as Repeatable fields now loads without breaking the editor. #7465 #7487 (@faisalahammad, @sc0ttkclark)
224 * Fixed: Resolved reordering of values for Repeatable Date/Time, Currency, and Number fields. #7471 #7486 (@faisalahammad, @sc0ttkclark)
225 * Fixed: Resolve sync associated taxonomy with relationship issues when not using bidirectional relationship field. #7477 #7485 (@faisalahammad, @sc0ttkclark)
226 * Fixed: Resolved reordering of values in List View relationship fields. (@sc0ttkclark)
227 * Fixed: Allow empty values in email fields when field is not required. #7476 #7483 (@faisalahammad, @sc0ttkclark)
228 * Fixed: esc_html_e usage when not used for translating in PodsUI. #7462 (@DAnn2012)
229 * Fixed: The default storage type for Settings is set to `option` when creating as it should have been. (@sc0ttkclark)
230 * Fixed: When using repeatable fields on a Pod that uses Table-based storage, a notice now shows explaining that it's not an available feature. (@sc0ttkclark)
231 * Fixed: Better support when values are sent as WP_Error and now show appropriate errors in save_pod_item validation handling. (@sc0ttkclark)
232 * Fixed: Resolve heredoc issue with Migrate PHP component. (@sc0ttkclark)
233 * Fixed: WordPress 7.0 compatibility issues fixed. (@sc0ttkclark)
234 * Fixed: Conditional logic now works properly for Boolean Group sub fields (used in Edit Field modal and other Pods Admin areas). (@sc0ttkclark)
235 * Extensive cleanup to resolve important WP Plugin Checker results, PHPCS, and PHPStan issues across the codebase. (@sc0ttkclark)
236 * Extensive testing upgrades to PHPUnit 10+ and wp-browser 4. (@sc0ttkclark, @lucetume)
237 * New hourly verification of the Pods PLC DID and FAIR metadata. (@johnbillion)
238
239 = 3.3.4 - September 24th, 2025 =
240
241 * Feature: Official support for DID `did:plc:e3rm6t7cspgpzaf47kn3nnsl` for optional installation via DID using the FAIR plugin. (@sc0ttkclark)
242 * Fix: Prevent duplicates in `Pods::field()` and `Pods::display()` for simple relationships. (@sc0ttkclark)
243
244 = 3.3.3 - September 4th, 2025 =
245
246 * Tweak: Support referencing ID for `PodsMeta::groups_get()`. (@sc0ttkclark)
247 * Tweak: Update edit capability used for settings Pods so it can be displayed on the edit pod screen correctly. (@sc0ttkclark)
248 * Fixed: Resolve issues with TinyMCE and Quill editors not loading when used as repeatable fields or conditional logic. #7448 #7438 #7430 (@multisme, @altermulti, @sc0ttkclark, @ztackett11)
249 * Fixed: Resolve PHP fatal errors for undefined constant `\Pods\Whatsit\Store::PLACEHOLDER` in some edge case circumstances. #7445 (@sc0ttkclark, @Hue-SPetrovic)
250 * Fixed: Resolve PHP 8.4 deprecation warnings with DI52 usage. #7448 (@sc0ttkclark, @doehry)
251 * Fixed: Resolve warnings when using `--args` with WP-CLI commands. #7452 (@sc0ttkclark, @KhaledSakr)
252 * Fixed: Resolve handling of decimals when auto-formatting to prevent removing zero number values and expand decimal handling for more cases. Improve logic matching (except dashes) for PHP vs JS. (@sc0ttkclark)
253 * Fixed: Resolve field assigment issue in `pods_config_merge_data()` to reference the correct field. (@sc0ttkclark)
254
255 = 3.3.2 - July 8th, 2025 =
256
257 * Tweak: Updated Swagger docs for Pods REST API endpoints. (@sc0ttkclark)
258 * Tweak: `pods_error()` handles any `Exception` object including those extending the base `Exception` class. This allows for more refined error handling in Pods code. (@sc0ttkclark)
259 * Tweak: PodsAPI now allows for passing in Pods related objects to be passed into various save/load methods without breaking those objects. (@sc0ttkclark)
260 * Tweak: Allow setting new group when duplicating a field. (@sc0ttkclark)
261 * Tweak: Added Jest testing coverage for more areas of the DFV code and updated to support the React Testing Library. #7427 (@sc0ttkclark)
262 * Fixed: Block Editor saves no longer trigger full saves when an autosave is sent and Pods form validation passes. (@sc0ttkclark)
263 * Fixed: Ensure Pods cache flushes when changing settings to prevent issues with Pods Blocks configs not showing fields conditionally linked to those settings. #7429 (@sc0ttkclark)
264 * Fixed: When duplicating a pod, group, or field it will now add a space between the label and the copy number. (@sc0ttkclark)
265 * Fixed: Typos corrected across the codebase. #7434 (@szepeviktor, @sc0ttkclark)
266 * Fixed: PHP deprecated warnings resolved in Pods REST API and DI52 usage. #7401 #7437 (@BrookeDot, @sc0ttkclark)
267 * Fixed: Saving Pods settings will now properly flush the Pods cache to ensure that the new settings are applied immediately to all areas that may be cached based on those settings. (@sc0ttkclark)
268 * Fixed: Added a "doing it wrong" notice and debug log line for when a non-string gets sent to `Pods::do_magic_tags()` to prevent PHP warnings. (@sc0ttkclark)
269 * Fixed: Better caching around the `pods_can_use_dynamic_feature_sql_clauses()` setting usage to prevent additional DB calls. (@sc0ttkclark)
270 * Fixed: Resolve issues when saving featured image based on the first value of a file field so it only saves files with the image type. #7433 (@sc0ttkclark)
271 * Fixed: Add support for `Value_Field` in `pods_config_for_field()` to ensure bidirectional relationships work as expected for saving on both sides. #7435 (@sc0ttkclark)
272 * Fixed: Prevent erroneous `?` and `#` characters in website formatting. (@sc0ttkclark)
273
274 = 3.3.1 - May 2nd, 2025 =
275
276 * Fixed: Resolve issue with `get_block_wrapper_attributes()` usage. (@sc0ttkclark)
277
278 = 3.3 - May 1st, 2025 =
279
280 * New minimum WP version required: WordPress 6.3+ (previously: WP 6.0+)
281 * Removed: PHP support for Pod Templates and Pod Pages has been officially removed from Pods. This feature was deprecated in Pods 2.3. We recommend you follow the newer more secure way: https://docs.pods.io/displaying-pods/pod-page-template-hierarchy-for-themes/ and https://docs.pods.io/displaying-pods/pod-template-hierarchy-for-themes/ and a snippet if you absolutely still need PHP support for now https://gist.github.com/sc0ttkclark/35a15e6f93622c45f12d671184fb1315 (@sc0ttkclark)
282 * Feature: Form validation for the Block Editor now prevents saving a post if there are required fields and shows the appropriate error message. #7343 #7369 (@JoryHogeveen, @sc0ttkclark)
283 * Feature: Upgraded Pods Blocks to the WP Blocks API version 3 to support more features like block wrapper attributes and the iframe editor. (@sc0ttkclark)
284 * Feature: Added support for WYSIWYG field type when using the TinyMCE editor to allow Delayed initialization and not showing the editor until clicking. This is optional and can be enabled per field. (@sc0ttkclark)
285 * Feature: Added support for WYSIWYG field type when using the TinyMCE editor to refresh the editor if you encounter compatibility issues with other plugins on load. (@sc0ttkclark)
286 * Tweak: Allow forcing `pods_serial_comma()` to use exactly what is sent instead of relying on the field config itself. (@sc0ttkclark)
287 * Tweak: Remove Pods Pro WPGraphQL deactivation message to support future features there. The core functionality of that was merged into Pods 2.9 but new work is still being done in the add-on. (@sc0ttkclark)
288 * Tweak: Pods Forms now wrap `div` / `p` form output types within a new `div.pods-form-fieldset` wrapper element. The table form output type has the new class `pods-form-fieldset` added to it too. (@sc0ttkclark)
289 * Fixed: Prevent doing it wrong notices in WP from unintentionally loading translatable strings too early. (@sc0ttkclark)
290 * Fixed: Improved PHP compatibility with strlen() usage. #7394 (@lbonomo, @sc0ttkclark)
291 * Fixed: More PHP 8.x compatibility fixes for `PodsUI`. (@sc0ttkclark)
292 * Fixed: Docs link for Date / Time field type now points to the correct URL. #7405 (@BrookeDot)
293 * Fixed: Remove unnecessary duplicate IDs in the fetching within `Pods::field()`. (@sc0ttkclark)
294 * Fixed: Name check handling when duplicating pod now works as expected and prevents weirdly named duplicate pod names. (@sc0ttkclark)
295 * Tooling: Generate build provenance attestation during deployment for .org zip. #7419 (@johnbillion)
296
297 Our GitHub has the full list of all prior releases and changelogs for Pods: [https://github.com/pods-framework/pods/releases](https://github.com/pods-framework/pods/releases)
298
299 == Upgrade Notice ==
300
301 = 3.1 =
302 This upgrade is security focused.
303
304 = 3.0 =
305 This upgrade requires a minimum versions of PHP 7.2+ and WordPress 6.0+.
306
307 = 2.8 =
308 This upgrade requires a minimum versions of PHP 5.6+ and WordPress 5.5+.
309