- Rewrote the headline module from scratch. Note that the old
headline code is still in place 'till the new code has proven
to be stable. See "syndication.module" for the new code.
Changes:
+ Improved the parser and tested it against RSS 0.9, RSS 0.91,
RSS 0.92, RSS 1.0, RDF and XML feeds.
+ Improved the administration interface. It might be a bit fuzzy
at first. Maybe some native English like Julian, Michael (or any
one else with knowledge in the field) can help out by suggesting
better naming, terminology or descriptions - as well as by
writing the help section for this module? I'd have no idea how
much this would be appreciated.
+ We can *easily* recognize new tags or extensions: we parse out
"link", "title", "description" and "author" right now, but we
will have to revise which tags to support and which not. New
tags can be added in less than 10 minutes (if you are familiar
with the code). Read: we have something we can build on.
+ Within each item, tags can now appear is random order which is
or was not the case with the old headline code where we expect
<link>s prior to <description>s for example.
+ Feed updates only (ie. always) happen through cron. Neither do
we use one global cron for updating all feeds; instead, every
feed can specify his own update-interval.
+ Newly fetched headlines are "appended" to the pool of existing
headlines (read: we don't replace the whole feed), and headlines
automatically "expire" after x days or hours. (Every headline
has a timestamp.)
+ Got rid of backend.class; it is integrated in the module.
+ Switched to more generic names: "headline" became "item" and
"backend" became "feed". This should ease future non-headline
oriented syndication.
+ You can associate attributes or keyword lists with every feed.
At the moment new items will automatically inherit their feeds
attributes but in future we can use heuristics to make these
attributes "mutate" when and where we see fit. The attributes
can be maintained by hand as well.
+ We don't export any blocks yet; we will soon do as soon this
new code has been tested for a bit more. We will only export
bundles though so if you want to export by feed/source, you
will have to make a source-specific bundle.
- Polished a bit on a few other modules: nothing major.
2001-05-26 18:26:56 +00:00
<?php
2003-08-20 21:00:31 +00:00
2004-08-21 06:42:38 +00:00
/**
* @file
2006-04-13 08:52:42 +00:00
* Used to aggregate syndicated content (RSS, RDF, and Atom).
2004-08-21 06:42:38 +00:00
*/
2019-04-16 05:38:27 +00:00
use Drupal\Core\Url;
2014-05-20 09:29:40 +00:00
use Drupal\aggregator\Entity\Feed;
2014-06-30 03:33:08 +00:00
use Drupal\Core\Routing\RouteMatchInterface;
2012-07-15 02:05:46 +00:00
2004-05-11 20:10:14 +00:00
/**
2009-12-04 16:49:48 +00:00
* Implements hook_help().
2004-05-11 20:10:14 +00:00
*/
2014-06-30 03:33:08 +00:00
function aggregator_help($route_name, RouteMatchInterface $route_match) {
2014-05-07 02:04:53 +00:00
switch ($route_name) {
case 'help.page.aggregator':
2014-09-26 12:28:23 +00:00
$path_validator = \Drupal::pathValidator();
2009-11-24 05:23:54 +00:00
$output = '';
$output .= '<h3>' . t('About') . '</h3>';
2017-03-04 01:20:24 +00:00
$output .= '<p>' . t('The Aggregator module is an on-site syndicator and news reader that gathers and displays fresh content from RSS-, RDF-, and Atom-based feeds made available across the web. Thousands of sites (particularly news sites and blogs) publish their latest headlines in feeds, using a number of standardized XML-based formats. For more information, see the <a href=":aggregator-module">online documentation for the Aggregator module</a>.', [':aggregator-module' => 'https://www.drupal.org/documentation/modules/aggregator']) . '</p>';
2009-11-24 05:23:54 +00:00
$output .= '<h3>' . t('Uses') . '</h3>';
$output .= '<dl>';
2014-09-30 06:50:14 +00:00
// Check if the aggregator sources View is enabled.
2014-09-26 12:28:23 +00:00
if ($url = $path_validator->getUrlIfValid('aggregator/sources')) {
$output .= '<dt>' . t('Viewing feeds') . '</dt>';
2019-04-16 05:38:27 +00:00
$output .= '<dd>' . t('Users view feed content in the <a href=":aggregator">main aggregator display</a>, or by <a href=":aggregator-sources">their source</a> (usually via an RSS feed reader). The most recent content in a feed can be displayed as a block through the <a href=":admin-block">Blocks administration page</a>.', [':aggregator' => Url::fromRoute('aggregator.page_last')->toString(), ':aggregator-sources' => $url->toString(), ':admin-block' => (\Drupal::moduleHandler()->moduleExists('block')) ? Url::fromRoute('block.admin_display')->toString() : '#']) . '</dd>';
2014-09-26 12:28:23 +00:00
}
2009-11-24 05:23:54 +00:00
$output .= '<dt>' . t('Adding, editing, and deleting feeds') . '</dt>';
2019-04-16 05:38:27 +00:00
$output .= '<dd>' . t('Administrators can add, edit, and delete feeds, and choose how often to check each feed for newly updated items on the <a href=":feededit">Aggregator administration page</a>.', [':feededit' => Url::fromRoute('aggregator.admin_overview')->toString()]) . '</dd>';
2015-09-08 10:24:01 +00:00
$output .= '<dt>' . t('Configuring the display of feed items') . '</dt>';
2019-04-16 05:38:27 +00:00
$output .= '<dd>' . t('Administrators can choose how many items are displayed in the listing pages, which HTML tags are allowed in the content of feed items, and whether they should be trimmed to a maximum number of characters on the <a href=":settings">Aggregator settings page</a>.', [':settings' => Url::fromRoute('aggregator.admin_settings')->toString()]) . '</dd>';
2015-09-08 10:24:01 +00:00
$output .= '<dt>' . t('Discarding old feed items') . '</dt>';
2019-04-16 05:38:27 +00:00
$output .= '<dd>' . t('Administrators can choose whether to discard feed items that are older than a specified period of time on the <a href=":settings">Aggregator settings page</a>. This requires a correctly configured cron maintenance task (see below).', [':settings' => Url::fromRoute('aggregator.admin_settings')->toString()]) . '<dd>';
2015-09-08 10:24:01 +00:00
2014-01-25 23:46:15 +00:00
$output .= '<dt>' . t('<abbr title="Outline Processor Markup Language">OPML</abbr> integration') . '</dt>';
2014-09-30 06:50:14 +00:00
// Check if the aggregator opml View is enabled.
2014-09-26 12:28:23 +00:00
if ($url = $path_validator->getUrlIfValid('aggregator/opml')) {
2019-04-16 05:38:27 +00:00
$output .= '<dd>' . t('A <a href=":aggregator-opml">machine-readable OPML file</a> of all feeds is available. OPML is an XML-based file format used to share outline-structured information such as a list of RSS feeds. Feeds can also be <a href=":import-opml">imported via an OPML file</a>.', [':aggregator-opml' => $url->toString(), ':import-opml' => Url::fromRoute('aggregator.opml_add')->toString()]) . '</dd>';
2014-09-26 12:28:23 +00:00
}
2009-11-24 05:23:54 +00:00
$output .= '<dt>' . t('Configuring cron') . '</dt>';
2019-04-16 05:38:27 +00:00
$output .= '<dd>' . t('A working <a href=":cron">cron maintenance task</a> is required to update feeds automatically.', [':cron' => Url::fromRoute('system.cron_settings')->toString()]) . '</dd>';
2009-11-24 05:23:54 +00:00
$output .= '</dl>';
2005-11-01 10:17:34 +00:00
return $output;
2014-05-07 02:04:53 +00:00
case 'aggregator.admin_overview':
2014-01-25 23:46:15 +00:00
// Don't use placeholders for possibility to change URLs for translators.
2014-10-08 15:21:44 +00:00
$output = '<p>' . t('Many sites publish their headlines and posts in feeds, using a number of standardized XML-based formats. The aggregator supports <a href="http://en.wikipedia.org/wiki/Rss">RSS</a>, <a href="http://en.wikipedia.org/wiki/Resource_Description_Framework">RDF</a>, and <a href="http://en.wikipedia.org/wiki/Atom_%28standard%29">Atom</a>.') . '</p>';
2019-04-16 05:38:27 +00:00
$output .= '<p>' . t('Current feeds are listed below, and <a href=":addfeed">new feeds may be added</a>. For each feed, the <em>latest items</em> block may be enabled at the <a href=":block">blocks administration page</a>.', [':addfeed' => Url::fromRoute('aggregator.feed_add')->toString(), ':block' => (\Drupal::moduleHandler()->moduleExists('block')) ? Url::fromRoute('block.admin_display')->toString() : '#']) . '</p>';
2007-12-04 16:34:27 +00:00
return $output;
2014-05-07 02:04:53 +00:00
case 'aggregator.feed_add':
2008-04-14 17:48:46 +00:00
return '<p>' . t('Add a feed in RSS, RDF or Atom format. A feed may only have one entry.') . '</p>';
2014-05-07 02:04:53 +00:00
case 'aggregator.opml_add':
Issue #1209674 by yoroy, kid_icarus, franz, pasive, barnettech, disasm, wesleydv, ericmulder1980, Sutharsan, apratt, theMusician, batigolix, vegantriathlete, amitgoyal, AndyThornton: Fix up UI text in Aggregator module
2014-06-20 21:23:11 +00:00
return '<p>' . t('<abbr title="Outline Processor Markup Language">OPML</abbr> is an XML format for exchanging feeds between aggregators. A single OPML document may contain many feeds. Aggregator uses this file to import all feeds at once. Upload a file from your computer or enter a URL where the OPML file can be downloaded.') . '</p>';
2003-08-20 21:00:31 +00:00
}
- Rewrote the headline module from scratch. Note that the old
headline code is still in place 'till the new code has proven
to be stable. See "syndication.module" for the new code.
Changes:
+ Improved the parser and tested it against RSS 0.9, RSS 0.91,
RSS 0.92, RSS 1.0, RDF and XML feeds.
+ Improved the administration interface. It might be a bit fuzzy
at first. Maybe some native English like Julian, Michael (or any
one else with knowledge in the field) can help out by suggesting
better naming, terminology or descriptions - as well as by
writing the help section for this module? I'd have no idea how
much this would be appreciated.
+ We can *easily* recognize new tags or extensions: we parse out
"link", "title", "description" and "author" right now, but we
will have to revise which tags to support and which not. New
tags can be added in less than 10 minutes (if you are familiar
with the code). Read: we have something we can build on.
+ Within each item, tags can now appear is random order which is
or was not the case with the old headline code where we expect
<link>s prior to <description>s for example.
+ Feed updates only (ie. always) happen through cron. Neither do
we use one global cron for updating all feeds; instead, every
feed can specify his own update-interval.
+ Newly fetched headlines are "appended" to the pool of existing
headlines (read: we don't replace the whole feed), and headlines
automatically "expire" after x days or hours. (Every headline
has a timestamp.)
+ Got rid of backend.class; it is integrated in the module.
+ Switched to more generic names: "headline" became "item" and
"backend" became "feed". This should ease future non-headline
oriented syndication.
+ You can associate attributes or keyword lists with every feed.
At the moment new items will automatically inherit their feeds
attributes but in future we can use heuristics to make these
attributes "mutate" when and where we see fit. The attributes
can be maintained by hand as well.
+ We don't export any blocks yet; we will soon do as soon this
new code has been tested for a bit more. We will only export
bundles though so if you want to export by feed/source, you
will have to make a source-specific bundle.
- Polished a bit on a few other modules: nothing major.
2001-05-26 18:26:56 +00:00
}
2007-04-06 13:27:23 +00:00
/**
2009-12-04 16:49:48 +00:00
* Implements hook_theme().
2007-04-06 13:27:23 +00:00
*/
function aggregator_theme() {
2017-03-04 01:20:24 +00:00
return [
'aggregator_feed' => [
2014-09-22 11:36:15 +00:00
'render element' => 'elements',
2014-02-13 10:17:50 +00:00
'file' => 'aggregator.theme.inc',
2017-03-04 01:20:24 +00:00
],
'aggregator_item' => [
2014-09-22 11:36:15 +00:00
'render element' => 'elements',
2014-02-13 10:17:50 +00:00
'file' => 'aggregator.theme.inc',
2017-03-04 01:20:24 +00:00
],
];
2014-09-22 11:36:15 +00:00
}
/**
* Implements hook_entity_extra_field_info().
2019-11-05 10:25:27 +00:00
*
* By default this function creates pseudo-fields that mask the description and
* image base fields. These pseudo-fields are omitted if:
* - a module makes the field's display configurable via the field UI by means
* of BaseFieldDefinition::setDisplayConfigurable()
* - AND the additional entity type property
* 'enable_base_field_custom_preprocess_skipping' has been set using
* hook_entity_type_build().
2014-09-22 11:36:15 +00:00
*/
function aggregator_entity_extra_field_info() {
2017-03-04 01:20:24 +00:00
$extra = [];
2019-11-05 10:25:27 +00:00
$entity_type_manager = \Drupal::entityTypeManager();
$entity_field_manager = \Drupal::service('entity_field.manager');
2014-09-22 11:36:15 +00:00
2017-03-04 01:20:24 +00:00
$extra['aggregator_feed']['aggregator_feed'] = [
'display' => [
'items' => [
2014-09-22 11:36:15 +00:00
'label' => t('Items'),
'description' => t('Items associated with this feed'),
'weight' => 0,
2017-03-04 01:20:24 +00:00
],
'more_link' => [
2014-09-22 11:36:15 +00:00
'label' => t('More link'),
'description' => t('A more link to the feed detail page'),
'weight' => 5,
2017-03-04 01:20:24 +00:00
],
'feed_icon' => [
2014-09-22 11:36:15 +00:00
'label' => t('Feed icon'),
2016-02-29 03:27:06 +00:00
'description' => t('An icon that links to the feed URL'),
2014-09-22 11:36:15 +00:00
'weight' => 6,
2017-03-04 01:20:24 +00:00
],
],
];
2014-09-22 11:36:15 +00:00
2019-11-05 10:25:27 +00:00
// Create Feed image and description pseudo-fields. Skip this if the field
// display is configurable and skipping has been enabled.
// @todo https://www.drupal.org/project/drupal/issues/3015623
// Eventually delete this code and matching lines in FeedViewBuilder. Using
// field formatters is more flexible and consistent.
$skip_custom_preprocessing = $entity_type_manager->getDefinition('aggregator_feed')->get('enable_base_field_custom_preprocess_skipping');
$base_field_definitions = $entity_field_manager->getBaseFieldDefinitions('aggregator_feed');
if (!$skip_custom_preprocessing || !$base_field_definitions['image']->isDisplayConfigurable('view')) {
$extra['aggregator_feed']['aggregator_feed']['display']['image'] = [
'label' => t('Image'),
'description' => t('The feed image'),
'weight' => 2,
];
}
if (!$skip_custom_preprocessing || !$base_field_definitions['description']->isDisplayConfigurable('view')) {
$extra['aggregator_feed']['aggregator_feed']['display']['description'] = [
'label' => t('Description'),
'description' => t('The description of this feed'),
'weight' => 3,
];
}
// Create Item description pseudo-field. Skip this if the field display is
// configurable and skipping has been enabled.
// @todo https://www.drupal.org/project/drupal/issues/3015623
// Eventually delete this code and matching lines in ItemViewBuilder. Using
// field formatters is more flexible and consistent.
$skip_custom_preprocessing = $entity_type_manager->getDefinition('aggregator_item')->get('enable_base_field_custom_preprocess_skipping');
$base_field_definitions = $entity_field_manager->getBaseFieldDefinitions('aggregator_item');
if (!$skip_custom_preprocessing || !$base_field_definitions['description']->isDisplayConfigurable('view')) {
$extra['aggregator_item']['aggregator_item']['display']['description'] = [
'label' => t('Description'),
'description' => t('The description of this feed item'),
'weight' => 2,
];
}
2014-09-22 11:36:15 +00:00
return $extra;
2007-04-07 07:38:36 +00:00
}
2007-04-06 13:27:23 +00:00
2004-05-11 20:10:14 +00:00
/**
2009-12-04 16:49:48 +00:00
* Implements hook_cron().
2004-05-11 20:10:14 +00:00
*
2009-09-25 15:20:12 +00:00
* Queues news feeds for updates once their refresh interval has elapsed.
2004-05-11 20:10:14 +00:00
*/
2004-04-27 20:10:09 +00:00
function aggregator_cron() {
2013-09-16 03:58:06 +00:00
$queue = \Drupal::queue('aggregator_feeds');
2014-03-27 06:49:51 +00:00
2019-05-24 06:44:36 +00:00
$ids = \Drupal::entityTypeManager()->getStorage('aggregator_feed')->getFeedIdsToRefresh();
2014-05-20 09:29:40 +00:00
foreach (Feed::loadMultiple($ids) as $feed) {
2010-02-26 00:11:58 +00:00
if ($queue->createItem($feed)) {
// Add timestamp to avoid queueing item more than once.
2014-01-24 07:45:57 +00:00
$feed->setQueuedTime(REQUEST_TIME);
2013-03-31 04:08:45 +00:00
$feed->save();
2010-02-26 00:11:58 +00:00
}
2001-07-09 18:13:53 +00:00
}
2010-02-26 00:11:58 +00:00
2014-03-24 10:06:27 +00:00
// Delete queued timestamp after 6 hours assuming the update has failed.
2014-05-20 09:29:40 +00:00
$ids = \Drupal::entityQuery('aggregator_feed')
2010-02-26 00:11:58 +00:00
->condition('queued', REQUEST_TIME - (3600 * 6), '<')
->execute();
2014-03-27 06:49:51 +00:00
2014-05-20 09:29:40 +00:00
if ($ids) {
$feeds = Feed::loadMultiple($ids);
2014-03-27 06:49:51 +00:00
foreach ($feeds as $feed) {
$feed->setQueuedTime(0);
$feed->save();
}
}
2001-07-09 18:13:53 +00:00
}
2006-02-22 10:13:42 +00:00
/**
2015-08-19 10:29:44 +00:00
* Gets the list of allowed tags.
2007-12-16 21:01:45 +00:00
*
2015-08-19 10:29:44 +00:00
* @return array
* The list of allowed tags.
2011-11-10 03:02:40 +00:00
*
2015-08-19 10:29:44 +00:00
* @internal
2006-02-22 10:13:42 +00:00
*/
2015-08-19 10:29:44 +00:00
function _aggregator_allowed_tags() {
return preg_split('/\s+|<|>/', \Drupal::config('aggregator.settings')->get('items.allowed_html'), -1, PREG_SPLIT_NO_EMPTY);
2006-02-22 10:13:42 +00:00
}
2006-03-08 09:52:13 +00:00
2012-01-10 03:22:24 +00:00
/**
2013-10-03 20:55:34 +00:00
* Implements hook_preprocess_HOOK() for block templates.
2012-01-10 03:22:24 +00:00
*/
function aggregator_preprocess_block(&$variables) {
2014-04-01 21:14:13 +00:00
if ($variables['configuration']['provider'] == 'aggregator') {
2012-08-03 15:31:18 +00:00
$variables['attributes']['role'] = 'complementary';
2012-01-10 03:22:24 +00:00
}
}