Podlove Podcast Publisher

Açıklama

We built the Podlove Podcast Publisher because existing solutions are stuck in the past, complex and unwieldy. The Publisher helps you save time, worry less and provides a cutting edge listening experience for your audience.

Official Site: publisher.podlove.org

Video Tutorial: Getting started with Podlove Publisher

Compatible Feeds

The Publisher makes it easy to create highly expressive, efficient and super compatible podcast feeds with fine grained control over client behavior (e.g. GUID control to replace faulty episodes and for clients to reload) supporting all important meta data.

Multi-Format Publishing

The Publisher also makes multi-format publishing – embracing all modern and legacy audio and video codecs – a snap. By adopting simple file name conventions, the plugin allows the podcaster to provide individual feeds for certain use cases or audiences without adding work for the podcaster during the publishing process.

Optimized Web Player

The Publisher also comes with integrated with the Podlove Web Player plugin (which you do not need to install separately) and fully support its advanced options including multiple audio (MP4 AAC, MP3, Vorbis, Opus) and video (MP4 H.264, WebM, Theora) format support for web browsers. This Web Player is fully HTML5 compatible (but provides Flash fallback for ancient environments) and is ready for all touch based clients too.

Chapter Support

The Publisher also makes it easy to publish chapter information in the player to make access to structured episodes even easier. Full support for linking directly to any part of your podcast on the web with instant playback included.

Flexible Templates

To round it all up, a flexible template system enables you to published Podcasts in a defined fashion and change the style at any time without having to touch your individual postings later on.

And this is just the beginning. We have a rich roadmap that will bring even more interesting features: integration with helpful services, much improved timeline metadata support (show notes) and much more.

Further Reading

Development of the plugin is an open process. The current version is available on GitHub Feel free to contribute and to fix errors or send improvements via GitHub.

Requires PHP 5.4+

Ekran Görüntüleri

  • Custom episode post type separates media from your blog content.
  • Download analytics provide you with all the data you ever wanted.
  • The Publisher automatically checks the health of your media files.
  • The mighty template engine gives you full control over the episode presentation.
  • Includes the Podlove Subscribe Button, the easiest way for listeners to subscribe to your podcast.
  • Includes the Podlove Web Player. One more thing: you can manage and present all contributors easily.

Yükleme

  1. Download the Podlove Publisher Plugin to your desktop.
  2. If downloaded as a zip archive, extract the Plugin folder to your desktop.
  3. With your FTP program, upload the Plugin folder to the wp-content/plugins folder in your WordPress directory online.
  4. Go to Plugins screen and find the newly uploaded Plugin in the list.
  5. Click Activate Plugin to activate it.

SSS

Installation Instructions
  1. Download the Podlove Publisher Plugin to your desktop.
  2. If downloaded as a zip archive, extract the Plugin folder to your desktop.
  3. With your FTP program, upload the Plugin folder to the wp-content/plugins folder in your WordPress directory online.
  4. Go to Plugins screen and find the newly uploaded Plugin in the list.
  5. Click Activate Plugin to activate it.
Is Podlove Podcast Publisher free?

Yes! The core features of Podlove Podcast Publisher are and always will be free. Paid Professional Support is available but not necessary to run the plugin.

Are there Download Statistics?

Yes! Podcast Downloads can be tracked and analyzed. You can easily see how many people downloaded you podcast episodes, which clients they used, if they prefer to subscribe to the feed or listen on your website using the web player—and much more.

Are there Privacy / GDPR considerations?

Podlove Publisher is GDPR compliant and provides prewritten text snippets for your privacy page. See https://docs.podlove.org/podlove-publisher/guides/dsgvo-gdpr.html

Where can I host my podcast files?

Any storage where you have control over the file naming is compatible with Podlove Podcast Publisher. You can manage files using a simple FTP/sFTP or use services like Amazon S3.

Where can I ask questions and get support?

Free support where questions are answered by the community is available in the Podlove Community Forum. There is a German community in the Sendegate. Professional Support by the plugin developer is also available.

How can I help the project?

The continued success of Open Source project relies on the community. There are many ways you can help:

This product includes GeoLite2 data created by MaxMind, available from http://www.maxmind.com.

İncelemeler

