We are excited to share with you a new feature we've been working on for 1.8.10 that should greatly improve the reliability of images in Media RSS and Twitter, and improve the consistency of data in all other modules.

What are we solving?

Xibo has had a long running quirk where a Player would ask for an updated Widget, the CMS would generate one containing new images, which it added to the Players required file list. The Player would show the new Widget but may not have finished downloading the associated images.

Xibo has another quirk where a Widget is loaded and the Player decides that it needs to request a fresh version. It does so, but it cannot wait for that to be returned, so its shows its current version, knowing that the updated one will be shown next time. This can result in stale data that is twice as old as expected.

How is it being solved?

The solution to this comes in 2 parts - firstly the Widget caching introduced in 1.8.8, improved in 1.8.9 and secondly a "Widget Sync" task in 1.8.10.

Prior to 1.8.8 the CMS cached all 3rd party resources (RSS, Twitter, etc) for a predefined period of time. If the resource was in the cache, it generated the Widget based on that cache each time it was requested. Post 1.8.8 the entire Widget is cached as well, based on criteria for each Widget.

The "Widget Sync" task is run by the CMS's task runner and every 5 minutes looks for Widgets that are active on any Display. If it finds any it updates their cache if required, including any images.

If this task is scheduled to run the Player should only ever be served content from the cache, meaning all of the files will be present and the Widget will be fresh at the point the Player sees it.

Spring Signage are pleased to announce Xibo for webOS v1.8 R11. This release works with Xibo CMS version 1.8.3 onward.

This release contains 9 improvements:

• The "Connect to CMS" options will stay on screen until manually dismissed or saved, instead of timing out
• XMR will reconnect reliably if it becomes disconnected
• Player will obey the logging level configured in the Display Settings
• Fixed "Unable to read property" error shown repeatedly in the logs
• Fix a problem with the splash screen not showing correctly on Displays with portrait orientation
• Unplayable Videos will be skipped instead of sitting at a black screen
• It is now possible to configure key locks to block the operation of on-monitor keys and remote control keys
• The Mac Address of the in use interface will be reported
• Opening the application triggers an update of all Widgets immediately as opposed to waiting for the first collection.

Download Xibo for webOS R11.

Instructions for upgrading from an earlier release can be found in the FAQ at the end of the installation guide. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

We are pleased to announce our 10th bug fix release for the 1.8 series of Xibo. The codename for this series is “Tempel”.

A new CMS is available with this release, with 68 resolved issues. We recommend that all users running 1.8 upgrade their CMS to this release.

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

There are some special considerations to note in this release.

Google Traffic Module

Google are making changes to their Traffic API billing and terms. Please read our blog post for more information and the actions you need to take. If you do not act your Traffic Widgets may cease to function or you may face higher than expected bills for your usage from Google!

Dropdown Lists

This release also improves the drop-down selection lists for Layouts, Media and Displays in the CMS. We found that in CMS instances with a large amount of Layouts, Media and/or Displays, the user interface could become unresponsive and hard to use. We have improved this by filtering and paging drop-down lists for these types of data so that they open faster.

Widget Sync

We've also made improvements to the way we manage Widget Caching and updating 3rd party resources, such as Tickers and Twitter. Please read our blog post for more information.

Calendar Module

In response to customer feedback we have included a new Module which shows an iCal feed on a Layout - the Calendar Module. To get started with this great new module take a look at our new guide on the community.

Chart Module

Adding to the work he did with Remote DataSets in 1.8.4, LukyLuke is back with another fantastic contribution. The Chart Module can be used to show various Chart types on a Layout, based on data in a DataSet (perhaps even a remote one!). Have a go yourself with our new walkthrough guide on the community.

We are pleased to announce Xibo for webOS v1.8 R12. This release works with Xibo CMS version 1.8.3 onward.

This release fixes an issue with the Player not progressing past the "Loading..." screen when it is restarted or turned on without a network connection.

Download Xibo for webOS R12.

Instructions for upgrading from an earlier release can be found in the FAQ at the end of the installation guide. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

We are pleased to announce our 11th bug fix release for the 1.8 series of Xibo. The codename for this series is “Tempel”.

A new CMS is available with this release, with 44 resolved issues. We recommend that all users running 1.8 upgrade their CMS to this release.

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

Xibo Signage are pleased to announce Xibo for Android v1.8 R107. This release works with Xibo CMS version 1.8 and has legacy mode for versions 1.4, 1.6, 1.7.

Features and Issues resolved in this release:

• Press the home button when Xibo is open and choose to use Xibo as a Launcher.
• Fix for "unexpected end of document" causing the splash screen to appear during some connection outages.
• Fix for XMR crashing and showing a "this application has stopped" window.
• New feature to run an intent when someone touches the screen.
• Fix for cookie support when showing a webpage in Manual Position/Best fit mode.

Download Xibo for Android R107.

Download Xibo for Android R107 for DSDevices J18 and J19.

Instructions for upgrading from an earlier release can be found in the FAQ. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

Become a Xibo Signage Channel Partner!
Would you like to represent the Xibo brand by becoming a Channel Partner? Apply now. https://xibo.org.uk/become-a-partner

Summary

Alpine Linux, the container Linux distrubution upon which Xibo’s Docker containers are based has said there is a flaw in the way their package manager (apk) works. This flaw could potentially allow an attacker to inject their own code in to the container at build time.

We have no evidence to suggest that any Xibo containers have been “poisoned” in this way, however, we have issued an updated 1.8.11 CMS container and 0.7 XMR container as a precaution.

If you’re using Xibo on our Cloud service, then you don’t need to take any action. You are already protected, regardless of the version you are running.

If you are running Xibo with Docker, it's our recommendation that you upgrade to the 1.8.11 CMS container and 0.7 XMR container released today (15th September 2018).

If you are already on 1.8.11, then you will need to issue a docker-compose pull command, followed by a docker-compose up -d command (coupled with any -f switches you normally use). See below for further examples.

If you're on an earlier version of the Xibo CMS, you can simply upgrade to 1.8.11 in the normal way.

Overview

You may have read in the news that the Alpine Linux distribution, upon which many Docker containers are based, has reported that their apk package manager is potentially vulnerable to a “poisoning” attack where an attacker could use a man-in-the-middle attack to inject code in to a container during the build process.

Xibo uses Alpine as the basis for its Docker containers, as is common through the industry as Alpine is specialised for that task. Xibo's Docker containers are built directly by Docker's Cloud service, an independent trusted third party, so you have total transparency as to what is included in them.

The Vulnerability

According to reports, an attacker with access to the network in the build environment could potentially poison a container during the build process by injecting their code in to the Alpine package manager and it would include that code inside the resulting container.

Alpine have published an updated version that prevents that happening, and have rebuilt their base containers upon which our containers are based.

Our Response

We have no evidence to suggest that the Xibo containers have been poisoned in this way, however, as a precaution, we have decided to rebuild the CMS container for 1.8.11 and XMR container for 0.7 to make available a version with the fix provided by Alpine Linux included.

Our recommendation therefore if you're running with Docker is to ensure you are running the 1.8.11 container that we have released today (September 15th 2018).

If you're running an earlier version of Xibo, you can simply upgrade in the normal way. If you're running 1.8.11 already, you will need to manually pull the new version of the container and then up the containers again:

docker-compose pull
docker-compose up -d

If you normally use a -f switch (eg -f cms_custom-ports.yml) don't forget to add that in:

docker-compose -f cms_custom-ports.yml pull
docker-compose -f cms_custom-ports.yml up -d

Full details of the original vulnerabilty can be found here:
https://justi.cz/security/2018/09/13/alpine-apk-rce.html
https://www.theregister.co.uk/2018/09/15/alpine_linux_bug/

We are pleased to announce Xibo for webOS v1.8 R13. This release works with Xibo CMS version 1.8.3 onward.

This release fixes an issue checking licences in non-UTC timezones.

Download Xibo for webOS R13.

Instructions for upgrading from an earlier release can be found in the FAQ at the end of the installation guide. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

Xibo Signage are pleased to announce Xibo for Android v1.8 R108. This release works with Xibo CMS version 1.8 and has legacy mode for versions 1.4, 1.6, 1.7.

Features and Issues resolved in this release:

• Blacklist MAC Addresses for certain Android 7 devices (00:15:18:01:81:31) and the Neo-U9-H.
• Add extra logging to help diagnose CMS connection problems
• Default name for new Players changed from "Android" to the Device Serial Number for easy identification in the CMS.
• Improved system signed applications so that they do not need to run as the system user.

