dirlikdesigns

<p>Easy to use XML feed importer with the ability to map feed items onto (custom) posts and their meta fields.</p>
<h4>Usage Notes</h4>
<ul>
<li>The feeds are managed (added / edited / deleted) like normal posts.</li>
<li>To import a new feed, you must first save the post with at least the title and URL fields filled in.
<ul>
<li>This is because the importer downloads a copy of the feed and works with that copy.</li>
<li>If you try to import before the feed is saved, the importer has no copy to work with yet.</li>
</ul>
</li>
</ul>
<h4>Form explanation</h4>
<ul>
<li>Import
<ul>
<li>It’s the first field in the form, but the last step.</li>
<li>There is no cancel button, so once you click the ‘import’ button, you can only refresh (or move away from) the page to cancel the import.</li>
<li>The import is done 10 feed items at a time, the progress is shown under the import button.</li>
<li>The import sends ajax requests until the import is done at which point the spinner stops spinning and the progress message shows ‘n posts imported’</li>
</ul>
</li>
<li>URL
<ul>
<li>the feed url</li>
</ul>
</li>
<li>Required Fields (optional)
<ul>
<li>comma separated list of (custom) post fields</li>
<li>if a field in this list has no mapping, than the import will fail</li>
<li>if the mapping of a field in this list turns out to be empty, than the corresponding feed item is skipped.</li>
</ul>
</li>
<li>Unique Fields (optional)
<ul>
<li>comma separated list of (custom) post fields</li>
<li>unique fields are not implicitly required</li>
<li>skips a feed item if a field with this value already exists.</li>
</ul>
</li>
<li>CSV delimiter (optional)
<ul>
<li>if this field is empty, the plugin assumes the URL links to a XML file</li>
<li>if this field is non-empty, the plugin assumes the URL links to a CSV file, with the given value as the delimiter</li>
<li>a CSV file will be converted to XML, so the further usage of the plugin remains the same.</li>
</ul>
</li>
<li>Select root
<ul>
<li>select the path to the items that should be mapped</li>
<li>i.e. you want to import products into your woocommerce installation</li>
<li>xml : <products> <product></product> … <product></product> </products></li>
<li>then the root should be /products/product</li>
<li>you can use the plus and minus buttons to go a level up or down</li>
<li>the select boxes show the possible paths for a given level</li>
<li>Click the ‘Select’ button to confirm the root</li>
<li>The XML area should fill up with the first item that matches root.</li>
</ul>
</li>
<li>Select post field
<ul>
<li>the first select box shows the registered post types and Taxonomies.</li>
<li>the second select box shows the corresponding fields. (Even columns like ID which you probably shouldn’t set manually)</li>
<li>many of the fields are always the same and correspond to the columns in the <code>wp_posts</code> table in the database, but the meta fields can differ.</li>
<li>the plugin needs at least one existing object of the selected post type to find these meta fields.</li>
<li>the meta fields are based on the first post of the selected post type it finds.</li>
</ul>
</li>
<li>Map
<ul>
<li>this shows the current mapping</li>
<li>if you have selected a mapping, it can be removed with the ‘x’ at the right hand side</li>
<li>if you are satisfied with the mappings, click ‘Save map’</li>
</ul>
</li>
<li>XML
<ul>
<li>once you have selected a root, the first xml item at this path will be shown here.</li>
<li>click anywhere on the XML to get the corresponding paths</li>
<li>the selected path will appear above the colourful XML</li>
<li>if the path contains attributes, they will appear as selectboxes</li>
<li>if the desired path depends on a sibling in the XML, follow these instruction:</li>
<li>some XML looks like this ..<parent> <key>name</key><value>Dirlik<value></parent> …</li>
<li>in this case, click on the value tag in the XML and the corresponding path appears: ‘Assign path: …/parent/value’</li>
<li>now click on ‘parent’ in the path and 2 new selectboxes appear and an ‘Add to attribute list’ button</li>
<li>in our example you would select ‘key’ in the first selectbox and ‘name’ in the second</li>
<li>click ‘Add to attribute list’ and the path changes accordingly</li>
<li>once you see the path you want, click the ‘Add to map’ button.</li>
<li>The Map will now reflect that the path you chose is mapped om the selected post field.</li>
</ul>
</li>
</ul>
<h3>WARNING</h3>
<p>This plugin is new and requires more testing. If you decide to use the plugin, please make a backup of your database first.<br />
Once you click the <code>import</code> link, there is no cancel button, you can refresh (or move away from) the page to cancel the import.<br />
On your first go, try a smaller feed to make sure you mapped it right.</p>
<h3>TODO</h3>
<ul>
<li>add row actions</li>
<li>define type of imported value (now images only work with _thumbnail_id meta value)</li>
</ul>


