Native Custom Fields – Custom Content Types and Meta Fields

Changelog

1.4.2

• Fixed: The field schema of the abilities accepted only a string or an array as default, so an AI agent giving a number field a numeric default (10) or a toggle field a boolean default (true) had the call rejected by schema validation. default now also accepts numbers and booleans. The value is still sanitized according to the field type, and string defaults keep working.
• Updated: The field schema documentation lists the accepted default types.

1.4.1

• Added: Read-only abilities to inspect the current configuration: list-post-types, get-post-type, list-taxonomies, get-taxonomy, list-post-meta-fields, get-post-meta-fields, list-term-meta-fields, get-term-meta-fields, get-user-meta-fields, list-options-pages and get-options-page. The get-* abilities return the configuration in the same shape the matching update-* / save-* abilities accept, so an AI agent can read a configuration, change it and save it back. Each result also reports builder_state, which shows whether the builder screens have data to load.
• Fixed: An options page created through the create-options-page, update-options-page and save-options-page-fields abilities was listed and rendered correctly, but its Edit and Fields screens in the Options Page Builder opened empty. The abilities stored the builder form state under the wrong option name, and never stored it at all for the fields. They now write it where the builder reads it. Re-run the abilities for an existing page to repair it.
• Fixed: The abilities also wrote the options page builder values into the page’s own settings option. That value is no longer written there. An existing native_custom_fields_create_options_page entry in such an option can be removed.
• Fixed: Saving the fields of an options page read the options pages configuration instead of the fields configuration as its base, so the configuration of other options pages could be copied into the stored fields configuration.
• Updated: Sections and fields saved through the abilities now carry the same base settings and dependency structure as those saved from the builder, so the builder loads them the same way. This affects the post meta, term meta, user meta and options page field abilities.
• Fixed: AI agents creating a notice field through the abilities put the message in the label, so the notice rendered empty. The ability schema did not list notice, heading or text_highlight or say where their content goes. The schema now documents it (children for notice, text for heading and text highlight), and a message given as message, or only in the label, is mapped to the right property. A notice that already exists with its text in the label needs the message entered in the builder.
• Updated: Ability documentation now covers the read-only abilities and the notice, heading and text_highlight field types.

1.4.0

• Added: The combobox field now searches server side when its options come from a dynamic token. What is typed in the field is sent to the REST API as the search argument, so collections larger than a single REST response stay fully reachable. Previously the typed text only filtered the records that had already been fetched.
• Added: The record matching a stored value is now fetched on its own, so a saved selection keeps its label even when it is not part of the current option list or search results.
• Fixed: A per_page above 100, or -1, made the whole request fail with rest_invalid_param and the field rendered no options at all. Such values are now capped at the REST maximum of 100, and per_page=all is accepted as a spelling of the same thing.
• Fixed: {{menus}} raised a TypeError on any navigation menu without a title.
• Fixed: Combining several dynamic tokens could list the same record more than once.
• Removed: The {{roles}} token from the options help text and the documentation. It was never implemented and always resolved to an empty list.
• Updated: The help text of the options field, which now documents the {{posts?type=slug}} pattern for querying a custom post type. That pattern was supported but undocumented, so there was no way to populate a field from a custom post type without reading the source. The text is also grouped into sections and rendered with its line breaks intact.
• Updated: Corrected two wrong parameter examples in the options help text: the users endpoint takes roles (plural, role slugs) rather than role, and author takes a user ID rather than a login name.
• Added: A “Dynamic Options” documentation page covering the available tokens, their parameters, the REST item limits, and server-side search. Select, radio, combobox, toggle group and token field documentation now links to it.
• Updated: Token field documentation now states that suggestions is a literal list and does not support the {{token}} syntax.

1.3.9

• Added: Sub-fields for repeater and group fields can now be defined through the field abilities (save-post-meta-fields, save-term-meta-fields, save-user-meta-fields, save-options-page-fields) using the new fields property on a field definition. Up to two levels of nesting are supported. Previously only the container field could be created and its contents had to be added in the field builder.
• Updated: Aligned the editor controls with the WordPress 7.1 component changes, so no deprecation notices are logged on 7.1.
• Removed: The “Size” option from the border, border box and font size field settings. The underlying size prop is deprecated and has no effect as of WordPress 7.1. A value stored by an earlier version is now ignored instead of being passed to the control.
• Removed: The “Large” (__unstable-large) choice from the input field “Size” setting. The remaining choices are default, small and compact.
• Removed: The __next40pxDefaultSize prop from every control. The 40px default height rollout is complete in WordPress 7.1 and the prop no longer has any effect.
• Updated: Border, border box, font size and input control documentation to match the available settings.
• Added: Missing “Requires at least” header in readme.txt and the plugin file. The plugin already assumed WordPress 7.0 as its minimum, but neither header declared it.

1.3.8

• Added: Missing “Tested up to: 7.1” tag in readme.txt

1.3.7

• Bumped WordPress tested-up-to version 7.1

1.3.6

Fixed: Repeater, group, file and multiple select fields were registered with the wrong meta type, so register_meta raised a “you must specify the schema for each array item” notice and dropped the meta from the REST API.
Fixed: The native_custom_fields_register_post_meta_type and native_custom_fields_register_term_meta_type filters received the meta key instead of the meta type as their filtered value.
Added: Array and object meta are now registered with a REST schema generated from the field configuration.
Updated: Hooks documentation now describes how the meta type is derived and when a custom schema is required.

1.3.5

Fixed: Repeater default values were not rendered on options pages until the section was reset.
Fixed: “Reset All” on an options page cleared repeater defaults instead of restoring them.
Fixed: Array defaults were flattened to an empty string for fields registered through the Abilities API.
Updated: Repeater control documentation now covers the default parameter.

1.3.4

Fixed: Post type archive did not work when “Has Archive” was enabled without a custom archive slug.
Fixed: Query var fell back incorrectly when no custom query var slug was provided.
Fixed: Endpoint mask normalization broke post types registered with rewrite disabled.
Updated: Post type template field now documents the correct block array format.

1.3.3

Fixed: Missing required field controls in Post Meta, Term Meta, User Meta and TreView forms.

1.3.2

Added: ncf_sanitize_field_value hook to override field sanitization.

1.3.1

Fixed: Sanitization issue for multine line text field.

1.2.8

• Fix: Boot method for external usage in another plugins.

1.2.7

• Add: Singleton pattern intp DI Container
• Fix: Boot method for external usage in another plugins.
• Move: Hooks in the services into controllers

1.2.6

• Add: Static boot method for external usage in another plugins.
• Test: Added Composer package capability.
• Test: Added GitHub Actions workflow for testing.

1.2.3

• Add: Into Packagist repository

1.2.0

• Add: Parent Slug parameter into options page

1.0.9

• Add: Annotations parameter into abilities

1.0.6

• Fixed: Auto generate empty labels for post types and taxonomies in Abilities.

1.0.5

• Moved: Pro features into free plugin: Import&Export Module & Options Page Builder & AI Integration.

1.0.4

• Added: Auto generate empty labels for post types.
• Added: Auto generate empty labels for taxonomies.

1.0.3

• Tested with WordPress 7.0

1.0.2

• Updated: Readme.txt
• Updated: Dashboard screen

1.0.1

• Updated: Add PHP-DI Version to 7.1.1
• Updated: Rest enpoint permissions in PostMetaController and OptionsController

1.0.0

• Initial public release