Please note we have had reports that some devices will show a "Launcher decision" popup on reboot. If you haven't done so already, please make sure you reboot after upgrading your device to make this selection.

Download Xibo for Android R108.

Download Xibo for Android R108 for DSDevices J18 and J19.

Instructions for upgrading from an earlier release can be found in the FAQ. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

We are pleased to announce Xibo for webOS v1.8 R14. This release works with Xibo CMS version 1.8.3 onward.

This release contains 3 fixes/improvements:

• We now support the LG E-Series of monitors! The supported monitors list has been updated to include this new series of monitors from LG.
• We fixed an issue with On/Off Timers not working properly when lots of Timers have been set.
• We fixed an issue where an invalid default Layout would prevent the rest of the Schedule being shown.

Download Xibo for webOS R14.

Instructions for upgrading from an earlier release can be found in the FAQ at the end of the installation guide. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

We are pleased to announce Xibo for webOS v1.8 R15. This release works with Xibo CMS version 1.8.3 onward.

This release contains 6 fixes/improvements:

• We fixed a critical issue with some players getting stuck on the Loading screen.
• We fixed an issue with expired trials and the way content was shown.
• We improved the management of local storage and tidied up temporary files more effectively.
• We store proof of play statistics in a local database rather than in memory.
• We improved the logic for migrating to a new CMS if the CMS address was changed.
• We added some extra logging so that the firmware and model number are available on the status window.

Download Xibo for webOS R15.

Instructions for upgrading from an earlier release can be found in the FAQ at the end of the installation guide. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

Please note that Xibo Signage will close on Monday 24th December at 12:00 noon for the UK Christmas holidays and will re-open at 8am on Thursday 27th December. We will then be open as usual until Monday 31st December. We are then closed all day on Tuesday 1st January 2019 and return to normal hours from Wednesday 2nd January 2019.

If you require support during these closures, please contact our service desk and we will be in touch as soon as we are able.

The team at Xibo Signage wish you all seasons greetings and best wishes for 2019.

We're very excited to be releasing today the second public "Technology Preview" of our forthcoming Player for Linux.

We're aiming to gather some feedback from the Community on how well the Player runs on the various types of hardware that you anticipate running a Linux Player on, as well as seeing what issues might be encountered.

This version builds on the functionality of the first public preview, and is now able to connect to a CMS over HTTP, and download whatever layout has been set as default, and then run that layout.

There's also been a whole raft of changes under the hood.

If you'd like to test the new Player, a small patch needs to be applied to your CMS to allow it to support the new type of Player. To make the patch:

• Download the XiboForLinuxMiddleware PHP file, extract it, and put it in /shared/cms/custom if you are using Docker and /custom on a manual installation.
• Update your settings-custom.php file, or add to your settings.php file for non-Docker based installs, the following new Middleware

$middleware = [new \Xibo\Custom\XiboForLinuxMiddleware()];

If successful you should see a new Display Profile for Linux added to your CMS whe you visit the Display Settings page.

Once your CMS is prepared, we'll need to get the Player installed. We're now using an improved distribution system based on snapcraft "snap" packages to package the Player for deployment. It offers a clean, dependency free installation, as well as the potential for automatic upgrades in the future.

Many Linux distributions support snap packages out of the box now, but we've tested with Ubuntu 16.04 LTS 64 bit and 18.04 LTS 64 bit.

To install the Player, simply run:

snap install xibo-player-test --channel=beta

The Player will be installed without affecting any other software you might have installed on your machine.

To run the Player, change in to a directory where you want us to store the layout and media files (a temporary directory or a new empty directory is perfect), and then run

xibo-layer-test --host yourcms.example.org --server-key yourkey --hardware-key yourhardwarekey

The server key is the one you would normally use to register Players with the CMS. The hardware key is normally generated for you (and in the future it will be, but for now you can use a random string to identify this display).

The Player will register with the CMS. Press Ctrl+C in the terminal window to quit.

Now in the CMS, authorise the display as normal. You can set a default layout for the Player to show, and then run the Player again.

On each run, the Player will download the layout from the CMS, and render it for you.

