Release 2.7.0


#1

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
  • 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

#2

Thanks a lot for all of your work! This is a really nice release.

I assume that this final version is the same as 2.7.0.build487 ?


#3

Yes it is :slight_smile:


#4

Vielen Dank für Deine Arbeit und die der anderen Beteiligten!

Ist es normal, dass sich das Plug-in automatisch (also gänzlich ohne mein Zutun) auf diese neue Version upgedated hat?


#5

Plugins können automatisiert aktualisiert werden, das ist aber kein Entscheidung des Plugins selbst, sondern eine WordPress-Einstellung oder separate Update-Manager.


#6

Vielen Dank für den Hinweis Eric. Weisst Du zufällig wo ich die Einstellung in Wordpress finde? Ich suche seit ca. einer Stunde und finde es nicht. Update-Manager benutze ich nicht.


#7

Gute Arbeit, vielen Dank.
Ich wünsche mir den Podlove WebPlayer 4.0.7. als standalone Version in einem Wordpress-Plugin.
Wird es dieses Plugin irgendwann geben?
Momentan nutze ich noch den Podlove Webplayer 2.1 mit dem vorhandenen WP-Plugin. Der Publisher ist gut, aber ich werde ihn nicht nutzen können, daher ist der WebPlayer in der Version 4 für mich bisher leider nicht möglich.
Aber schön sieht er schon aus…


#8

Da arbeite ich gerade dran :slight_smile: https://github.com/podlove/podlove-web-player/issues/491


#9

Danke für das Shows-Feature! Beim Resonator haben wir ja kurze und lange Folgen und ich würde das dafür gerne nutzen. Ich habe die Shows angelegt und mal zwei Folgen exemplarisch zugewiesen: https://resonator-podcast.de/show/kurzfolge/feed/mp3/ und https://resonator-podcast.de/show/langfolge/feed/mp3/

Nur der Subscribe-Button mag noch nicht so recht. Auf https://resonator-podcast.de/abonnieren/ habe ich [podlove-subscribe-button show=“kurzfolge”] eingebunden, aber die Ausgabe lautet: “Du musst zuerst einen Button erstellen und seine ID angeben.”

Habt ihr das mal in einem Wordpress getestet, das neben dem Publisher zusätzlich auch den Subscribe Button als separates WP-Plugin instaliiert und in Benutzung hat? Bei uns ist das nämlich so, da ich in derselben Instanz andere Subscribe Buttons pflegen möchte, namentlich meinen handgestreichelten Kurationsfeed: https://resonator-podcast.de/wissenschaft-auf-die-ohren/

Auch im Twig-Template klappt die Einbettung über {{ podcast.subscribeButton({show: ‘langfolge’, format: ‘rectangle’, color: ‘#00477b’, style: ‘outline’, size: ‘small’}) }} z.B. auf https://resonator-podcast.de/archiv/langfolgen/ nicht so recht, da der Button hier nur den normalen Gesamt-Feed ausgibt, nicht den show-spezifischen.

Am I holding it wrong?


Announcement: WordPress Plugin
#10

Gut möglich, dass es Probleme gibt, wenn parallel der standalone PSB verwendet wird. Schaue ich mir an.


#11

Hi Eric,

nach dem Update auf die 2.7.0 habe ich ein Problem.

Laut Errorlog von nginx scheint ein Argument zu fehlen.

PHP message: PHP Warning: Missing argument 2 for podlove_maybe_override_post_titles() in /var/www/wordpress/wp-content/plugins/podlove-podcasting-plugin-for-wordpress/includes/auto_post_titles.php on line 12

Unter 2.6.4 funktioniert das ganze noch ohne Probleme.

Mit freundlichen Grüßen,

Patrick


#12

Das gleiche habe ich auch:


#13

Hmm, vielleicht ein Plugin oder Theme, das den Titel-Filter nicht ganz korrekt aufruft, den ich für die Titel-Generierung verwende. Sollte sich aber leicht beheben lassen. Danke euch für die Meldung.


#14

Gerne. Das Theme ist Twenty Sixteen.
Aber Plugins sind natürlich so einige aktiv…


#15

Wer die beliebten dreistelligen Nummern für die Episode im Template wiedergeben möchte kann folgenden Code verwenden:

{{ “%03d”|format(episode.number) }}

LG

Maddin (2D1H)


#16

Thanks a lot!

Can I somehow change the rule of the Title Migration assistant for splitting the title into mnemonics. My title format is:

<prefix><number>: <title>

The result is that Title Migration detects : <title> as the title.
15

Edit: Fount it and added (very) simple pull request: