Tradueix al Català

Pàgines

Source text		Traduccions
#	SimplePie Show related projects	(not translated)
#	Installed Show related projects	(not translated)
#	The SimplePie library is required for Feeds SimplePie Parser. Show related projects	(not translated)
#	<br />Download the compiled, single-file version of the library from the <a href="!url">SimplePie download page</a>, place it into %folder and rename it to %file. Show related projects	(not translated)
#	Aggregates RSS/Atom/RDF feeds, imports CSV files and more. Show related projects	(not translated)
#	An example of a node importer and a user importer. Show related projects	(not translated)
#	<p> You can create as many Feeds importer configurations as you would like to. Each can have a distinct purpose like letting your users aggregate RSS feeds or importing a CSV file for content migration. Here are a couple of things that are important to understand in order to get started with Feeds: </p> <ul> <li> Every importer configuration consists of basic settings, a fetcher, a parser and a processor and their settings. </li> <li> The <strong>basic settings</strong> define the general behavior of the importer. <strong>Fetchers</strong> are responsible for loading data, <strong>parsers</strong> for organizing it and <strong>processors</strong> for "doing stuff" with it, usually storing it. </li> <li> In Basic settings, you can <strong>attach an importer configuration to a content type</strong>. This is useful when many imports of a kind should be created, for example in an RSS aggregation scenario. If you don't attach a configuration to a content type, you can use it on the !import page. </li> <li> Imports can be <strong>scheduled periodically</strong> - see the periodic import select box in the Basic settings. </li> <li> Processors can have <strong>mappings</strong> in addition to settings. Mappings allow you to define what elements of a data feed should be mapped to what content fields on a granular level. For instance, you can specify that a feed item's author should be mapped to a node's body. </li> </ul> Show related projects	(not translated)
#	<p> Define which elements of a single item of a feed (= <em>Sources</em>) map to which content pieces in Backdrop (= <em>Targets</em>). Make sure that at least one definition has a <em>Unique target</em>. A unique target means that a value for a target can only occur once. E. g. only one item with the URL <em>http://example.com/content/1</em> can exist. </p> Show related projects	(not translated)
#	A natural name for this configuration. Example: RSS Feed. You can always change this name later. Show related projects	(not translated)
#	A description of this configuration. Show related projects	(not translated)