Please let us know of any rendering issues you encounter in the comments below. Depending on the respose we get to this we may not be able to answer each comment individually, but will be reading the responses and investigating where feasible.

When you're finished testing, you can safely delete the files the Player created in your temporary directory, and if you want to remove the Player from your system, simply run

snap remove xibo-player-test

and the Player will be cleanly removed.

We are proud to announce the release of our first development preview for the 2.0 version of Xibo. The codename for this version is “Swift”.

Originally discovered on November 27, 1869 by Tempel (the codename for our 1.8 release), the 11P/Tempel–Swift–LINEAR comet was rediscovered by Swift on October 11, 1880, lost and rediscovered again by LINEAR on December 7, 2001.

2.0.0-alpha is a development preview only and should not be used in production. You can upgrade to this release from 1.8 series.

We have had 4 focus points for this version:

• Improved Layout Design experience
• Playlists
• Draft/Published Layouts
• Database Schema migrations for Upgrades

This alpha is a CMS only release - Player releases will follow in due course and you can use a 1.8 Player against a 2.0.0-alpha CMS.

Layout Designer

We've redesigned our Layout Designer from the ground up, with the new design being based on feedback from thousands of users with years of experience. The 'key brief' to bring about a simplified process for designing a Layout and to make that experience flow without interruption.

There is a new Toolbox, located at the bottom of the screen for adding Widgets and Library Media which includes tabs for searching in the Library. We've also given the toolbar a memory so that when you next open Xibo, you can pick up right where you left off.

We've enhanced how you position and size Regions on a Layout by using a Layout Navigator, located in the top left and made the Region timeline always visible. We've also included smarts to estimate when items will be shown in time with each other.

Playlists

Xibo has always had Playlists, but they've been single-use and hidden away inside Regions, making them inflexible.

We've extracted this concept out into its own Playlists Page accessible from the Library. You can now name and reuse these Playlists across multiple Layouts and Regions. Each Playlist you create has a timeline which can hold all Xibo's Widgets, even Sub-Playlists, which are assigned using the Toolbox. With the use of search criteria, Playlists can also be pre-populated on creation or dynamically kept up to date.

To assign a Playlist to a Layout you simply use the Sub-Playlist Widget. This Widget allows one or more Playlists to be selected and, if more than one is selected, you can decide how the Widgets on that Playlist are combined in the Region.

Draft/Published Layouts

We've all been there - you have a Layout playing across your inventory and notice a typo, wrong logo being used, or that the date isn't quite correct. Currently, you need to go into Xibo to change it, make an adjustment and all Displays immediately download and play the Layout while you are still making changes...

We've solved that problem with Draft/Published on Layouts!

Before you can make any change to a Layout in 2.0 you need to Checkout to change the Layout to a Draft Layout. Changes made to a Draft Layout are never sent automatically to Displays, so you can take your time with edits. When you're done you can either Publish to make those changes permanent, at which point the Layout will be sent, or Discard to go back to the original Published version.

Database Migrations

We have adopted a tool called Phinx to help us manage database schema changes between versions. 1.8 and earlier had a tool developed in-house, which grew complex over time. Phinx gives us a strong framework to author and test migrations so that we can improve our database updates moving forward.

Download

We're making this alpha available for people to try using our recommended installation method, Docker. We will be providing release files for the stable 2.0.0 release for those of you running without Docker in due course.

• Xibo for Docker - Linux / Windows

Future development

Our immediate development work will be to prepare a 2.0.0-beta release which will add more polish to all the features we've put in 2.0 so far. We will also be responding to your feedback and any bug reports.

Beyond 2.0 we've begun working on 2.1, which will focus on improvements to Proof of Play statistics.

We're improving our release cycle - you can read about that here.

We are pleased to announce Xibo for webOS v1.8 R16. This release works with Xibo CMS version 1.8.3 onward.

This release contains 1 fix:

• We fixed an issue processing schedules which contain a mixture of priority and non-priority schedules

Download Xibo for webOS R16.

Instructions for upgrading from an earlier release can be found in the FAQ at the end of the installation guide. It’s also well worth having a look at the Knowledge Base.

If you have a white label build of the application it is available in your account.

Today we're making available another preview of the forthcoming Player for Linux.

This new version supports downloading and processing the schedule from the CMS and is for the first time long-running, so it will switch between layouts as dictated by the CMS schedule. Overlay and command schedules are not supported.

