The popular blogging platform WordPress has proven to be also rather popular with podcasters. However, the system itself is not particularly made for podcasting and while some things are easy, other things are rather complicated and error-prone.
Therefore a variety of plugins want to improve on this and want to make life easier for podcasters. But all of them are tying too much into the conventions and workflows of WordPress that are not always doing what a podcaster needs.
The Podlove Podcast Publisher tries to solve the problem from the podcasters’ perspective and implements a variety of features and workflows that have been rather difficult to achieve with WordPress until now. The plugin makes the process easier by settling on a few common conventions to make publishing and maintaining podcast feeds a snap and highly reliable.
The plugin is currently in Beta and still under heavy development.
In its current beta form, the plugin provides:
- Strong separation of blog and podcast content (using a custom post type)
- Simple dashboard to provide an overview of the podcast status
- Automatic asset validation in the background to ensure the integrity of your podcast media files
- Flexible template system to create unified blog posts for episodes
- Chapter mark support (including Podlove Simple Chapters)
- Integration of the Podlove Web Player (with chapter support)
- Support for multiple media files per episode to support more platforms, adapt to listener bandwidth requirements or support different viewing resolutions.
- The concept of episode assets ensures podcast integrity, allows for easy publishing and reduces overall complexity when posting
- Complete control over content of podcast feeds.
- Descriptions in feeds based on title/subtitle/summary info cascade to allow for smaller and more precise feeds
- Strong compatibility with feed and podcast directory standards
- Builtin modules and support for separate plugins to extend functionality
- Support for most iTunes podcast extensions
- Support for feed proxies with temporary or permanent redirection
- Integrated Migration Assistant to move on from PodPress or PowerPress
- Integration with the audio post-production service Auphonic to easily import asset and metadata information with a single click
- Integration with Podcast-to-BitTorrent service Bitlove to automatically offer BitTorrent downloads for all of your files
- Automatic posting of new episodes to App.net
- Support for Paged Feeds based on RFC5005
- OpenGraph and Twitter Card support for better social media integration
- Pubsubhubbub support superfast feed updates
In the future, the plugin will provide for
- Timeline-oriented show notes for links, images, chapters, annotations, transcripts and more
- Extensive download statistics
- Extended metadata support for listing participants and other contributors
- Extended dashboard to provide even more overview
- Automatic archive, contributor overview pages
- Automatic listing of the podcast feeds
- Support of multiple episode types (shows)
- Complete control over the length of podcast feeds
- Complete support for iTunes podcast extensions
- Live show support (Announcements and streaming web client)
Open Development and Requirements
Podlove publisher an open collaborative effort and you find the current development on github:
The plugin currently requires PHP 5.3 and WordPress 3.x. We might raise this limits as things progress to be able to embrace upcoming features of PHP and/or WordPress and to cut off outdated technology that keeps things from improving and is usually prone to additional security risks.
We provide updates through the WordPress plugin directory so you can keep your installation up-to-date easily.
Feel free to contribute and to fix errors or send improvements via github.
The plugin is in beta now and mostly considered stable. We will add more features in the future but we think we have settled on the basic structure for now.
You can find the plugin here:
If you encounter a specific problem using the Podlove Podcast Publisher that you think is a bug, please consider submitting the problem here:
You can also contact us on Twitter for general questions: