Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Tweet Display Back is a module for Joomla! that allows users to display a user or list feed from Twitter on their site.
PHP CSS HTML
Failed to load latest commit information.
.tx Move the language files, no need for version specific folder anymore
build Sync PHPCS rules and fix errors
fields Site now supports HTTPS
language en-GB corrections
libraries Change remote service URL due to migrated platform and no redirects o…
media 2015
tmpl
.gitignore Use Joomla Coding Standards repo for PHPCS checks
.gitmodules Use Joomla Coding Standards repo for PHPCS checks
README.markdown Prepare new release
TDB.xml Wrong URL for updates
TDB_version_new Prepare new release
build.xml Version bump
helper.php Duplicate tweets with no retweet filter enabled (Fix #93)
index.html Stardized index.html
mod_tweetdisplayback.php 2015
mod_tweetdisplayback.xml Change remote service URL due to migrated platform and no redirects o…
script.php 2015

README.markdown

Tweet Display Back Analytics

Tweet Display Back is a module for Joomla! sites which allows users to display a user or list feed on their site.

Compatibility

The current release of Tweet Display Back is compatible with Joomla! 2.5.6 and newer. Older versions of the module are available for download at https://www.babdev.com/extensions/releases/tweet-display-back

Requirements

Tweet Display Back has no external requirements; everything necessary is included in the core Joomla! distribution.

Support

Installation Package

  • If you have made a checkout of the repository, you can build installation packages using Ant by running 'ant dev_head' 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.

Something went wrong with that request. Please try again.