YAML Custom Fields

2.0.0

Changed

• Needs WordPress 6.4 or newer. Older versions weren’t tested. WordPress won’t offer this update to older sites.
• The shared value tick always wins. When “Use the shared value on this page” is ticked, ycf_get_fields() now shows the shared value too. Before, it ignored the tick.
• A page’s own value beats a site detail with the same name.
• ycf_has_field() means “has a value”. An empty text or an empty list is no value. An unticked box or a zero still is.
• Mistakes in a schema are refused when saved. Unknown types (with a “Did you mean…?” hint), the same name twice, names with square brackets, and names the plugin uses itself. Schemas already saved keep working.

New

• Works in the block editor. The fields are a real box now. No Classic Editor plugin needed.
• Block themes. Their templates are listed and can have fields.
• [ycf] shortcode. Show a field without editing the theme. Works in a Shortcode block, a widget or the content.
• REST API. Every page and post has a yaml_cf object. There are routes for site details and collections. You can save through it too, with the same checks as the editor.
• Settings screen. YAML CF → Settings has three choices: page caches, REST API access, and what happens when the plugin is deleted.
• Keep content when the plugin is deleted. A choice on the Settings screen.
• Galleries. Image fields take list: true. Pick many images at once. Reorder by dragging or with the keyboard.
• Search box for big lists. A category or collection field with more than 50 choices becomes a search box. Change the limit with the yaml_cf_picker_threshold filter.
• Sections fold away. Each section shows its first field as its title. A small Collapse all button folds them all.
• Save and add another. For collection items. Saves and opens an empty item.
• Content Check finds left-behind content. Values of removed fields are listed under “Values with no field”, with a button to remove them.
• Warning when a field loses its place. Removing or renaming a field in any schema says which fields are affected.
• yaml_cf_field_value filter. Change any value before the theme gets it.
• Use site details on these pages. The switch is back on the main screen.

Better

• One kind of message. Messages look the same everywhere, with the same icons. Nothing pops up in a corner. Nothing disappears on its own. Results of a switch or button show right next to it, so the page doesn’t jump.
• Accessible messages. Screen readers read each message once, with its kind (“Error:”, “Warning:”). Errors get keyboard focus. Pickers say how many results they found.
• Icons. Headings, columns and buttons have icons. The same thing always has the same icon.
• One field per row in every form.
• The Custom fields box can be folded in the classic editor too, and remembers it. The “not saved yet” line works in the block editor too.
• Main screen. The table doesn’t jump when you switch templates on and off. It works on small screens.
• Faster. Plugin data isn’t loaded on every page view. Values are worked out once per page. Editor scripts only load where there are fields. Editor pages are much smaller.
• Collections scale. Each item has its own database row. The item list has pages of 50.
• No copy of the schema in every post. Schema changes take effect at once.
• “Add section” is drawn by the server, so a new section is the same as one that was already there.
• Clearer texts. Onboarding says the theme needs a line of code. An empty template list says why. Permission messages say what’s really needed.

Fixed

• Removing a field from a schema no longer deletes its content. Put the name back and the content comes back. The same on every screen.
• A tick box can be unticked again.
• Importing no longer empties fields the file doesn’t mention.
• A template with only shared fields now shows the Custom fields box.
• Child themes showed no templates.
• Themes built on singular.php (like Twenty Twenty) couldn’t get page fields.
• ycf_get_field() and ycf_get_fields() could give different values for the same field.
• A typo in a field type showed nothing and then lost the field’s content.
• Two fields could share a name, and one replaced the other.
• Shortcuts like - info: and - section: caused warnings in shared fields and inside sections.
• Fields could be saved into another post when a plugin saved a second post at the same time.
• A form left open too long lost your changes without a word. Now it says so.
• Collection labels didn’t update after a schema change.
• A collection field could show an item from another collection.
• Big collection imports could lose their lock.
• Imports kept image IDs from another site in site details, site parts and shared content.
• ycf_get_image() with a custom size like [300, 200] crashed the page.
• Fields named with digits only (like 2024) could be renamed by some saves.
• The import preview couldn’t tick pages from older export files.
• Content Check offered to delete fields still in use.
• “Empty all fields” left galleries, file lists and pickers filled.
• Import messages didn’t show in the block editor.
• The active filter button in Content Check was unreadable.

Security

• Admin-only actions use their own security token.
• Writers can only get their own post’s schema.
• The category picker checks the user may use that taxonomy.
• Site details no longer leak to visitors through a page’s REST data.
• Picker labels are inserted as text, not HTML.
• CSS cleaning repeats until nothing is left to remove.
• Schemas over 256 KB are refused.

Removed

• Nine old background requests nothing used anymore.

Updated

• Tested with WordPress 7.1.

1.2.9

• UPDATED: WordPress 7.0 Compatibility – Confirmed compatibility and updated “Tested up to”
• FIX: Import JSON Parsing – Fixed “Invalid JSON: Syntax error” when importing settings, page data, or data objects whose field values contain HTML/rich-text content, by removing an errant sanitize_textarea_field() call that corrupted the JSON payload before parsing

1.2.8

• NEW: Multiple File Uploads – File fields now support list: true to attach multiple files, with a dedicated admin UI for adding and removing files
• UPDATED: ycf_get_file() for Lists – When list: true is set, ycf_get_file() returns an array of file-data arrays instead of a single one
• IMPROVED: Attachment Validation – Validation now checks each attachment ID in file/image list fields individually

1.2.7

• FIX: Data Object Fields in Blocks/Objects – Fixed data_object fields not rendering correctly when nested inside block or object fields by adding recursive data object collection in AssetManager and DataObjectController
• FIX: Attachment Data Validation – Fixed attachment validation logic to correctly handle the case where a schema exists but has no image/file fields, preventing numeric values from being incorrectly cleared
• FIX: Import Schema Parsing – Fixed data object import to parse YAML schema before validating attachment data, ensuring attachment IDs are preserved correctly during import

1.2.6

• FIX: Code Field HTML Preservation – Code fields now use base64 encoding with a marker prefix to preserve HTML/JavaScript/CSS code exactly as entered, preventing WordPress sanitization from stripping tags
• FIX: Code Field Re-save Protection – Already-encoded code fields are now preserved on re-save even if schema detection fails, preventing data loss on page refresh
• NEW: Auto-decode on Frontend – Code field values are automatically decoded when retrieved via yaml_cf_get_field() and related functions

1.2.5

• FIX: Code Field Sanitization – Changed filter from FILTER_SANITIZE_FULL_SPECIAL_CHARS to FILTER_UNSAFE_RAW in postRaw() to preserve raw data for schema-aware sanitization, fixing HTML entities being encoded before code fields could be properly identified