XML Import

XML feed importer with ability to map feed items onto (custom) posts.

starbist

<p>YAML Custom Fields allows you to define structured content schemas with an intuitive interface and ACF-like template functions. Perfect for theme developers who want flexible, schema-based content management without the complexity.</p>
<h4>Features</h4>
<ul>
<li>Define YAML schemas for page templates and template partials</li>
<li>15+ field types including string, rich-text, images, blocks, taxonomies, data objects, and more</li>
<li>Easy-to-use admin interface for managing schemas and data</li>
<li><strong>Three-level data hierarchy:</strong>
<ul>
<li>Per-page data for individual customization (stored in post meta)</li>
<li>Per-template global data shared across all posts using the same template</li>
<li>Site-wide global data for partials like headers and footers</li>
</ul>
</li>
<li><strong>Per-field global/local toggle:</strong> Each field can independently use template global data or page-specific data</li>
<li><strong>Visual dual-field interface:</strong> See both template global and page-specific values side-by-side</li>
<li>Data Objects for managing structured, reusable data (universities, companies, etc.)</li>
<li>Data Validation page for reviewing imported content</li>
<li>Consolidated Export/Import page for all data types (settings, page data, data objects)</li>
<li>Simple template functions with ACF-like syntax and auto-merge behavior</li>
<li>Administrator-only access for security</li>
<li>Clean uninstall removes all database records</li>
<li>WordPress Coding Standards compliant</li>
</ul>
<h4>Supported Field Types</h4>
<ul>
<li><strong>String</strong> – Single-line text with min/max length</li>
<li><strong>Text</strong> – Multi-line textarea</li>
<li><strong>Rich Text</strong> – WordPress WYSIWYG editor</li>
<li><strong>Code</strong> – Code editor with syntax highlighting</li>
<li><strong>Boolean</strong> – Checkbox for true/false values</li>
<li><strong>Number</strong> – Number input with min/max constraints</li>
<li><strong>Date</strong> – Date picker with optional time</li>
<li><strong>Select</strong> – Dropdown with single/multiple selection</li>
<li><strong>Taxonomy</strong> – WordPress categories, tags, or custom taxonomies with single/multiple selection</li>
<li><strong>Post Type</strong> – Dropdown to select registered post types (Post, Page, custom post types)</li>
<li><strong>Data Object</strong> – Reference to structured data objects managed independently (universities, companies, team members, etc.)</li>
<li><strong>Image</strong> – WordPress media uploader for images</li>
<li><strong>File</strong> – WordPress media uploader for any file</li>
<li><strong>Object</strong> – Nested group of fields</li>
<li><strong>Block</strong> – Repeatable blocks for flexible page builders</li>
</ul>
<h4>Usage Example</h4>
<p>In your theme template:</p>
<pre><code><?php
$hero_title = ycf_get_field('hero_title');
$hero_image = ycf_get_image('hero_image', null, 'full');
$category = ycf_get_term('category');
$post_type = ycf_get_post_type('content_type');
$university = ycf_get_data_object('university');
$features = ycf_get_field('features');
?>

<div class="hero">
  <?php if ($hero_image): ?>
    <img src="<?php echo esc_url($hero_image['url']); ?>" alt="<?php echo esc_attr($hero_image['alt']); ?>">
  <?php endif; ?>
  <h1><?php echo esc_html($hero_title); ?></h1>
  <?php if ($category): ?>
    <span class="category"><?php echo esc_html($category->name); ?></span>
  <?php endif; ?>
  <?php if ($university): ?>
    <p><?php echo esc_html($university['name']); ?></p>
  <?php endif; ?>