It has no file management yet, so will download everything from the CMS on each collection, so it isn't suitable for use on anything other than a test CMS at the moment. It should not be used for production use.

Please see the post for the 0.3.3-alpha release for instructions on configuring your CMS to support the new Player.

Note also that you must have the File Download Mode in your CMS set to Apache or NGINX and your webserver correctly configured to support that. If you're using Xibo with Docker, then that has already been done for you.

Once your CMS is prepared, we'll need to get the Player installed. We're now using an improved distribution system based on snapcraft "snap" packages to package the Player for deployment. It offers a clean, dependency free installation, as well as the potential for automatic upgrades in the future.

Many Linux distributions support snap packages out of the box now, but we've tested with Ubuntu 16.04 LTS 64 bit and 18.04 LTS 64 bit.

If you previously installed 0.3.3a and haven't removed it, then it will automatically upgrade in due course to 0.4a. You can force that to happen now by running:

snap refresh xibo-player-test --channel=beta

You can check to see what version of the Player you have installed by running

snap list

You should see an entry in the output like this:

Name                  Version         Rev   Tracking  Publisher     Notes
xibo-player-test      0.4-alpha       50    beta      stivius       -

If you've never run the test Player before, or you previously removed the snap package, then to install the Player, simply run:

snap install xibo-player-test --channel=beta

The Player will be installed without affecting any other software you might have installed on your machine.

To run the Player, change in to a directory where you want us to store the layout and media files (a temporary directory or a new empty directory is perfect), and then run

xibo-player-test --host yourcms.example.org --server-key yourkey --hardware-key yourhardwarekey

The server key is the one you would normally use to register Players with the CMS. The hardware key is normally generated for you (and in the future it will be, but for now you can use a random string to identify this display).

The Player will register with the CMS. Press Ctrl+C in the terminal window to quit.

Now in the CMS, authorise the display as normal. You can set a default layout for the Player to show, and then run the Player again.

On each run, the Player will download the layout from the CMS, and render it for you.

Please let us know of any rendering issues you encounter in the comments below. Depending on the respose we get to this we may not be able to answer each comment individually, but will be reading the responses and investigating where feasible.

When you're finished testing, you can safely delete the files the Player created in your temporary directory, and if you want to remove the Player from your system, simply run

snap remove xibo-player-test

You can see a list of known issues here:
https://github.com/xibosignage/xibo-linux/blob/13f698c439533d659c2ffa9a553e24122ccc08a9/CHANGELOG.md

In addition, we know there are issues with the Player connecting to servers that support only HTTPS connections, or that run on non-standard port numbers.

We are proud to announce the release of our first beta for the 2.0 version of Xibo. The codename for this version is “Swift”.

Originally discovered on November 27, 1869 by Tempel (the codename for our 1.8 release), the 11P/Tempel–Swift–LINEAR comet was rediscovered by Swift on October 11, 1880, lost and rediscovered again by LINEAR on December 7, 2001.

2.0.0-beta is a should be used for testing only and not be used in production. You can upgrade to this release from 1.8 series.

We have had 4 focus points for 2.0:

• Improved Layout Design experience
• Playlists
• Draft/Published Layouts
• Database Schema migrations for Upgrades

If you're interested in reading more about these things and what they mean for Xibo, please take a look at our 2.0.0-alpha blog post.

This beta is a CMS only release - Player beta releases will follow in due course and you can use a 1.8 Player against a 2.0.0-beta CMS.

We will leave you with a teaser screenshot of the new Layout Designer!

Download

We're making this beta available for people to try using our recommended installation method, Docker. We will be providing release files for the stable 2.0.0 release for those of you running without Docker in due course.

• Xibo for Docker - Linux / Windows

At Xibo we have a big plan, which is to make digital signage available to everyone! We want every business and organisation to be able to leverage the benefits that digital signage can bring. That is why we have introduced subscription pricing for our commercial players and hosting products.

What does this mean?

To put it simply, you can now purchase our Android, webOS and Tizen commercial players on an annual or monthly basis, and remove the upfront expenditure. And the same applies for our Xibo in the Cloud product.

If you prefer you can still purchase our licenses on a perpetual basis, choose whichever model is best for your business.

Stay current with free upgrades

If you are not already convinced, bug fixes, minor and major software version upgrades are available also for free. As you are on a subscription, you can keep up to date with the latest Xibo releases at no extra cost.

Some pricing examples

Here are some examples of what you would pay per display (excluding applicable taxes).

• One Android display license = $18 per year or $1.50 per month
• One webOS or Tizen display license = $72 per year or $6 per month
• One Xibo in the Cloud display slot = $20.40 per year or $1.70 per month

So if you had 10 Android displays with Xibo in the cloud, that would cost just $32 per month. Bargain right?

Note: Examples use pricing on 25/01/2019, please check the shop the latest pricing. Taxes may apply.

Minimum volumes do apply for monthly purchases as per below.

• For Android you need to purchase 10 or more display licenses
• For Xibo in the cloud you will need to purchase 10 or more display slots
• For webOS and Tizen you will need to purchase 3 or more display licenses.

Get started

Visit our shop and get started. Or if you need help, get in touch with our sales team on sales@xibosignage.com

We are pleased to announce our 12th bug fix release for the 1.8 series of Xibo. The codename for this series is “Tempel”.

This release improves the stability and scalability of the Xibo platform through 84 bug fixes and improvements.

Download

Please use the links below to download this release:

• Xibo for Docker - Linux / Windows
• Xibo for Apache/Nginx / WAMP/IIS

You may use any 1.8 series compatible Player with this release. We are pleased to provide an updated Windows Player as part of this release. Download Xibo for Windows.

Upgrade

The CMS can be upgraded to later versions - we recommend all users upgrade when possible to take advantage of the latest bug fixes and features. Please refer to the upgrade guide.

Changelog

Please find below a complete list of changes in this release.

bug

• 1722: Theme for Analogue Clock states Light regardless of settings. thanks to @DanielBW1
• 1717: File uploads don't work in PHP7
• 1716: File uploads take a long time to process after reaching 100%
• 1714: Currencies module - the API endpoint of exchangeratesapi.io has changed thanks to @PeterMis
• 1712: Schedule: Repeat Hourly shows incorrect date/time on Agenda view thanks to @DanielBW1
• 1703: CMS Proxy Credentials field won't accept \ characters thanks to @alexharrington
• 1702: Displays are not retaining up to date Status. Returning to Cloud Icon shortly after a Collect. thanks to @DanielBW1
• 1701: Ticker: If Number of Items is empty, Ticker will start at beginning of the Feed thanks to @DanielBW1
• 1700: Overlay Layout does not acknowledge changes to the Overlay Layout whilst scheduled. thanks to @DanielBW1
• 1698: Syntax Error when Adding/Editing Row for Remote Dataset thanks to @DanielBW1
• 1694: Media Download Queue not cleared on completion
• 1688: Widget Sync struggles on larger installations
• 1684: Some settings help text mentions Xibo thanks to @dasgarner
• 1683: Media Library - Sort by Revised returns no results thanks to @alexharrington
• 1680: Ticks Disappear from Permission Check boxes when page is changed thanks to @DanielBW1
• 1678: Time Disconnected Statistics not displaying accurately thanks to @DanielBW1
• 1677: Remote DataSet - Date dataType column is set to null on fetch data thanks to @PeterMis
• 1676: Media Dashboard - the module dropdown should show only enabled modules thanks to @PeterMis
• 1675: Status Dashboard - Bandwidth graph shows incorrect data thanks to @PeterMis
• 1673: http downloads not being bandwidth limited thanks to @DanielBW1
• 1669: Replace Media Not automatically closing/ allows multiple file selection thanks to @DanielBW1
• 1664: Error: Undefined index: scheduleId in /lib/Xmds/Soap.php on line 402 thanks to @DanielBW1
• 1661: Local Video, Video and Video In Widget message incorrect thanks to @DanielBW1
• 1660: Stocks Widget reports Change value incorrectly thanks to @DanielBW1
• 1659: Importing a Layout into the CMS sets useDuration to 0 thanks to @DanielBW1
• 1657: Export layout broken where a media item has been edited thanks to @alexharrington
• 1653: Users removed from User group when Saved thanks to @DanielBW1
• 1650: Weather Widget: "Concurrent record locked, time out" error when not configured correctly thanks to @DanielBW1
• 1648: cannot import Layout if resolution setting does not exist thanks to @DanielBW1
• 1645: Scheluded events spanning more than 1 month on repeat not appearing on schedule for following month correctly thanks to @DanielBW1
• 1644: Region Timeline - Image hoverPreview cache issue thanks to @PeterMis
• 1643: ca-certs import added in 1.8.11 broken thanks to @alexharrington
• 1638: About Page needs to be updated thanks to @DanielBW1
• 1637: Display Page - Status description does not show on hover thanks to @PeterMis
• 1636: Import Backup Database Not working thanks to @DanielBW1
• 1635: Regular Maintenance errors when someone has set up WoL and the display hasn't given a MAC address yet thanks to @dasgarner
• 1633: Upgrade from 1.7.10 fails due to fixing indexes thanks to @dasgarner
• 1632: Cannot remove tags from Displays thanks to @DanielBW1
• 1631: Notifications - Audience not saved correctly on Edit thanks to @PeterMis
• 1628: Layouts: Media Filter poor performance thanks to @dasgarner
• 1626: Calendar - not always returns correct items from the ics thanks to @PeterMis
• 1625: Media Dashboard - not showing all data it should thanks to @PeterMis
• 1621: Tasks: MySQL has gone away, task status error and deactivated thanks to @dasgarner
• 1620: DataSetColumn Grid sort doesnt do anything thanks to @dasgarner
• 1619: Clock - Flip Clock Counter does not work thanks to @PeterMis
• 1616: Cache problem. Layout list, preview image (thumbnail) not updating thanks to @avanceja
• 1608: DataSets - library Image column can cause the row to become inaccessible thanks to @PeterMis
• 1607: Schedule - Add/edit event forms require displayGroup and campaign page permissions thanks to @PeterMis
• 1689: Windows Player not resizing correctly
• 1681: User unable to schedule Event, unless permitted displays are selected in the Select Displays box first. thanks to @DanielBW1
• 1658: DataSet Data - Library image impossible to clear the selection thanks to @PeterMis
• 1618: Status Dashboard shows 0 displays thanks to @dasgarner
• 1617: Fixes to DataSetView break formatting on users who have overridden the template thanks to @dasgarner

