Our recent release gives you two great settings that can be enabled for User Passwords.

Forgotten your Password? - Reset at login.

Save time and enable a link to be made available to Users who have forgotten their Password so they do not have to wait for this to be reset by a Super Admin in order to gain access to the CMS. With this enabled, a User can simply click on the link to send a Password Reset Notification to their saved email address.

This feature can be activated by Super Admin Users by navigating to Settings under the Administration section of the Menu and selecting the Users tab.

Force Password Change at next login.

Ensure that new Users update the Password first given to them the next time they log in to the CMS. This option is set at the individual User level by accessing Users under the Administration section of the Menu. Edit the User record and select Force Password Change from the Options tab.

Two helpful features to help you get the best out of Xibo!

We have looked at how we can make Upgrading Players that little bit easier in the CMS without the need for User's having to select many Displays or Display Groups to do a simple Player Version upgrade, and so we have done exactly that...

Once the latest Player Version has been downloaded from the Download Centre upload to the CMS from the Player Versions page of the CMS menu...

...navigate to Display Settings to edit the appropriate Display Profile, from the Advanced tab select the Version using the drop down.

All Displays assigned to that Display Profile will download the new version and install it during the next configured download and upgrade window!

We have also included a Player Version Override option for Displays you wish to run an alternate version. Simply assign a different Player Version for selected Displays before upgrading the Player Version on the Display Profile.

Please note: Windows Player upgrades are not supported in this way.To upgrade Windows Players you will need to install the new version as detailed in the Installation Manual.

Full information on Upgrading Players can be found in our Administrator Manual

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.2 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.2 CMS.

We will leave you with a teaser screenshot of the new Playlist Feature!

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

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

This new version supports connecting to CMS instances over http or https, and to CMS instances that run inside sub directories, or on custom ports. It also supports legacy XMDS file downloads so no special configuration of the CMS File Download Mode is required.

In addition, it manages its local files so it should download content once only from the CMS and then maintain that local library.

If you have a 1.8.12 CMS, then you can connect the Player directly to that as it already has support for Linux Players. You may need to create a Display Settings Profile for the Linux Player ahead of connecting your first Linux Player. Not all of the settings in the Display Settings Profile will work at present, but we've included them now in readiness for them being implemented in to the Player.

If you have an earlier 1.8 CMS, then please see the post for the 0.3.3-alpha release for instructions on configuring your CMS to support the new Player.

Once your CMS is ready, 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 or 0.4a and haven't removed it, then it will automatically upgrade in due course to 0.5a. 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.5.1-alpha     59    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 https://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

We are proud to announce the first release candidate 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-rc1 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.

Also included are some improvements over 2.0.0-beta.2, such as:

• Improved webOS/Tizen display settings
• A mechanism so that display settings can be overridden on an individual display
• Repeating Schedule settings for a particular week day in the month
• Improvements to the way the inline text editor works
• A horizontal menu option
• An updated tour (this is a work in progress and we hope to have it completed for rc2)

Download

Please use the links below to download this release:

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

This release is also available on Xibo in the Cloud.

You may use any 1.8 series compatible Player with this release.

Xibo are pleased to announce Xibo for Windows v2 R200. This release works with Xibo CMS version 2.0 and has legacy mode for version 1.8.

Features and Issues resolved in this release:

• Support for Xibo CMS 2.0
• Switch Video from a Region to full screen at run time
• Widget From/To dates
• Packaged HTML module

Download Xibo for Windows R200.

Instructions for upgrading from an earlier release can be found in the FAQ.

If you have a white label build of the application, the upgrade is available in your Xibo customer portal account.

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

Features and Issues resolved in this release:

• Support for Xibo CMS 2.0
• Switch Video from a Region to full screen at run time
• Widget From/To dates
• Packaged HTML module
• Philips integration (remote reboot and upgrade, video screenshot, LED control)
• Ability to act as the device owner if installed as part of the firmware

Download Xibo for Android R200.

Download Xibo for Android R200 for DSDevices J18 and J19.

Upgrading from an earlier release

We are providing licence upgrades to this release, free of charge, for any licences purchased since 12 December 2018. Check your eligibility by looking at the number of upgrades your licence pool has been assigned in the Xibo customer portal.

Upgrades for licences purchased prior to this date are available for £4 GBP, per licence.

If you have a subscription licence, this upgrade is included within your subscription.

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, the upgrade is available in your account.

We are proud to announce the first release 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.

We have had 4 focus points for 2.0:

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

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 Layout 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, 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. If more than one is selected, you can decide how the Widgets on that Playlist are arranged 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 right. 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 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.

Other improvements

We haven't stopped there! There are plenty of other improvements in version 2, such as:

• Improved webOS/Tizen display settings
• A mechanism so that display settings can be overridden on an individual display
• Repeating Schedule settings for a particular week day in the month
• A horizontal menu option
• An updated product tour for new users

Download

Please use the links below to download this release:

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

This release is available on Xibo in the Cloud!

There are new Players available with this release:

• Xibo for Windows
• Xibo for Android
• Xibo for webOS: coming soon

You may use any 1.8 series compatible Player with this release. Please be aware that 1.8 series Players will not support the new v2 features.

Keep in touch

We have a lot planned for this year and have already started work on 2.1! Follow us on Twitter to be kept up to date.

Find out how our version numbers will work from this release.

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

This release contains 9 fixes and improvements:

• On-premise licensing now available
• Overlay Layouts update correctly
• Improvements to the status window showing Overlay Layouts
• Fixed the "failed to parse Layout" error
• Better reporting for licensing
• Connect to a v2 Xibo CMS in legacy mode
• Codec improvements for SM5KE series
• Download window in Display Settings is now honoured

Download Xibo for webOS R17.

Instructions for upgrading from an earlier release can be found in the Upgrade 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 v2 R200. This release works with Xibo CMS version 2.0.0 onward and is backwards compatible with Xibo CMS 1.8.3 onward.

Features and Issues resolved in this release:

• Support for Xibo CMS 2.0
• Switch Video from a Region to full screen at run time
• Widget From/To dates
• Packaged HTML module

Download Xibo for webOS R200.

Upgrading from an earlier release

We are providing licence upgrades to this release, free of charge, for any licences purchased since 12 December 2018. Check your eligibility by looking at the number of upgrades your licence pool has been assigned in the Xibo customer portal.

Upgrades for licences purchased prior to this date are available for £16 GBP, per licence.

If you have a subscription licence, this upgrade is included within your subscription.

Instructions for upgrading from an earlier release can be found in the Upgrade 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.

The Layout Designer gives you design flexibility and is at the heart of content creation in Xibo!

Add and position Regions to define areas of your Layout.

Assign content using Widgets or media uploaded to the CMS Library.

Give Widgets Start and End dates using the Toolbar.

Re-order your content and edit assigned Widgets from the Layout Timeline.

Preview each stage of your design…

... to ensure it will play as intended.

Once you are happy with your design set to Publish and even Schedule Now, all without leaving the Layout Designer!

We are pleased to announce the release of our first development preview for the 2.1 version of Xibo. The codename for this version is “Brooks”.

The 12P/Pons–Brooks comet was discovered 12 July 1812 and has an orbital period of 70.85 years. It will next be closest to Earth in 2024.

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

Proof of Play

The main focus of this release is to improve the Proof of Play statistics collection, storage and presentation.

There are 3 main changes to address this:

• Layout/Media and Widget settings to control whether statistics are collected for an item.
• Collection Aggregation settings on the Display Settings Profile to configure Hourly/Daily/Individual statistics aggregation (requires a supported Player).
• Introduce a MongoDB statistics storage module for high-volume stats collection.

We are also hoping to provide more reporting options for Proof of Play, an example is provided in this alpha release:

Bugs

In addition there are 7 bugs closed in this release and 14 bugs closed from the upcoming 2.0.1 release.

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.1.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.1.0-alpha2 release which will add more polish to all the features we've put in 2.1 so far. We will also be responding to your feedback and any bug reports.

Beyond 2.1 we've begun planning 2.2, which will focus on improvements to the Scheduling capabilities of Xibo.

As well as a brand new Layout Designer, version 2.0.0 gives you a Layout status to give you all the time you need to make changes, without impacting on your scheduled content!

A Layout with a Published status is locked for editing and can be viewed in a Read Only mode, Checkout to enable editing.

Use the row menu for the Published Layout you want to make edits to and click on Design...

...click to Checkout at the bottom of the screen and put the Layout into a Draft status to allow for editing.

Spotlight Tip: The Checkout button on the row menu can be used for when you need to mark a Layout as a draft to make changes later!!

Once you are happy with changes made, confirm edits by clicking on the Publish button, located on the bottom toolbar.

Checkout ensures that your Layout will not be disrupted in any current schedules with your audience only seeing what you want them to see. Your original version will remain untouched until you tell Xibo to overwrite it with Publish!

Just one of the many new features of 2.0.0.

We are pleased to announce our 1st patch for Xibo CMS v2.0. The codename for this series is “Swift”.

This patch improves the stability and scalability of the Xibo platform through 14 solved issues.

Download

Please use the links below to download this release:

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

If you have a v2.0 Xibo in the Cloud CMS then you have been updated with this patch automatically.

You may use any v2 compatible Player with this patch. At the time of writing these are the latest:

• Xibo for Windows
• Xibo for Android
• Xibo for webOS

1.8 series Players will also function but please be aware that new v2 features will not be supported.

Changelog

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

bug

• 1774: Publish layout does not work when it is assigned to display/displayGroup
• 1773: Remote Dataset returns Xibo-based placeholder when the remote server is unavailable, left blank or has SSL issues
• 1769: Permissions lost on layout publish
• 1768: CMS Installation fails against MySQL 5.7
• 1767: Exceptions option in Custom Daypart not appearing
• 1757: Layouts with no background colour set don't show correctly in the new layout designer
• 1755: Proof of Play page - Layout filter search does not work
• 1753: Media Manager - filter by Layout or Region throw SQL error
• 1772: apereo/phpcas missing in vendors thanks to @moobyfr
• 1771: DataSetTicker dropdown search doesn't search
• 1765: User Option to disable switching Display Thumbnail column when Requesting a Screenshot
• 1762: Font Awesome for non-root folder installs
• 1754: Only the first Widget in the Layout Preview gets rendered
• 1764: Scroll bar for Region Timeline does not remember previous position.

Keep in touch

We have a lot planned for this year and have already started work on 2.1! Follow us on Twitter to be kept up to date.

Find out how our version numbers work.

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

This new version has the following changes over 0.5a:

• We have switched to our permanent snap publisher and application name (xibosignage/xibo-player)
• We have switched our version numbers to match the other Players in the Xibo suite.
• We have fixed connecting to a CMS protected by SSL with SNI, which was one of the issues reported from 0.5a test.

We will continue to address the other feedback and issues found. You can see a list of known issues and other things we're working on here. We know there are problems with memory leaks, and this release is not intended to fix that.

Prepare your CMS

If you have a 1.8.12 CMS, then you can connect the Player directly to that as it already has support for Linux Players. You may need to create a Display Settings Profile for the Linux Player ahead of connecting your first Linux Player. Not all of the settings in the Display Settings Profile will work at present, but we've included them now in readiness for them being implemented into the Player.

If you have an earlier 1.8 CMS, then please see the post for the 0.3.3-alpha release for instructions on configuring your CMS to support the new Player.

Remove the old snap

Once your CMS is ready, 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.

1.8-alpha6 is not upgradable from older alphas, so if you previously installed 0.3.3a, 0.4a or 0.5a and haven't removed it, then

snap remove xibo-player-test

Install the Xibo Player

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 --channel=beta

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

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           1.8-alpha6      3     beta      xibosignage   -

Run the Player

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 --host https://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.

Feedback

Please let us know of any rendering issues you encounter in the comments below. Depending on the response 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

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

Features and Issues resolved in this release:

• Performance and stability improvements with XMR/Push messaging
• Fix an issue where the timezone wasn't being pushed to the CMS correctly
• Fix an issue with using CMS time where the CMS is SSL protected
• Updated core libraries with latest versions

Download Xibo for Android v2 R201.

Download Xibo for Android v2 R201 for DSDevices J18 and J19.

Upgrading from an earlier release

We are providing licence upgrades to this release, free of charge, for any licences purchased since 12 December 2018. Check your eligibility by looking at the number of upgrades your licence pool has been assigned in the Xibo customer portal.

Upgrades for licences purchased prior to this date are available for £4 GBP, per licence per major version.

If you have a subscription licence, this upgrade is included within your subscription.

Instructions for upgrading from an earlier release can be found in the Administration Manual.

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

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

This new version has the following changes over 1.8-alpha6:

• We have added a configuration utility accessible by starting xibo-player.options.
• The configuration utility automatically starts if the player has not been configured before.
• XMR (Push Messaging) has been included in this release.

We will continue to address the other feedback and issues found. You can see a list of known issues and other things we're working on here. We know there are problems with memory leaks, and this release is not intended to fix that.

Prepare your CMS

If you have a 1.8.12 CMS, then you can connect the Player directly to that as it already has support for Linux Players. You may need to create a Display Settings Profile for the Linux Player ahead of connecting your first Linux Player. Not all of the settings in the Display Settings Profile will work at present, but we've included them now in readiness for them being implemented into the Player.

If you have an earlier 1.8 CMS, then please see the post for the 0.3.3-alpha release for instructions on configuring your CMS to support the new Player.

Upgrading from an older release

Once your CMS is ready, 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.

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           1.8-alpha7      4     beta      xibosignage   -

Upgrading from 1.8-alpha6

To upgrade from the 1.8-alpha6 release,

snap refresh xibo-player --channel=beta

Remove the old snap

1.8-alpha6 is not upgradable from older alphas, so if you previously installed 0.3.3a, 0.4a or 0.5a and haven't removed it, then

snap remove xibo-player-test

After removing the older release, continue to install the Xibo Player.

Install the Xibo Player

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 --channel=beta

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

Run the Player

To run the Player select Xibo Linux Player from the desktop/app drawer or open a terminal and run

xibo-player

If running for the first time, an options form will open asking for your CMS details. To get back to this options form in the future run xibo-player.options.

The CMS Address and Key are the ones you would normally use to register Players with the CMS. Please choose an appropriate local library for the Player to store its files. On the advanced tab a unique Display ID has been generated for you.

The Player will register with the CMS. Press Exit to quit and then launch the Player again.

Now in the CMS, authorise the display as normal. You can set a default layout for the Player to show, or make any other Scheduling/Layout changes as normal.

Feedback

Please let us know of any rendering issues you encounter in the comments below. Depending on the response 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

We are pleased to announce our 13th 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 25 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/2.0 series compatible Player with this release.

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.

• 1785: Fault Page available in Page Security for Users who cannot use it.
• 1782: Custom-Made Dayparts set to show once causing Event Playback issue
• 1744: Calendar Widget does not display "No Data returned from Source message"
• 1743: Time Disconnected Stats are inaccurate
• 1742: Module - valid extensions need better validation
• 1741: CMS is not correctly adjusting the schedule for Players in different time zones.
• 1740: MAX_LICENSED_DISPLAYS setting not being obeyed
• 1736: Dataset $dateFormat doesn't work on columns which themselves are formulas
• 1735: Agenda View not showing relationship between layouts and campains/groups
• 1734: Day view in Schedule is inaccurate.
• 1729: Display Profile Copy is broken
• 1728: "overrideConfig does not have a default value" error when trying to connect Players to CMS
• 1727: Player Software uploads dont work due to generic file valid extensions
• 1725: Total Duration in Proof of Play is not displaying number of days.
• 1724: Media Dashboard broken in 1.8.12
• 1784: The first time you connect an authorised Player the wrong settings are returned
• 1778: Add a log message if a display is unauthorised by Regular Maintenance
• 1763: Translations in javascript are not escaped thanks to @chalda-pnuzig
• 1761: Missing translations for some javascript components thanks to @chalda-pnuzig
• 1760: Warning: "continue" targeting switch is equivalent to "break" thanks to @chalda-pnuzig
• 1759: count(): Parameter must be an array or an object that implements Countable thanks to @chalda-pnuzig
• 1748: Editing a Display which belongs to a large dynamic display group takes a long time
• 1732: User Delete - Unexpected Error related to campaign ownership
• 1745: Change message to say Authorised instead of Licensed
• 1726: Flip Clock Countdown timer shows all zeroes when scheduled

Xibo’s new Toolbar in 2.0.0 brings the added functionality of being able to specify dates and times of assigned Widgets on a Layout.

Defining start and end times of a Widget means that the assigned content will only be displayed between the specified time frame, when scheduled. So you can set up media content to play at a future date as well as define end dates!

Click on Expiry Dates from the Toolbar and click on the Widget you wish to assign…

...or drag and drop, whatever you find easiest.

Specify Start and End dates and times…

Once assigned simply click on the clock icon to make any required edits to dates and times.

This feature gives users ultimate flexibility and control over what content should be displayed and when within a schedule!

Take a look at our Tools page of the User Manual to see all available toolbar actions in 2.0.0.

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

This new version has the following changes over 1.8-alpha8:

• We have resolved memory leaks and instabilities showing Video Widgets
• Full screen and windowless mode have been added
• The Player window can no longer be resized manually using the mouse

We will continue to address the other feedback and issues found. You can see a list of known issues and other things we're working on here. We are aware of an issue with high RAM usage effecting some devices - if you are effected, please let us know.

Prepare your CMS

If you have a 1.8.12 or later CMS, then you can connect the Player directly to that as it already has support for Linux Players. You may need to create a Display Settings Profile for the Linux Player ahead of connecting your first Linux Player. Not all of the settings in the Display Settings Profile will work at present, but we've included them now in readiness for them being implemented into the Player.

If you have an earlier 1.8 CMS, then please see the post for the 0.3.3-alpha release for instructions on configuring your CMS to support the new Player.

Upgrading from an older release

Once your CMS is ready, 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.

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           1.8-alpha7      8     beta      xibosignage   -

Upgrading from 1.8-alpha6 or later

To upgrade from the 1.8-alpha6 or later release,

snap refresh xibo-player --channel=beta

Upgrading from earlier that 1.8-alpha6

1.8-alpha6 is not upgradable from older alphas, so if you previously installed 0.3.3a, 0.4a or 0.5a and haven't removed it, then

snap remove xibo-player-test

After removing the older release, continue to install the Xibo Player.

Install the Xibo Player

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 --channel=beta

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

Run the Player

To run the Player select Xibo Linux Player from the desktop/app drawer or open a terminal and run

xibo-player

If running for the first time, an options form will open asking for your CMS details. To get back to this options form in the future run xibo-player.options.

The CMS Address and Key are the ones you would normally use to register Players with the CMS. Please choose an appropriate local library for the Player to store its files. On the advanced tab a unique Display ID has been generated for you.

The Player will register with the CMS. Press Exit to quit and then launch the Player again.

Now in the CMS, authorise the display as normal. You can set a default layout for the Player to show, or make any other Scheduling/Layout changes as normal.

Feedback

Please let us know of any rendering issues you encounter in the comments below. Depending on the response 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