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.

TeaCii

<p>This plugin allows you to display the value of a custom field on a page or post. Permitted values are raw text, html, javascript, javascript file url, css, css file.</p>
<p>Since version 1.1.x it also allows you to show a custom field of any page or post, provided you have the id.</p>
<p>One of the intended use of this plugin is to provide just in time code without editing the theme. Often code, especially css, gets lost with theme change. This techniques will ensure the values are loaded only on the given page and they will survive changes of themes and other plugins.</p>
<p>You can also use this to include javascript snippets or files. They will only be loaded on the given post or page. This in turn allows for loading of scripts only where needed.</p>
<p>You may use the plugin in two ways:<br />
[dcf field=”name_of_custom_field”]<br />
or optionally you can<br />
– define the type of the field value. By default the type is “raw”.<br />
– provide the id number of the page or post. By default, it would be the current page/post id.<br />
[dcf field=”name_of_custom_field” type=”value_type” id=’post_or_page_id_number’]</p>
<p>The accepted value types are:</p>
<p>“raw” – this is the default and you do not need to specify this type. It outputs the value as it is. You can use html code in the values quite safely.</p>
<p>“js” – use this to specify that the value is actually javascript. Do not wrap it with the script tag. Remember that $ is not a valid jQuery replacement in WordPress. You should use “jQuery” instead.</p>
<p>“jsf” – You may need to include a javascript file. The value of the custom field should be a fully qualified javascript file url.</p>
<p>“css” – use this to specify css code in the value of the custom field.</p>
<p>“cssf” – You may need to include a css file. The value of the custom field should be a fully qualified css file url. Here I would like to note that:<br />
– It is highly unusual to include css files in the body. However, it does work.<br />
– There may be a side effect that some elements may not show properly until the css file is completely loaded.</p>


Display Custom Fields

This plugin allows you to display the value of a custom field on a page or post. Permitted values are raw text, html, javascript, javascript file url, …

XML Import vs Display Custom Fields