</div>
</code></pre>
<h3>Developer Documentation</h3>
<h4>Template Functions</h4>
<p><strong>Get a single field value:</strong></p>
<pre><code>$value = ycf_get_field('field_name');
$value = ycf_get_field('field_name', 123); // Specific post ID
$value = ycf_get_field('logo', 'partial:header.php'); // From partial
$value = ycf_get_field('title', null, $block); // From block context
</code></pre>
<p><strong>Get image field with details:</strong></p>
<pre><code>$image = ycf_get_image('field_name', null, 'full');
$image = ycf_get_image('field_name', 123, 'thumbnail'); // Specific post ID
$image = ycf_get_image('icon', null, 'medium', $block); // From block context

// Returns: array('id', 'url', 'alt', 'title', 'caption', 'description', 'width', 'height')
</code></pre>
<p><strong>Get file field with details:</strong></p>
<pre><code>$file = ycf_get_file('field_name', null);
$file = ycf_get_file('field_name', 123); // Specific post ID
$file = ycf_get_file('document', null, $block); // From block context

// Returns: array('id', 'url', 'path', 'filename', 'filesize', 'mime_type', 'title')
</code></pre>
<p><strong>Get taxonomy field (term or terms):</strong></p>
<pre><code>$term = ycf_get_term('field_name', null);
$term = ycf_get_term('field_name', 123); // Specific post ID
$term = ycf_get_term('category', null, $block); // From block context

// Returns: WP_Term object or array of WP_Term objects (for multiple selection)
</code></pre>
<p><strong>Get post type field:</strong></p>
<pre><code>$post_type = ycf_get_post_type('field_name', null);
$post_type = ycf_get_post_type('field_name', 123); // Specific post ID
$post_type = ycf_get_post_type('content_type', null, $block); // From block context

// Returns: WP_Post_Type object or null
</code></pre>
<p><strong>Get data object field:</strong></p>
<pre><code>$university = ycf_get_data_object('field_name', null);
$university = ycf_get_data_object('field_name', 123); // Specific post ID
$university = ycf_get_data_object('university', null, $block); // From block context

// Returns: Array with data object entry fields or null
</code></pre>
<p><strong>Get all entries of a data object type:</strong></p>
<pre><code>$all_universities = ycf_get_data_objects('universities');
foreach ($all_universities as $entry_id => $university) {
    echo esc_html($university['name']);
}

// Returns: Array of all entries for the specified data object type
</code></pre>
<p><strong>Get all fields:</strong></p>
<pre><code>$fields = ycf_get_fields();
$fields = ycf_get_fields(123); // Specific post ID
$fields = ycf_get_fields('partial:footer.php'); // From partial
</code></pre>
<p><strong>Check if field exists:</strong></p>
<pre><code>if (ycf_has_field('hero_title')) {
    echo ycf_get_field('hero_title');
}
</code></pre>
<p><strong>Working with Block fields:</strong></p>
<pre><code>$blocks = ycf_get_field('features');

if (!empty($blocks)) {
    foreach ($blocks as $block) {
        // Access nested fields using context_data parameter
        $title = ycf_get_field('title', null, $block);
        $icon = ycf_get_image('icon', null, 'thumbnail', $block);
        $category = ycf_get_term('category', null, $block);

        echo '<h3>' . esc_html($title) . '</h3>';
        if ($icon) {
            echo '<img src="' . esc_url($icon['url']) . '">';
        }
        if ($category) {
            echo '<span>' . esc_html($category->name) . '</span>';
        }
    }
}
</code></pre>
<h4>Sample YAML Schema</h4>
<pre><code>fields:
  - name: hero_title
    label: Hero Title
    type: string
    required: true
    options:
      maxlength: 100
  - name: hero_image
    label: Hero Image
    type: image
  - name: category
    label: Category
    type: taxonomy
    options:
      taxonomy: category
  - name: tags
    label: Tags
    type: taxonomy
    multiple: true
    options:
      taxonomy: post_tag
  - name: content_type
    label: Content Type
    type: post_type
  - name: university
    label: University
    type: data_object
    options:
      object_type: universities
  - name: features
    label: Features
    type: block
    list: true
    blockKey: type
    blocks:
      - name: feature
        label: Feature Block
        fields:
          - name: title
            label: Title
            type: string
          - name: icon
            label: Icon
            type: image
          - name: description
            label: Description
            type: text
</code></pre>
<h4>Working with Partials</h4>
<p>For custom partials, add the @ycf marker in the file header:</p>
<pre><code><?php
/**
 * Custom Navigation Partial
 * @ycf
 */