Best Non-Commercial Podcast Plugin

This is by far the best non-commercial podcast plugin available for WordPress. It’s not always easy to use, and you have to pay close attention to what you’re doing when you’re setting the settings, but once you get it the way you want it, it runs very well.

Best podcast plugin

I host my podcast on a site with a different name, so I wanted a way to customise my podcast URL so that the feed has the podcast name in it and not just the domain name. This let me do that with no hassle, and is just a really slick podcast in general. Thanks so much!

Breaks some major details

Looks pretty cool and comes with a great mp3 player. BUT had some conflicts with Yoast SEO that kept the links from showing up with the featured image and snippet in social media. I figured out how to configure things so that they worked together and thought things were great.

THEN I noticed that the podcast feed was broken. It kept throwing the feed into a redirect loop or redirecting to the home page. This was despite disabling all other plugins and changing the theme to Twenty Seventeen. Couldn’t ever get that ironed out so I gave up on it.

UPDATE: Changing my review. I solved the YOAST SEO conflict by unchecking the Open Graphs setting in Podlove > Modules.

The feed issue was caused by server-side caching, CDN and the Let’s Encrypt SSL certificate. I disabled the certificate and that corrected the issue. (There is a setting in Podlove > Expert Settings that can help with this but I had to just disable the certificate). There are A LOT of little things that you can adjust with this plugin. That means you might need to take your time and review all of the setting carefully. Once you’ve got everything dialed in it’s great but I’m not sure why Powerpress was able to create a valid feed with my server configuration but Podlove was not.

Poorly written script; Resource hog

I just installed it and was going to go back later tomorrow to set it up and try it out. However, over the course of the day, it slurped up my entire feed and crashed my site due to excessive CPU usage. I’m not sure why since I hadn’t changed any settings yet. Totally useless and a bunch of angry subscribers.

Doesn’t work with MediaFire

I tried this as an alternative to powerpress but it doesn’t work – it cannot find the mp3 files on MediaFire and there’s no ability to give it a specific URL for an episode. Admittedly, powerpress is glitchy with MediaFire which is why I’m trying alternatives, and otherwise this seems to be a well-designed plugin, it’s just designed for FTP folders not Cloud servers.

33 incelemeyi oku

Katkıda Bulunanlar ve Geliştiriciler

“Podlove Podcast Publisher” açık kaynaklı yazılımdır. Aşağıdaki kişiler bu eklentiye katkıda bulunmuşlardır.

Katkıda bulunanlar

“Podlove Podcast Publisher” 2 dile çevrildi. Katkıda bulundukları için çevirmenlere teşekkürler.

“Podlove Podcast Publisher” eklentisini dilinize çevirin.

Geliştirmeyle ilgilenir misiniz?

Kodu görüntüle, SVN deposuna göz at veya RSS ile geliştirme günlüğüne abone ol.

Değişiklik Kaydı

2.7.10/11

  • update Analytics JS frameworks, fixing #982
  • add download location analytics chart
  • remove weekday chart
  • add option to disable average episode display

2.7.9

Too much slimming in 2.7.8. Undo.

2.7.8

  • fix release workflow
  • slim down plugin size by removing unnecessary files from release
  • update Podlove Web Player 4

2.7.7

Update 2.7.5 changed the way download tracking works to comply with GDPR. We tried the radical approach and anonymized IPs. As it turns out, this is not viable. Download numbers are skewed by this change and often much lower than they realistically should be. If you saw a drop in downloads since updating to 2.7.5 or 2.7.6, this is the reason.

The good news is that this update changes download tracking again and new download numbers should get back to normal. The bad news is that the data since the GDPR update cannot be fixed/restored because it’s missing data granularity — which was the point of the change; just not anitcipating the effect on the actual download numbers.

So what’s the new tracking approach?

Podlove Publisher now stores the request_id again just like before the update: a hash based on the actual IP address and the user agent. What’s new is that now once a day, all request_ids older than 24 hours are salted again, making it impossible to restore IPs from them. This 24 hour window is enough to determine download numbers exactly as before the GDPR update.

To be clear, IPs are never stored in plain text. But since IPs could be restored by brute force attack from the temporary unsalted request_id hashes, they have to be treated like plain IPs. The text snippet for your privacy page has been updated in the docs and you should update it on your site: https://docs.podlove.org/podlove-publisher/guides/dsgvo-gdpr.html

2.7.6

No changes.

2.7.5

Preparation for GDPR/DSGVO

If you are using Podlove Publisher Tracking/Analytics, an update to this version is highly recommended.

Tracking uses a request_id to be able to determine when two requests came from the same user and should be counted as one unique access. This request id used to be a hash of the original IP address and the user agent. This approach however is vulnerable to a brute force attack to get the IP address back from the hash. Here’s what we are doing about that:

First, we anonymize the IP before generating the hash. So instead of using 171.23.11.209, we use 171.23.11.0.

Second, you need to deal with the existing request_ids. There is a new “DSGVO” section under “Tools” with a button that will rehash all existing request_ids with a randomly generated salt. That way it will become unfeasible to determine the original IP address but your analytics will stay the same.

In case you have a lot of downloads (let’s say much more than 50.000), you may want to do this via command line because that will be much quicker than via the tools section. You need wp-cli, then simply call wp eval 'podlove_rehash_tracking_request_ids();'. On a multisite, pass the blog id as a parameter: wp eval 'podlove_rehash_tracking_request_ids(42);'.

Other

  • fix Podlove Subscribe Button language parameter
  • fix rel="self" link in show feeds
  • fix Podlove Subscribe Button not delivering show feeds
  • templates: handle episode.show access when there is no show
  • templates: allow episode filtering by show, for example: {% for episode in podcast.episodes({show: "example"}) %}

2.7.4

No changes, but the previous release is not delivered correctly by WordPress, so this is simply a re-release attempt to fix it.

2.7.3

  • fix: geo database updater
  • update Podlove Web Player 2: remove Flash Fallback
  • update Podlove Web Player 4

2.7.2

  • fix: itunes:image tag in show feeds
  • fix: “Debug Tracking” choosing wrong media files to check availability
  • enhancement: “Debug Tracking” now suggests disabling SSL-peer-verification if URL cannot be resolved and https is used
  • system report: include active plugins

2.7.1

  • fix: PHP warning when the_title filter is called with only one parameter
  • fix: handle colons in migration tool
  • fix: PWP4 warning when using shortcode
  • new service: letterboxd

2.7.0

New Module: Shows

With shows you can offer feeds to subtopics of your podcast. Here’s how it works: You create a show and define show meta, similar to a podcast: title, slug, subtitle, summary, image and language. These fields override your podcast settings. All other settings are the same as your podcast.

For each episode, you decide which show it’s in. Each show has its own set of feeds that listeners can subscribe to. The main feed remains unchanged, containing all episodes from all shows.

The Podlove Subscribe Button can be configured to subscribe to a show by referencing the show slug. Use the shortcode [podlove-subscribe-button show="show-slug"] or the template tag { podcast.subscribeButton({show: 'show-slug'}) }}.

We do not recommend using Shows and Seasons at the same time.

Updated Metadata for Podcast/Episode/Seasons according to iOS11 Specification

Apple announced an updated specification for feed elements. These changes enable the Apple Podcasts app to present podcasts in a better way. But since these feed extensions are readable by any podcast client, we expect others to take advantage of these new fields soon. Here is how we implemented the specification:

  • The podcast has a new “type” field where you can select between “episodic” and “serial”, which may affect the order of episodes. The field <itunes:type>episodic</itunes:type> appears in the feed.
  • Episodes have a new “title” field. It defaults to the episode post title but can be set separately now, allowing you to define different titles for the website and podcast clients. The field <itunes:title>Interview with Somebody Infamous</itunes:title> will appear in the feed.
  • Episodes have a new “type” field where you can select between “full” (default), “trailer” and “bonus”. This won’t have any effect in the Publisher but may be used by podcast clients. The field <itunes:episodeType>full</itunes:episodeType> appears in the feed.
  • Episodes have a new “number” field. If used, <itunes:episode>42</itunes:episode> will appear in the feed.
  • Episodes in seasons will have an <itunes:season>2</itunes:season> field in the feed automatically.

