Back up first. Needs WordPress 6.4+. The shared value tick now wins in ycf_get_fields(), and a page value beats a site detail with the same name. Schemas with mistakes are refused. The database is tidied once, by itself.<\/p>","1.2.6":"
Important fix for code fields. HTML\/JavaScript\/CSS code is now properly preserved using base64 encoding. Re-save any code fields that previously had content stripped.<\/p>","1.2.5":"
Bug fix for code field sanitization. Code fields now preserve raw content correctly without premature HTML entity encoding.<\/p>","1.2.4":"
Asset folder reorganization for better WordPress.org compliance. All functionality remains unchanged.<\/p>","1.2.3":"
Bug fix for dynamic block fields. Taxonomy, post type, and data object fields now render correctly when adding blocks dynamically.<\/p>","1.2.2":"
Important security update with nonce verification fixes. Updated to PHP 8.1+ requirement with Symfony 6.4 compatibility.<\/p>","1.2.1":"
Fixes for export\/import functionality and template global field handling. Recommended update for better data portability.<\/p>","1.2.0":"
Major feature update introducing Template Global Fields for shared default values across posts using the same template.<\/p>","1.1.0":"
Code quality improvements, consolidated Export\/Import page, and enhanced security. All functionality remains backwards compatible.<\/p>","1.0.0":"
Initial release of YAML Custom Fields.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3717169,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3430736,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3717169,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3717169,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.3","1.2.4","1.2.5","1.2.6","1.2.7","1.2.8","1.2.9","2.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3717169,"resolution":"1","location":"assets","locale":"","width":2880,"height":1920},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3717169,"resolution":"2","location":"assets","locale":"","width":2880,"height":1920},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3717169,"resolution":"3","location":"assets","locale":"","width":2880,"height":1920},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3717169,"resolution":"4","location":"assets","locale":"","width":2880,"height":1920},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3717169,"resolution":"5","location":"assets","locale":"","width":2880,"height":1920}},"screenshots":{"1":"The YAML CF screen, with a switch per template and the status of its fields.","2":"The schema editor for a template.","3":"The schema editor for a site part, like the header.","4":"The content of a site part.","5":"The Documentation page, written in plain words."}},"plugin_section":[],"plugin_tags":[529,2010,2235,1117,31642],"plugin_category":[55],"plugin_contributors":[253140],"plugin_business_model":[],"class_list":["post-259154","plugin","type-plugin","status-publish","hentry","plugin_tags-content","plugin_tags-custom-fields","plugin_tags-fields","plugin_tags-schema","plugin_tags-yaml","plugin_category-seo-and-marketing","plugin_contributors-starbist","plugin_committers-starbist"],"banners":{"banner":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/banner-772x250.png?rev=3717169","banner_2x":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/banner-1544x500.png?rev=3717169","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/icon-128x128.png?rev=3717169","icon_2x":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/icon-256x256.png?rev=3430736","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/screenshot-1.png?rev=3717169","caption":"The YAML CF screen, with a switch per template and the status of its fields."},{"src":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/screenshot-2.png?rev=3717169","caption":"The schema editor for a template."},{"src":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/screenshot-3.png?rev=3717169","caption":"The schema editor for a site part, like the header."},{"src":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/screenshot-4.png?rev=3717169","caption":"The content of a site part."},{"src":"https:\/\/ps.w.org\/yaml-custom-fields\/assets\/screenshot-5.png?rev=3717169","caption":"The Documentation page, written in plain words."}],"raw_content":"\n
YAML Custom Fields adds boxes to fill in on pages, like \"Headline\", \"Team photo\" or \"Event date\". Writers fill them in. The website shows them in the right place.<\/p>\n\n
You list the fields of each page template in a short text, called a schema. Each field takes a few lines.<\/p>\n\n
Click Create schema<\/strong> and list the fields:<\/p>\n\n fields:<\/p>\n\n Open a page that uses the template. The fields are in a \"Custom fields\" box. In the block editor it's below the content. In the classic editor it's below the title.<\/p><\/li>\n Show each field in the theme with one line:<\/p>\n\n<\/li>\n<\/ol>\n\n The Documentation<\/strong> page in the plugin explains every step in plain words.<\/p>\n\n The full guide is on the plugin's Documentation page. Here's the short version.<\/p>\n\n Each function also has a long name starting with Always escape what you print: YAML Custom Fields doesn't collect or send any data. Everything stays in your WordPress database.<\/p>\n\n For a ZIP file, use Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/p>\n\n Everything else is included.<\/p>\n\n\n A short list of the fields a page gets. Each field has a name, a label and a type. It's written in YAML, a simple text format with one setting per line.<\/p><\/dd>\n Writers don't. They only fill in fields. To show fields on the website, the theme needs one line per field. The Copy code<\/strong> button next to each field copies that line for you.<\/p><\/dd>\n Yes, classic and block themes. A child theme is scanned together with its parent, so the parent's templates are listed too.<\/p>\n\n Block themes have no template files to edit. Use the Yes. The fields are in a \"Custom fields\" box below the content. You don't need the Classic Editor plugin.<\/p><\/dd>\n Yes, the WordPress REST API. Every page and post has a Posts, pages and other public content types, like an \"Events\" type from a theme or plugin.<\/p><\/dd>\n Only administrators change schemas and settings. Writers fill in fields on posts they may edit.<\/p><\/dd>\n Nothing is lost. The content stays.<\/p><\/dd>\n\n
Developer Documentation<\/h3>\n\n
Functions<\/h4>\n\n
ycf_get_field( 'name' ) \/\/ One field\nycf_get_field( 'name', 42 ) \/\/ A field of another post\nycf_get_field( 'name', 'partial:header.php' ) \/\/ A site part\nycf_get_field( 'title', null, $section ) \/\/ A field inside a section\nycf_get_fields() \/\/ All fields\nycf_has_field( 'name' ) \/\/ Does it have a value?\nycf_get_image( 'name', null, 'large' ) \/\/ Image: id, url, alt, title, caption, width, height\nycf_get_file( 'name' ) \/\/ File: id, url, path, filename, filesize, mime_type, title\nycf_get_term( 'name' ) \/\/ Category or tag (WP_Term)\nycf_get_post_type( 'name' ) \/\/ Content type (WP_Post_Type)\nycf_get_data_object( 'name' ) \/\/ An item from a collection\nycf_get_data_objects( 'short-name' ) \/\/ Every item in a collection\nycf_get_global_field( 'name' ) \/\/ One site detail\nycf_get_global_fields() \/\/ All site details\n<\/code><\/pre>\n\nyaml_cf_<\/code>.<\/p>\n\nesc_html()<\/code> for text, esc_url()<\/code> for links, wp_kses_post()<\/code> for formatted text. Code fields print as they are.<\/p>\n\nShortcode<\/h4>\n\n
[ycf field=\"headline\"]\n[ycf field=\"hero\" size=\"large\"]\n[ycf field=\"phone\" source=\"site\"]\n[ycf field=\"subtitle\" default=\"Coming soon\"]\n<\/code><\/pre>\n\nWhere data is stored<\/h4>\n\n
\n
_yaml_cf_data<\/code><\/li>\nyaml_cf_schemas<\/code><\/li>\nyaml_cf_partial_data<\/code><\/li>\nyaml_cf_template_global_schemas<\/code> and yaml_cf_template_global_data<\/code><\/li>\nyaml_cf_global_schema<\/code> and yaml_cf_global_data<\/code><\/li>\nyaml_cf_data_object_types<\/code>. Each item has its own option, plus a small index per collection. Read them with ycf_get_data_objects()<\/code>.<\/li>\n<\/ul>\n\nPrivacy Policy<\/h3>\n\n
Third-Party Libraries<\/h3>\n\n
\n
\n
Credits<\/h3>\n\n
\n
Support<\/h3>\n\n
\n
\n
Requirements<\/h4>\n\n
\n
\n
What is a schema?<\/h3><\/dt>\n
Do I need to code?<\/h3><\/dt>\n
Does it work with any theme?<\/h3><\/dt>\n
[ycf field=\"name\"]<\/code> shortcode in a Shortcode block.<\/p><\/dd>\nDoes it work with the block editor?<\/h3><\/dt>\n
Is there an API?<\/h3><\/dt>\n
yaml_cf<\/code> object. There are also routes for site details and collections. The Documentation page has the details.<\/p><\/dd>\nWhich content types are supported?<\/h3><\/dt>\n
Who can change the setup?<\/h3><\/dt>\n
What happens when I turn the plugin off?<\/h3><\/dt>\n
What happens when I delete the plugin?<\/h3><\/dt>\n