Summer Round-up

We’ve had a busy “summer” this year with lots going on at Xibo HQ.

1.8 “Tempel”

Our main focus has been 1.8 series and we are pleased to report that we are close to a viable 1.8.0-alpha release. If you’ve been following the development you’ll know that 1.8 contains a rewrite to the core application which brings Xibo up to date with the latest conventions, adds a framework and includes the Twig template engine for easy theme adjustments.

We’re wrapping up initial testing before we push forward with some extra features before release. Developers and early adopters are encouraged to try the development branch on GitHub and report any issues they counter on the Community. There are instructions in the README for installation from the repository. At present it is an install only release and will not upgrade older versions, so please don’t try!


We’ve also included our new API documentation which has all been written in Swagger (you can find the swagger.json file in the repository). The API is easier to use than ever before and to prove it we’ve designed the web portal to use it too! This means the routes you call as an API developer are the same tried and tested routes we use in the web portal.

Xibo for Android

There is a new Xibo for Android update available which builds on the stability enjoyed by users of 1.7 R55. R56 adds further stability improvements as some handy features – see the announcement.

1.7 “Tuttle”

We’ve had a lot of questions about 1.7 support after 1.8 is released and we would like to put people at ease! 1.7 will receive at least 1 more bug fix release (1.7.5). This will happen after 1.8.0-alpha.


That’s all for this round-up!

1.7.2 Released

We are pleased to announce our second bug fix release for the 1.7 series of Xibo. The codename for this series is “Tuttle”.

A new CMS and Windows Player are available with this release, with just over 70 bugs resolved.

The release notes are available in the manual and the download is available on Github.

Launching the Xibo Community!

We are very pleased to announce that we are launching the new Xibo Community today. We have listened to feedback on GitHub, collected ideas and have settled on a new community discussion area right here on There are categories for general discussion, support, features and FAQ and you can log in using all of your favourite services (Facebook, Twitter, Google, GitHub, etc).

We will still be using GitHub for development, but will only be tracking verified bugs on GitHub (bugs discussed in the community).

We look forward to some great Xibo discussion!

1.7.1 Released

We are proud to announce our first bug fix release for the 1.7 series of Xibo. The codename for this series is “Tuttle”.

This release fixes some important issues with the 1.7.0 release and we recommend everyone upgrade. This is a CMS only release and the 1.7.0 windows player should be used.

The release notes are available in the manual and the download is available on Github.


1.7.0 Released

We are proud to announce our first release for the 1.7 series of Xibo. The codename for this series is “Tuttle”.

It has taken us a little over 4 months to bring you the new features in this release – the highlights are:

  • Clean, modern user interface
  • Improved translatable manual
  • Scheduling Calendar with Day, Week and Month Views
  • Simplified Player Registration and Configuration
  • Advanced Player Configuration managed from the CMS
  • Screen Shot Request from the Player
  • Media RSS support
  • Twitter support
  • Weather provided by Forecast IO
  • Effects for Text based media
  • New options for scaling web pages and embedded content
  • Many bug fixes and improvements
  • Settings for force HTTPS/STS
  • Reporting for Client up / down events.
  • Improved Sorting for all table data.
  • “Select All” functions in key places.
  • Tabs for the Settings page.
  • Options for ticker media to not strip attributes.
  • Options for ticker media to strip certain tags.
  • Better database Export (works with larger databases when Apache Sendfile mode is enabled).
  • Date formatting for Tickers.
  • General Date formatting.
  • Translated Calendar (JavaScript Translations).
  • Remove Inactive users from the permissions list.
  • Switched all HTML based media to HTML5 doctype.
  • Option to scale embedded media.
  • and much more.

The release notes are available in the manual and the download is available on Github.

We would like to take this opportunity to say a big Thank You to everyone involved in the Xibo Project Community. We couldn’t release Xibo without the help we get from people who reported bugs, submitted patches or donated money.

We have big plans for the future, so please subscribe to our RSS or follow us on Twitter or Facebook.

Moving to Github

The Xibo Project has been hosted on Launchpad since December 2008 and we appreciate the excellent platform that has been provided free of charge over that time. Bazaar is an excellent version control system and the Bug reporting on Launchpad has been perfect for our needs up until now. However, as the project has grown we have very quickly realised we need to do all we can do to encourage contribution to the platform. With only 2 main contributors to date and a handful of occasional helpers, we have struggled to push forwards with our plans, fix bugs and get new software released in a timely fashion.

Xibo is essentially a PHP/.NET/Python project and these types of developers are far more abundant on Github than they are on Launchpad – and of course many developers are now learning Git as standard, rather than Bazaar. Therefore we have taken the difficult decision to move most of the project over to Github, starting with the stable release of 1.7.0.

Details for Users

The only difference to end users will be the location to get support and report problems. The old Launchpad Answers system will be replaced by Github Issues. The Answers system in Launchpad will still be active, but only for historical viewing. It will not be monitored for new issues. FAQs and Tutorial articles will be available in the User Manual.

Details for Developers

All new development and maintenance of existing releases will be managed on Github. The following transitions will occur immediately after the release of 1.7.0.


The Source code will be transferred from Bazaar to Git and hosted on Github in a repository per component. This means there will be a repository for the CMS, one for the Windows Player, one for the Ubuntu Player, etc. There will be a central repository which glues everything together and provides an overview of the repository layout.

All active branches in Launchpad will be marked as abandoned, but where new Git repositories are created Launchpad Branches will be created to mirror “master” in those repositories.

Bugs and Features

Bugs and Features will be tracked using Github Issues. Features will be documented as a Blueprint on a Github Wiki located on the central repository. We will be porting over selected bugs and blueprints in the weeks following the migration.


Forking and submitting Pull Requests will be used as standard by the project development team and by any outside contributions.


Launchpad will contain a mirrored branch for each release and for the current development effort so that Translations can continue to occur in Launchpad.

Timing and Questions

We are planning to make the migration at the end of January 2015 to coincide with the release of our new stable 1.7.0 software . If anyone has any feedback on this migration please feel free to raise an issue on Github. It is our great hope that this move will increase the collaboration, increase exposure and ultimately result in a better product which is updated more frequently.