Hello, it would be great if you could update xibo directly from the CMS like eg a plugin from Wordpress.
To the makers of xibo…is not possible? You save a lot of time here.
Thank you very much for an info
Could you provide more information about which elements of Xibo you are referring to? Did you mean the CMS or the Players?
Many Thanks.
I mean the CMS. I am now on 1.8.12 and if there is an update zb on 2.XX.XX that you just in the dashboard on a button and then the CMS accordingly makes an update to the latest version of CMS.
1 Like
I have always expected updates from xibo developers from 2016 till today
This way prevents possible data loss.
CMS User provides continuous and fast return.
CMS User provides very fast turnaround as a result of tests and trial versions for interactive contents.
Some design or schemes problems to be experienced are prevented.
Many plugins can be created by users or developers.
Custom or automatic design creation wizard can be produced.
Simple plug-ins can be created, such as the automatic screen split plug-in.
But for the last 2 years. There is a docker and sometimes it is a complete torment. It sometimes takes hours to figure out where we made a mistake. No interactive videos for installation and upgrade. Some hosting servers prevent us from using docker. We have to delete all the information and make a new installation.
Docker make me angry. Manual upgrade some times gived error. All templates copy from hosting on the desktop. Than start new install. Than create new template. Do it everything again. Because 1.8 template desing is not usiable 2.0 or up. All pictures shift somewhere or CMS library can not find picture, RSS ticker is not working, you have to create and control again.
I like wordpress updating system. Wordpress is open source. If we want we can copy this updating knowledge. Everything easy, create one copy on the desktop. Do it everything. If something wrong dont worry came back before update manually. Why we want to different?
I may have made mistakes in some words because I wrote fast. If there is any confusion, you can write me please.
In my opinion the concept of having the CMS check with some URL, download an update package and then execute that on the underlying server is filled with potential security problems which terrify me. We would be going in the wrong direction if we put something like this into the software.
If you do not like Docker - don’t use it - we aren’t forcing you to. We supply release archives with every stable release which you can use for a installation directly on your chosen webserver.
Upgrading with Docker is super easy though - which is why we recommend it.
1.8 Layouts are fully compatible with v2 onward - if you have some issues please provide us with examples so that we can track down the problem and improve the upgrade.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.