I had a few instances of Xibo running with 1.8.13 for a while, now we updated all to v2.3.11, and I have one with 3.0.1. for my next project.
We do use a lot of SQL-Syntax and datasets. It seems to me that something has changed in the meanwhile and I don’t know to solve it.
If I use this
Room LIKE ‘Room01’ AND NOW() > KPZstart AND NOW() < KPZend
it seems that now the ‘AND’ doesn’t work anymore. I only get the room to be filtered.
If I use
NOW() > KPZstart AND NOW() < KPZend
only the start date is filtered, the dataset entry is still shown when the end date is reached
Are there new ways to get these dataset filters to work?
@natasha
Is there a possibility to get some info on this from a Xibo member? Do you need more information, should I export you my layout and the dataset to check?
Any help is very welcome.
There are only a few days for me to decide if I setup my new project in v3 or v2.
Hi @natasha,
thank you for the support. Is there a chance to get informations when the bug will be corrected?
This is an elementary function of my new project that I need to bring from layout and testing to a release soon.
I need to setup another version with latest CMS v2 if I cannot use it in v3.
This would be a lot of work now and after a working release of v3 to convert all the users and players and scenes back and forth.
An answer from Xibo members would help me a lot.
I know this is Open Source, but maybe you can support me on this special issue that I haven’t expected to be there in v3.
Great, so on docker you can pull release30 - it will say 3.0.2 but will contain all currently resolved 3.0.3 bugs:
- run docker-compose down if the containers are up
- Open the docker-compose.yml (or the cms_custom_ports.yml if you’re using that file to up your containers)
- Find the line under cms-web that specifies the docker image that is used to pull cms files, it should look like this : image: xibosignage/xibo-cms:release-3.0.1
- Change the image to release30 ie that line should be changed to:
image: xibosignage/xibo-cms:release30
and save the file
- run docker-compose pull
(wait for it to finish) then:
- run docker-compose up -d
Make sure you save a file after making a change and wait for the pull to finish.