</code></pre>
<p>Then click “Refresh Template List” in the YAML Custom Fields admin page.</p>
<h4>Template Global Fields</h4>
<p>Template Global Fields allow you to define default values that are shared across all posts using the same template, while still allowing individual posts to override specific fields.</p>
<p><strong>Setting up Template Global:</strong></p>
<ol>
<li>Go to <strong>YAML Custom Fields</strong> admin page</li>
<li>Enable YAML for your template (e.g., page.php)</li>
<li>Click <strong>Add Template Global</strong> to define the template global schema</li>
<li>Define fields that should have shared default values</li>
<li>Click <strong>Manage Template Global Data</strong> to set the default values</li>
</ol>
<p><strong>Using Template Global in Posts:</strong></p>
<p>When editing a post that uses a template with Template Global fields, you’ll see a dual-field interface for each field:</p>
<ul>
<li><strong>Template Global (All Pages)</strong> – Read-only display showing the default value (with Edit link)</li>
<li><strong>Page-Specific Value</strong> – Editable field for this post only</li>
<li><strong>Checkbox</strong> – “Use template global for this field” – Toggle per field</li>
</ul>
<p><strong>Benefits:</strong></p>
<ul>
<li><strong>Consistency:</strong> Set default values once, use across all posts</li>
<li><strong>Flexibility:</strong> Override any field on any post individually</li>
<li><strong>Clarity:</strong> See both global and local values side-by-side</li>
<li><strong>Efficiency:</strong> Update template global to affect all posts at once</li>
</ul>
<p><strong>Data Priority (when using template functions):</strong></p>
<p>When a field uses template global, <code>ycf_get_field()</code> returns data in this priority order:</p>
<ol>
<li>Page-specific value (if “use template global” is unchecked)</li>
<li>Template global value (if “use template global” is checked)</li>
<li>Site-wide global value (if template has site-wide global enabled)</li>
<li>null (if no value exists)</li>
</ol>
<h4>Data Storage</h4>
<ul>
<li><strong>Page/Post data:</strong> Stored in post meta with key <code>_yaml_cf_data</code></li>
<li><strong>Template Global preferences:</strong> Stored in post meta with key <code>_yaml_cf_use_template_global_fields</code> (per-field array)</li>
<li><strong>Template Global schemas:</strong> Stored in options table with key <code>yaml_cf_template_global_schemas</code></li>
<li><strong>Template Global data:</strong> Stored in options table with key <code>yaml_cf_template_global_data</code></li>
<li><strong>Site-wide global schema:</strong> Stored in options table with key <code>yaml_cf_global_schema</code></li>
<li><strong>Site-wide global data:</strong> Stored in options table with key <code>yaml_cf_global_data</code></li>
<li><strong>Partial data:</strong> Stored in options table with key <code>yaml_cf_partial_data</code></li>
<li><strong>Schemas:</strong> Stored in options table with key <code>yaml_cf_schemas</code></li>
<li><strong>Data Object Types:</strong> Stored in options table with key <code>yaml_cf_data_object_types</code></li>
<li><strong>Data Object Entries:</strong> Stored in options table with keys <code>yaml_cf_data_object_entries_{type_slug}</code></li>
</ul>
<h3>Privacy Policy</h3>
<p>YAML Custom Fields does not collect, store, or transmit any user data outside of your WordPress installation. All data is stored locally in your WordPress database.</p>
<h3>Third-Party Libraries</h3>
<p>This plugin includes the following third-party libraries:</p>
<ul>
<li><strong>Symfony YAML Component</strong> (v6.4) – Licensed under MIT License (GPL-compatible)
<ul>
<li>Homepage: https://symfony.com/components/Yaml</li>
<li>License: https://github.com/symfony/yaml/blob/7.3/LICENSE</li>
</ul>
</li>
</ul>
<h3>Credits</h3>
<ul>
<li>Author: <a href="https://www.silvestar.codes" rel="nofollow ugc">Silvestar Bistrovic</a></li>
</ul>
<h3>Support</h3>
<p>For documentation, examples, and support, visit:<br />
* <a href="https://github.com/maliMirkec/yaml-custom-fields" rel="nofollow ugc">Plugin Documentation</a><br />
* <a href="https://github.com/maliMirkec/yaml-custom-fields/issues" rel="nofollow ugc">Report Issues</a></p>


YAML Custom Fields

A WordPress plugin for managing YAML frontmatter schemas in theme templates and partials.

XML Import vs YAML Custom Fields