3

You can do this a number of ways, and essentially just need an array-like structure to represent the rows. "Table": [ { "one": "Option1", "two": "Option2" }, { "one": "Option3", "two": "Option4" } ] This issue might be related to your feed however. In the dropdown, you have <altTitles> eg: - there should be a value from your ...


3

Have you set the type of data you're providing for the category field? Each element field allows you to state what attribute the data you're trying to import. Title, ID or slug, which are shown in a small dropdown field on the feed mapping page. Can you check this?


3

Do you need to close out the xml tag at the end? I've used FeedMe successfully several times. Here's a sample xml file I use: <xml> <blog> {exp:channel:entries channel="projects" limit="500"} <entry> <entry_date>{entry_date format="%F %d %Y"}</entry_date> <title>{...


3

Check out the cleanAssetUrls configuration added just for you! http://sgroup.com.au/plugins/feedme/getting-started/configuration


3

Feed Me only supports Entries at this stage. Its on the short-term roadmap in allow importing into all Elements, including Commerce Products. This cannot be achieved through hooks at the moment. Keep an eye on the plugin page. Update: FeedMe 2.0 now supports multiple entry types, including Commerce Products: http://sgroup.com.au/plugins/feedme/getting-...


3

You'll be able to get better/quicker help through the plugin page and submitting an issue - https://github.com/engram-design/FeedMe/issues. I'd be happy to help and see what might be the issue. But if you could, please follow the Support steps as outlined here - https://github.com/engram-design/FeedMe#support.


3

I'm unable to view the feed via the link you've provided - seems like it may not allow public access. In any case, see a working example below using an example public RSS feed. {% set params = { url: 'http://www.feedforall.com/sample.xml', type: 'xml', element: 'item', } %} {% set feed = craft.feedme.feed(params) %} {% for node in feed %} {{ ...


3

Just needed to save each entry and formatting corrects itself.


3

Files and assets are two different concepts. An asset represents a file already in Craft, and you'll be able to search and browse for it in the Assets section. Whereas in a number of different cases, you'll want to create (upload) an asset from a URL. If you have an existing asset in Craft already, so you don't want to upload it, then provide just the ...


3

You can create a feed-me.php file under your /config directory, then you can configure the data delimiter: <?php return [ '*' => [ 'pluginName' => 'Feed Me', 'dataDelimiter' => '-|-', ] ]; On my side, that is not working all the time (if almost never), but the doc says it should! (https://verbb.io/craft-plugins/feed-...


3

You should be able to use something similar to the following: use Craft; use verbb\feedme\FeedMe; use verbb\feedme\queue\jobs\FeedImport; $feeds = FeedMe::$plugin->feeds->getFeeds(); foreach ($feeds as $feed) { $limit = null; $offset = null; $processedElementIds = []; Craft::$app->getQueue()->delay(0)->push(new FeedImport([ ...


2

As the example actually shows, you'd reference these sort of nodes using the array notation. {{ node['dc:creator'] }}


2

It looks a bit awkward, but to append items to an array you have to use Twig's merge filter, merging the feeds_array with itself for each new item. Here's how I'd do it if you need different logic for each feed: {% set feeds_array = [] %} {% for node in craft.feedme.feed(my_rssfeed) %} {% set feeds_array = feeds_array|merge([{ title: node.title }]) %} {...


2

I'm sure I can give you a hand (Feed Me developer here) - would you be able to submit a Help request using the instructions here - https://github.com/engram-design/FeedMe#support? Happy to post back findings here. EDIT: Thanks for your patience - This was indeed a bug, which has been fixed in the latest master. Let me know if you continue to have issues!


2

Feed Me currently doesn't support this, as sometimes your data is contained in attributes, so it needs to be able to access that. Crucially, the tags are the same value, which is what trips things up. Have you looked at the Wordpress to Craft guide? https://sgroup.com.au/plugins/feedme/guides/migrating-from-wordpress


2

There's nothing through Feed Me that handles this elegantly at the moment, and you'd need to either parse your html data before or after the import. We've done this a few times on an import, where we've created a trivial PHP script which extracts images out of HTML content. Something like: $html = '<p>Some text</p><img src="http://example....


2

Sounds like your options simply need to be JSON decoded. Unfortunately, Twig doesn't ship with a json_decode filter, so you'll need a plugin – there are several that fit the bill over at StraightUpCraft. Using the JSON Decode Filter plugin, here's how your code would look: {% set options = entry.optionsAndAccessoiries|json_decode %} ...


2

For sake of completeness: the problem was that FeedMe was checking for statuscode 200 (http ok) instead of 226 that is used to determine a successful FTP transaction. This has been fixed in the latest FeedMe 2.0.0 branch that can be found on https://github.com/engram-design/FeedMe/tree/2.0.0


2

FTP should still work just fine in Feed Me 2. You can also use basic authentication by providing the username/password in the URL. ftp://username:password@website.com/public_html/feed.xml You can also use the curlOptions settings in the configuration.


2

After being in contact with the developer both issues are solved. If you have a similar issue use the latest codebase on the master branch (not the 2.0.7 as that version doesn't have the fixes yet) for the first issue (date format problem) there is an additional functionality available that allows you to predefine what the layout is of the date field you'...


2

I used FeedMe successfully and this is what I used. The images have to be already present as assets in Craft(ftp and then update asset indexes). Having the full url in the images part stumped me too. In this example I pulled the images twice because in my EE build I was using the first image of many to create a preview image and in craft I actually created a ...


2

You can’t use dot syntax because of the colon, try this instead {{ feed[0]['itunes:image']['@href'] }}


2

I believe the correct syntax you're looking for is: {{ node.logo.enclosure['@url'] }} As a handy hint, you can use the following to inspect any element parsed by Feed Me to see how you can access it. Using {{ dump(node.logo.enclosure) }} for example, you can see an array with keys and values for you to access. This is also outlined in the documentation - ...


2

I think the Json-file in it self is valid (you can always run it through a linter like JsonLint) but the problem lies with the fields. Some items (such as title) are required. I found a more accurate example in the repo of the plugin. You can find it here [ { "title": "JSON", "slug": "json", "pubDate": "Tue, 24 Feb 2015 09:00:53 +0000", "...


2

There's currently no method to parse variables into the feed itself through this, or any means. Typically, we approach this as feeds being third-party, or otherwise non-editable. How would you see utilising issueNumber to work in this scenario? You can use the concept of aliases in your URL if that helps? Lastly, you could also make use of the (...


2

Check to make sure your Primary Element field in the initial setup is the entry element and not the top level in your xml file, for example: <root> <article></article> <article></article> </root> article should be the Primary Element


2

This is fixed in 3.0.0-beta.10. Additionally, there's no longer the concept of environment variables in Craft, instead we now have aliases. So instead of using: {siteUrl}assets/data/clients.xml Use: @web/assets/data/clients.xml


2

I believe they've added the documentation you're wanting here: https://verbb.io/craft-plugins/feed-me/docs/content-mapping/field-types#assets Assets Accepts single or multiple values. You should supply the filename only, excluding the full path to the asset, but including the filename. If you're uploading remote assets, you'll need to produce fully-...


Only top voted, non community-wiki answers of a minimum length are eligible