We decided to complement these changes by introducing a podcast mnemonic/abbreviation field. Now we can autogenerate blog episode titles, based on the episode number and title, if you like. The mnemonic can be set in podcast settings. The setting to autogenerate blog episode titles is an expert setting in the “Website” section.

To help existing podcasts to conform to these new fields we made a “Title Migration” module which will greet you with a notice once you update the Publisher. It will try to extract episode numbers and titles from your existing titles, saving you time and effort updating each episode one by one.

Template API Changes

  • episode.title now returns the new episode title field, if it is set, but has a fallback to the post title. If you want a specific version, use episode.title.clean or episode.title.blog.
  • the post title of an episode can still be accessed via episode.post.post_title
  • new accessor: episode.number
  • new accessor: episode.type
  • new accessor: podcast.mnemonic
  • new accessor: podcast.type
  • new accessor: season.mnemonic

Podlove Web Player 4

The Shortcode [podlove-web-player] accepts several parameters, increasing its versatility.

With post_id you can embed episodes on any page, for example [podlove-web-player post_id="1234"].

Every config parameter available can be overridden using shortcode attributes. The only difference from the linked documentation page is the notation. For nested configs like show.title use underscores (_) instead. For example, display a green player with custom title like this: [podlove-web-player show_title="Special Title" theme_main="#00ff00"]

You can now also display a player with live content like this: [podlove-web-player mode="live" audio_0_url="http://mp3.theradio.cc/" audio_0_mimeType="audio/mp3" title="Livestream" link="https://theradio.cc"]

You can choose to deliver Podlove Player via Podlove CDN (Content Delivery Network) or via your WordPress server. CDN is the default for new setups but if you are already using Podlove Publisher we continue delivering Podlove Player via your WordPress server unless you explicitly change it.

Podlove Web Player 4 is the new default player.

Other

  • analytics: show download totals for last 24 hours and last 7 days in overview
  • Podigee Player: add support for transcripts
    • create a Podigee Transcript asset
    • set this asset in Expert Settings > Web Player
    • See https://cdn.podigee.com/ppp/samples/transcript.txt for an example transcript
  • Podlove Web Player 4: support contributors
  • player settings: when no episode or files are available, use a “Podlove” demo sound
  • reduce Podlove Template Cache duration from 1 day to 1 hour for the following change:
  • new template accessor: {{ episode.total_downloads }}
  • New in “Global Feed Settings”: An option for how the episode title should be displayed. It defaults to “Blog Post Title”, so that after the iOS 11 title migration, the output does not actually change — following the principle of least surprise. However, the setting can be changed to “Episode Title”, which is the new clean title, or “Custom Template”, which is a title template with the same capabilities as the blog post title template.
  • when using the Podlove Subscribe Button CDN and the CDN is not reachable, fall back to the locally hosted script
  • fix Geo DB Updater: use our own Podlove CDN as download source
  • fix quotes in contributor fields
  • fix WordPress conditionals in episode archives
  • fix deleting related episodes (#907)
  • fix network admin bar now does not include broken links if Publisher is not activated network-wide (#933)
  • fix import getting stuck issue (#910)
  • Bitlove module: remove all frontend functionality because it has been dysfunctional for a long time
  • fix Auphonic module showing wrong status message after file upload
  • fix Audacity chapter import when times contain commas
  • fix email notification issue where not emails were sent (#938)
  • fix feed redirect issue for HTTP/1.0 clients
  • fix network module: only activate when the plugin is activated network-wide, not when the plugin in active within a multisite
  • fix calculation of contribution counts
  • Fix various issues in the download table display. Until now, new downloads were calculated hourly, which provides a good estimate but often not exact numbers. The calculation could also get stuck, leading to missing data display. From now on, the estimates are still calculated hourly but additionally a full, precise aggregation is done once a day, which should lead to more consistent numbers overall.
  • enhance email error reporting
  • enhance open graph module: detects WP SEO plugin and does not output any tags to avoid conflicts
  • social services: add SlideShare
  • show warning if upload directory is not fully qualified
  • remove download section from default template (because it is included in PWP4)
  • image cache: instead of returning invalid URLs with 0 width and 0 height when something goes wrong, return the source URL instead
  • episode list: add display option to display episode number as a column
    add Liberapay as donation service
  • display current season in episode form

Changes for previous versions can be found in the changelog.txt.