enhancement

• 1710: Statistics: Filter by tag
• 1708: DisplayProfile Copy
• 1693: Support additional headers for queue downloads
• 1690: Library: Media Copy functionality
• 1687: Ticker: Option/Setting for image update interval
• 1686: Tasks: It shouldn't be possible for a task to run more than once per XTR poll thanks to @dasgarner
• 1679: Time Disconnected Report - Add Time Connected thanks to @alexharrington
• 1674: Add Bandwidth graphing for deleted Displays thanks to @DanielBW1
• 1671: M4V as a valid extension for Video thanks to @DanielBW1
• 1667: Twitter Metro: Add/Edit for incorrect dialog title thanks to @dasgarner
• 1665: Module: Stocks improve “items” and wording an help text (Enhancement) thanks to @Tashamy
• 1663: Module: DataSet View: Change title to DataSet View thanks to @dasgarner
• 1662: Module: Currencies - improve "items" wording and help text thanks to @dasgarner
• 1651: Displays: Filter by additions thanks to @dasgarner
• 1649: Setting to auto-authorise new Displays thanks to @dasgarner
• 1646: Rename "Dashboard" to "Icon Dashboard" to match the manual thanks to @dasgarner
• 1639: api call : /stats Lacking displayId for proofOfPlay thanks to @jeanfrancoisnoel
• 1627: Api displayprofile Get return empty config Array xibo docker xibo-docker-1.8.10 thanks to @firestorms321
• 1624: Settings: Default mail_from and mail_to should be empty thanks to @dasgarner
• 1623: Users: Forgotten Password reset thanks to @dasgarner
• 1622: Users: Force password change next login thanks to @dasgarner
• 1615: Investigate Mcrypt thanks to @alexharrington
• 1605: DataSet: Publish as RSS thanks to @dasgarner
• 1576: Auto-enable the Thumbnail column when the user requests a screenshot thanks to @alexharrington
• 1692: Assign from Library: Show and Filter by Tags
• 1691: Templates: Permissions Column should not be sortable
• 1640: PHP readfile() output buffering OOM issue thanks to @PeterMis