Skip to content

Releases: phoenixseo/pods-repeater

Release list

0.3.0-alpha — first public alpha

0.3.0-alpha — first public alpha Pre-release
Pre-release

Choose a tag to compare

View all tags
@phoenixseo phoenixseo released this 20 Oct 18:02
v0.3.0-alpha
5273aa9

0.3.0-alpha

First public build. Alpha: install on a test site, not on a site you depend on. There is no upgrade path guarantee between alpha builds and the data format may still move.

Repeatable field groups for Pods: a field type that stores an ordered list of rows, each row a set of sub-fields. Read back with pods_field(), or with the ACF-style reader (have_rows() / the_row() / get_sub_field()).

Requirements
WordPress 6.8 or newer (suite runs against 6.8.2)
PHP 7.4 or newer (suite passes on 7.4.33 and 8.3.35)
Pods 3.x, must be active (tested with 3.3.9.1)

Install

Download pods-repeater-0.3.0-alpha.zip below, then Plugins → Installieren → Plugin hochladen (on multisite: in the network admin). INSTALL.md in this release walks through installation and a five-step first test.

What changed in this build

  • Repeaters no longer nest. A sub-field of type repeater is refused on save — the save returns an error naming the sub-field, and writes through the API, an import or a REST call drop the nested value instead of storing a structure the frontend cannot read.
  • Compatibility statements match what was measured: WordPress 6.8 minimum, PHP 7.4 minimum, header and readme carry the same numbers and a test keeps them in sync.
  • The supported sub-field type list was corrected: file, avatar, oembed, phone, currency and slug were advertised but never accepted.
  • Known limitations are documented, with the working alternative for each.

Known limitations

  • file, avatar and oembed are not valid sub-field types.
  • Repeaters cannot be nested.
  • Field groups (reusable sub-field sets) are created in the admin only — no REST route, no WP-CLI command, no export/import.
  • Existing ACF repeater data is not migrated.
  • No block-editor or REST editor UI: in Gutenberg the value appears as raw JSON; editing happens in the classic Pods field UI.

Full list and reasoning in readme.txt under Known Limitations.

Verifying the package

pods-repeater-0.3.0-alpha.manifest.txt is the file list read out of the built zip, not a statement of intent — 12 entries, root folder pods-repeater/, no vendor/, tests/ or scripts/. SHA-256:

041e6d00fc72b907e9fa244d80f4fdb7931b9c6a51fa9313c26fae98b6b4e1de

Support

Issues are read, but there is no support promise and no release schedule. This is a one-person alpha. The CI badge on the README is the honest statement about what is tested: PHP 7.4 and 8.3 against WordPress 6.8.2 and Pods 3.3.9.1.

Loading