dirlikdesigns

Easy to use XML feed importer with the ability to map feed items onto (custom) posts and their meta fields.
<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>
This plugin is new and requires more testing. If you decide to use the plugin, please make a backup of your database first. 
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. 
On your first go, try a smaller feed to make sure you mapped it right.
<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.

Paras Ralhan

Effortless custom fields is the super easy, most beautiful, and the least confusing custom fields plugin you have seen so far.
It offers 32 field types including posts-dropdown, taxonomy-dropdown, users-dropdown, menus-dropdown, sidebars-dropdown, multiple-images, multiple-files, and many more.
It allows you to create fields for all post types, taxonomies, all setting pages, customizer, and user profiles.
<h3>How it makes your life 5 times easier :</h3>
  
It lets you save all your time & energy that go in “confusion, learning, organizing, waiting, and styling” with other custom field plugins. 
  
––––––––––––––––––––––––––––––––––––––
<h3>Create your custom fields in 3 simple steps :</h3>
<ol>
<li>Choose Fields’ Destination: Choose where you want to create your fields: for posts, pages, categories, customizer, or profile, etc… Every location has its own set of fields. 
 </li>
<li>Select Field Type: Out of 32 types of fields, decide the type you want. Fields’ visuals, search, and logical categorization help you decide quickly. 
 </li>
<li>Enter Field’s Data: Just fill the data related to field: label, key, placeholder, description, default value, etc… You can also control field’s visibility with visibility filters. 
 </li>
</ol>
<iframe loading="lazy" title="Effortless Custom Fields — 3 Steps" width="750" height="422" src="https://www.youtube.com/embed/EDRot_n2BuU?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<h3>Amazing new possibilities, you’ve never seen before :</h3>
<ul>
<li>You can now organize your fields with incredible ease.</li>
<li>Its beautiful and minimal design, and how elegantly it responds to actions gives an absolute delight.</li>
<li>We value your time, so there are no unnecessary ajax-calls and page-loads.</li>
<li>It demands almost zero learning. Using it is as easy as breathing. Everything just makes sense. 
 </li>
</ul>
––––––––––––––––––––––––––––––––––––––
<h3>More reasons to love it:</h3>
<ol>
<li>Only one function to learn — “effcf_get” : This is the only function you need to get the field value in the frontend. If a single function can handle it, why to offer more. Offering more functions lead to more confusion, more complexity, and more effort—exact opposite of our core values. How big deal it can be to learn using just one function. Even for learning this, you don’t need to go anywhere else; code is provided where you create the field itself. 
 </li>
<li>Short and simple documentation : In a race to give more features than their competitors, companies end up making softwares so complex that at most times user struggles. Instead of putting efforts on design and ease of use, they try to explain everything in documentation. But ECF is different. It won’t require you to refer documentation often—everything is clear and obvious. Documentation is, however, created for ECF but is kept super simple and small. It only covers things that are not obvious. 
 </li>
<li>Fields management is not a pain anymore : In ECF, you have one place to create or manage fields for one location (let’s say post type = post) and a completely separate place for another location (post type = page), and so on. No field sharing accross locations—direct one to one mapping. Everything neatly organized. No matter how many fields you need to manage for each location, you’ll do it with ease and confidence. 
 </li>
<li>Easily copy fields to other locations : In ECF, each location own its independent set of fields. If you want similar fields—that you already created for one location—for other locations, you can use this option. 
Follow the steps: 
  
   1) Select fields you want to copy. 
   2) Choose action “Copy to other locations.” 
   3) Choose locations where you want these fields. 
   4) Click “Copy Selected Fields to Selected Locations” button. 
 </li>
<li>Fields are trashed before permanent deletion : Now, you won’t be interrupted with most irritating prompt in most software: “Are you sure you want to delete…?” Whenever you press delete on a field or field-group, it will safely move to trash—living there as long as you want. Whenever you feel the need, you can delete all or some of them in one go—by selecting and deleting. 
 </li>
<li>You can disable fields, groups, tabs, etc… : Disabling fields, groups, tabs, etc… is a great option to have. if you are unsure of an entity’s (field, tab, section, repeater section) future need, don’t delete it, disable it. It will hide disabled entities for your clients but remain in place to be shown whenever needed. You can think of this feature as a temporary deletion.</li>
</ol>
  
––––––––––––––––––––––––––––––––––––––
<h3>Links</h3>
<ul>
<li><a href="https://ecfwp.com/" rel="nofollow ugc">Visit our Website</a></li>
<li><a href="https://ecfwp.com/docs" rel="nofollow ugc">See Docs</a></li>
<li><a href="https://ecfwp.com/contact-us" rel="nofollow ugc">Get Support</a></li>
</ul>
  
––––––––––––––––––––––––––––––––––––––
<h3>PREMIUM</h3>
Effortless Custom Fields plugin’s premium version is also available.
<ul>
<li><a href="https://ecfwp.com/" rel="nofollow ugc">Learn more »</a></li>
<li><a href="https://ecfwp.com/pricing" rel="nofollow ugc"> Buy ECF Premium »</a></li>
</ul>
<h4>Free vs Premium</h4>
<ol>
<li>Field Grouping
<ul>
<li>Free: You can group your fields only with “headings.”</li>
<li>Premium: You can group your fields only with “tabs,” “accordions,” “field groups,” and “headings.”</li>
</ul>
</li>
<li>Repeater
<ul>
<li>Free: No repeatable fields.</li>
<li>Premium: Create unlimited repeatable fields in any possible location.</li>
</ul>
</li>
</ol>
  
––––––––––––––––––––––––––––––––––––––

Effortless Custom Fields :: ECF

World’s least confusing custom fields plugin.

XML Import vs Effortless Custom Fields :: ECF