Xibo CMS 3.2.1 - Released

We are pleased to announce the first patch to the 3.2 version of Xibo. The codename for this version is “Perrine”.

This is a companion discussion topic for the original entry at https://xibosignage.com/blog/3-2-1-released

Unfortunately an issue has been found with the 3.2.1 release related to folders.

We are rolling a patch out for Cloud-hosted customers currently, and an updated release will be available for self-hosted users later today. Further information is available in the Github issue:

I noticed that the Media Resolution only shows for images and not videos. Should it work with videos also?

Thank you,

Hi John,

We get the resolution of a video from its cover image (i.e. the thumbnail), so if a video does not have a thumbnail we can’t currently show the resolution.


Update 2022-10-11 20:00 UTC

Unfortunately we found a release day issue with the folder tree which prevented users from navigating around folders. Full details can be found here:

This issue was serious enough to retag the release, generate new source downloads, and Docker images.

If you upgraded to 3.2.1 before this time, please re-apply the release. To do so with Docker simply issue docker-compose pull && docker-compose up -d on your install. To do so with source files please redownload and follow the upgrade instructions again.

Customers with Cloud hosted CMS instances have been patched already.

Apologies for the inconvenience caused by this issue, we will make sure this area of the CMS has automated testing.

Thanks folders work perfectly now. :slight_smile:

Is there a way to have it automatically create a thumbnail if the user doesn’t create one, also is there a way to create one after the video has already been uploaded?

Thank you,


We noticed user creation with SAML-integration is broken after upgrading.
The error we receive is: Integrity constraint violation: 1048 Column ‘homeFolderId’ cannot be null.


Thank you for reporting this issue, a bug report has been created, apologies the inconvenience:

There is a patch suggestion in the issue report which might be useful if you run Xibo from source files.