Documentation
Site building

Notify apps of new episodes

Tell WebSub hubs and the Podcast Index right away when a feed changes.

Podcast apps check feeds on their own schedule, so a new episode can take hours to appear. The optional Podcast Publisher Notify module announces each change as it happens. It needs a Podcast Publisher release newer than 1.0.0-alpha10.

Turn on notifications

drush en podcast_publisher_notify

The module notifies two kinds of services:

  • WebSub hubs. Apps and directories subscribe to a hub and fetch the feed when the hub passes on a notification. The default hub is Google's https://pubsubhubbub.appspot.com/.
  • The Podcast Index. Apps that use its catalog learn about the update right away. No account is needed.

Configure the services

Open Configuration → Web services → Podcast feed notifications (/admin/config/services/podcast-publisher-notify):

  1. Enter one WebSub hub URL per line in WebSub hubs. Leave it empty to notify no hub.
  2. Uncheck Notify the Podcast Index to skip it.
  3. Click Save configuration.

The page needs the Administer podcast settings permission.

When notifications are sent

A notification goes out when you save a published podcast, or publish, change, unpublish, or delete a published episode. It is sent after the page has been delivered, once per podcast, however many episodes changed. Episodes released by Scheduler notify when cron publishes them.

Each feed also links to itself and to the configured hubs, as the WebSub standard requires:

<atom:link href="https://your-site.example/podcast/12/feed.xml" rel="self" type="application/rss+xml" />
<atom:link href="https://pubsubhubbub.appspot.com/" rel="hub" />

The rel="self" link is part of every feed, even without this module.

Check that it works

Notifications are logged. Open Reports → Recent log messages (/admin/reports/dblog) and filter by the type podcast_publisher_notify. A message is logged for each notification sent and each one that failed.

  • Hubs fetch the feed from its public URL. A local development site cannot be reached, so the hub ignores or rejects the notification.
  • The notification contains the absolute feed URL. Cron run by Drush needs the site's URL, for example drush --uri=https://your-site.example cron. Without it, the notification names http://default/podcast/12/feed.xml as the feed.