relisiuol

<p>Content Aggregator helps WordPress sites import external content as posts. It is built for sites that need to pull from feeds or remote endpoints on a schedule, while still controlling how imported posts are titled, dated, categorized, and published.</p>
<p>Out of the box, Content Aggregator includes parser definitions for RSS feeds, Atom feeds, and WordPress REST API post endpoints. Its parser registry uses JSON and XML mappings, so additional source formats can be supported without changing the import workflow.</p>
<h3>Key features</h3>
<ul>
<li>Manage import sources from the WordPress admin.</li>
<li>Detect the source type automatically from a source URL.</li>
<li>Import new items through WP-Cron on a configurable schedule.</li>
<li>Limit how many sources are checked during each scheduled run.</li>
<li>Configure post title, date, and content templates with placeholders.</li>
<li>Assign categories and choose the post status for imported content.</li>
<li>Set a default featured image when the remote item has no usable image.</li>
<li>Avoid duplicate imports using the original item URL.</li>
<li>Optionally enforce unique post titles.</li>
<li>Optionally redirect imported posts to the original source URL.</li>
<li>Configure the request User-Agent and SSL certificate path for remote fetches.</li>
<li>Automatically disable sources that stay offline beyond the configured expiration delay.</li>
</ul>
<h3>Supported sources</h3>
<p>Content Aggregator ships with support for common feed and WordPress content sources:</p>
<ul>
<li>RSS feeds.</li>
<li>Atom feeds.</li>
<li>WordPress REST API post endpoints.</li>
<li>JSON and XML sources when a matching parser definition is available.</li>
</ul>
<h3>Imported post templates</h3>
<p>Each source can define templates for the imported post title, publication date, and content. Templates can use placeholders for the original title, source name, current import date, original publication date, original content, and original URL.</p>


Content Aggregator

Create WordPress posts from RSS, Atom, WordPress REST API, JSON, and XML sources.

BjornW

<blockquote>
<p>THIS PLUGIN IS NOT MAINTAINED ANYMORE!<br />
  For historical purposes this plugin is still online. The general concept could still be useful,<br />
  the code is probably not working and horrible outdated.</p>
</blockquote>
<p>Create streams of sitewide aggregated content from your multisite WordPress installation with bbAggregate.</p>
<p>A stream contains posts from those blogs allowed to participate in the stream. Anyone writing posts can add his/her post to one or more streams.<br />
The streams are shown by using a specific page template. (see also the examples directory). It offers functionality similar<br />
to the sitewide categories / global terms, but with more control and (hopefully) less buggy behaviour.</p>
<p>This plugin adds two database tables to your installation:</p>
<ul>
<li>$prefix_bbAggregate_item (links an item to a stream)</li>
<li>$prefix_bbAggregate_stream (contains the stream info)   </li>
</ul>
<p>NB: This plugin is only useful for a WordPress Multisite installation in which multiple<br />
blogs are being used.</p>
<h4>How does it work?</h4>
<p>First, you create a stream (neccessary user capabillity: ‘manage_options’,admin role works perfectly). (See screenshot-4.png)<br />
It is recommended to only use letters, numbers and underscores or dashes in the stream name. Spaces in the name may cause problems at the moment.</p>
<p>Streams are defined by a name, a description (which is saved but not yet accessible for public use) and some options (see screenshot-5.png) such as:</p>
<ul>
<li>maximum number of posts (limits the total amount of posts in a stream)</li>
<li>maximum number of posts per blog (limits the amount of posts per blog in a stream)</li>
<li>number of posts per page (limits the amount of posts per page. Pagination is included)</li>
<li>excluded blogs (blogs which have been explicitly excluded from using this stream. Posts from these blogs will not be shown in this stream) </li>
</ul>
<p>After creating a stream (See screenshot-6.png and screenshot-7.png), create a post in a blog which is not excluded from this stream. Below the Post Editing Area you will see a new metabox called<br />
Streams (see screenshot-8.png) with a list of available streams (streams which have excluded this blog are not shown). By ticking the checkbox in front of the stream name<br />
you’ve added your post to this stream. Every user able to add a post may add his/her posts to the streams shown.</p>
<p>To show a stream of content you (or the theme designer of the theme you use) need to prepare the theme for showing the items. You need a page template<br />
for this. An example of this can be found in bbAggregate/examples and the template is called: bbAggregate-template-aggregated-posts. For now you can copy<br />
it into the directory of your active theme so you can test bbAggregated. Keep in mind though that it will not use your theme’s style!<br />
Create a page in the blog where you also have copied the page template and select the Aggregated Posts template<br />
as the page’s template. Add the customfield with the name ‘bbagg_stream’ (without quotes) and customfield value the exact(!) stream name of the stream you want to show (see screenshot-11.png).<br />
By the way, the example page template the custom field name is hardcoded, but you can change it in the template as long as you also use the new name<br />
for your customfield. After adding the customfield name and value and publishing the page you can view the page and you should now see your post part<br />
of the stream’s aggregated content (see screenshot-12.png).</p>
<p><em>Note</em>: The stream default options can be changed sitewide by visiting the Super Admin->Options (See screenshot-9.png). Look for ‘bbAggregate sitewide defaults’ (see screenshot-10.png). After changing<br />
the options’ values and saving the changes new streams will use your new defaults. This can only be done by users with super admin rights. Keep in mind that streams are sitewide. Thus streams created in blog 1<br />
are also visible in the bbAggregate settings of blog 2.</p>
<h3>TODO</h3>
<p>Feel free to send patches 😉</p>
<ul>
<li>Remove database tables upon delete of plugin </li>
<li>Add .po and .mo files for translations</li>
<li>Create php doc files</li>
</ul>


bbAggregate

Create streams of sitewide aggregated content from your multisite WordPress installation with bbAggregate

Content Aggregator vs bbAggregate