Podcast Manager is a suite of extensions allowing users to host and manage a podcast feed from their Joomla! site.
PHP JavaScript CSS HTML
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.tx
build
com_podcastmanager Transifex pull Jun 22, 2015
com_podcastmedia
files_podcastmanager_hathor
files_podcastmanager_strapped
language
lib_getid3
mod_podcastmanager
mod_podcastmanagerfeed
plg_content_podcastmanager
plg_editors-xtd_podcastmanager
plg_finder_podcastmanager_feeds
plg_finder_podcastmanager_podcasts
plg_podcastmedia_user
.gitignore
.gitmodules
README.markdown
build.xml
pkg_podcastmanager.xml
script.php

README.markdown

Podcast Manager

Podcast Manager is a suite of extensions for a Joomla! powered website which allows users to create, manage, and host a podcast feed directly from their website.

Compatibility

Podcast Manager is currently compatible with Joomla! 2.5.6 or newer and requires PHP 5.3 or later.

Joomla! 2.5.6 is the minimum supported version of the 2.5 series due to supporting both Joomla! 2.5 and 3.x with a single package and the necessary support code not being present in earlier versions of 2.5. Also, high level security issues exist in older versions of 2.5, and as such, they will NOT be supported. Older versions of Podcast Manager compatible with older versions of Joomla! (the first supported version was Joomla! 1.6) are available from the downloads section of this repository.

Requirements

Podcast Manager has no external requirements to operate; all necessary code is installed with the package.

Support

Installation Package

  • Installation packages for Podcast Manager are available from the downloads section of this repository.
  • If you have made a checkout of the repository, you can build installation packages using Ant by running 'ant' from your interface.

Stable Master Policy

The master branch will at all times remain stable. Development for new features will occur in branches and when ready, will be pulled into the master branch.

In the event features have already been merged for the next release series and an issue arises that warrants a fix on the current release series, the developer will create a branch based off the tag created from the previous release, make the necessary changes, package a new release, and tag the new release. If necessary, the commits made in the temporary branch will be merged into master.