Manual/Custom Install
Docs
Introduction
CMS Installation
CMS Configuration
CMS Upgrades
Android Installation
Windows Installation
webOS Installation
Tizen Installation
Linux Installation
Player Upgrades
Player Licensing
White Labelling
My Account
Resolving Common Issues
Troubleshooting / FAQ
Android FAQ's
webOS FAQ's
- Xibo for Android
- DSDevices DSCS9X/95 Set-up Guide
- Install a White Label or a different Player version on DSDevices
- CEC Screen Power on/off with DSDevices
- Hardware Recommendations
- Philips Signage SoC Monitors
- Sony Bravia SoC
- Hisense Commercial Displays SoC
- Managing Storage on the Android Device
- Player Settings
- Players without an Internet Connection
- Remote Administration with SS Helper
- Restart Rooted Device with a Shell Command
- Running Xibo for Android
- Resolving Common Issues
- Error shown when I try to licence my Player?
- Player not updating from the CMS?
- I can see my Licence entry but the Player appears unlicensed?
- Error message - Player is missing dependencies
- My scheduled Layouts are not working?
- Layout won't play? Splash screen plays?
- Watchdog error message
- Troubleshooting for Administrators
- Audit Trail
- Log Information
- Player Logs
- Getting the Player Status
- Request Player Status via CMS - Logged in Players only
- Request Player Status directly from a Device
- Can I use the Xibo name / logo?
- Can I run a Xibo Player on Raspberry Pi?
- How can I increase the upload file size limit?
- How do Players communicate with the CMS?
- How many displays can Xibo support?
- How do I reset the Xibo_admin account password?
- Power On/Off for Players
- Testing with Xibo
- Why do I need a Default Layout?
- Xibo for Android FAQ's
- Autoplaying Embedded Youtube Videos
- Closing to Home screen
- Displaying Images
- Embedded TV
- External SD card not listed when running Banana-Pi
- Helper Command to change Time zone
- HTML5 Video
- Memory Notifications
- Menu not accessible
- SSL Support
- Using Portrait Displays
- Video wont play properly
Upgrade Manual/Custom Install
Upgrading a manual/custom installation happens in 3 stages:
- Requirements (upgrading to v1.8.x)
- Upgrade the CMS files (Upgrading the CMS files is a manual process that should be completed by your web server administrator).
- Upgrade the database (In 2.x, 3.x and 4.x, upgrading the CMS can be done by your web server administrator from the terminal. In versions earlier than v2.0.0 upgrading is completed in a wizard and can be done by the CMS administrator).
Please check the release notes for the version you want to upgrade to before starting the upgrade.
You should always take a backup before upgrading your CMS Installation.
Upgrading to v4.0.0 and later
- Open a terminal
-
cdinto your installation folder - run
vendor/bin/phinx migrate -c phinx.php
Xibo CMS v4 requires public/private and encryption keys to be saved in the library folder. Instructions for doing this can be found here.
After a successful upgrade a background task called “Widget Compatability” runs in XTR and converts all widgets from v3 to v4. Xibo v4 must have XTR correctly configured and operational to function correctly.
Upgrading to v3.0.0 and later
- Open a terminal
-
cdinto your installation folder - run
vendor/bin/phinx migrate -c phinx.php
Upgrading to v2.0.0 and later
- Open a terminal
-
cdinto your installation folder - run
vendor/bin/phinx migrate -c phinx.php
Upgrading to a version earlier than v2.0.0
- Log in as an administrator.
- The upgrade wizard will open and show the list of upgrade steps.
- Press start to run through them.
Upgrading to v1.8.x
- Ensure your environment meets the requirements for installation. If it does not then correct that before continuing.
- Backup settings.php from your installation (found in
web/settings.php) - Manually take a backup of your database
- Replace your existing installation with the new version from the tar.gz or zip file. Do not copy over the top.
- Replace your backup settings.php file in your Xibo installation directory
- Browse to http://your.server/path as normal
Verify All
If upgrading to a version earlier than 4.0.0, once the upgrade has completed, login to your CMS and click the Verify All button from the Modules page under the Administration section of the CMS main menu. This is to ensure any updates/enhancements are applied to any module files which may have changed between versions.
