1.8.0-rc2 CMS problem

A fresh 1.8.0-rc2 install on linux server…media page return following error (chrome):

Getting DataTables warning: table id=libraryItems - Ajax error. For more information about this error, please see http://datatables.net/tn/74

Library folder has full permissions, version 1.7.x was ok…help!


Did you use Docker? Or self-install?

If you self-installed, do you have “web” in the URL you use to access the CMS?

I use self-install and I’ve “web” url to access the CMS

Please go back and re-read the install guide. You can’t install a 1.8.0 CMS in the same way as you used to for 1.7 series. They are very different in their requirements.

“web” should not appear in the URL you use to access the CMS. The contents of the web folder should be the only part of the CMS code that is web served. The files above should not be in the web server root.

To achieve this, for the vhost for the website you’re using, change the web root to the web directory, or use an alias.

Alternatively, use a Docker container - as this is all then handled for you.

Thanks Alex I try!

Sorry where I find the install guide?

It’s in the manual:


and for Docker

Thanks Alex I’ve done now it’s ok!

Now I did the upgrade on a test server, but when it comes out the final 1.8 version I’ll be able to upgrade without losing the sql data?

Good question - I’m interested as well. I installed Docker for 1.8 rc1, and am wondering if the upgrade to 1.8 rc2 (and production release) is similar to 1.7, or if there is another step I need to take so I can keep my existing information without messing up the system.

I really need to read more before I post, sorry. - http://xibo.org.uk/manual-tempel/en/upgrade.html from another post has the steps for 1.8 rc1 to rc2, and for Thomas_Poli, post at 1.8.0-rc2 Released says you can upgrade from rc to production, so this should all be good.

ok it’s possible but how? When I did the upgrade the installation procedure asked me to make new DB or choose an existing but empty … why?

I’m not sure I can help on that one; it sounds like you did the Manual CMS installation. I used Docker and did a “./launcher upgrade” with my existing launcher.env and it all just happened like magic. Everything from 1.8rc1 works fine still in 1.8rc2 that I can see so far, and my 1.8rc1 client still appears to run fine (so I can upgrade the client in the next day or so).

If you’re trying to do it manually, http://xibo.org.uk/manual-tempel/en/upgrade.html has all the steps and says the upgrade wizard should startup near the end of your steps.

We will be providing some specific notes for anyone wanting to go from 1.7 non-docker to 1.8 docker (essentially importing your old DB when Docker starts).

For any 1.7 to 1.8 (non-docker) the upgrade notes have the steps covered - for any 1.8.x to 1.8.0-rc2 a launcher upgrade is all that is required when using Docker. Again covered in the upgrade notes.

If Thomas is able to provide the exact environment he is going from and to and the steps he has done, then perhaps we can isolate where the missing link is

I upgrade from xibo 1.7.6 to 1.8.0-rc2 and I use self install but I’m in a test server (shared hosting) no problem.

In my production server I’ve last 1.7.9 version and perhaps I can use docker…

Hi Thomas,

1.7.6 to 1.8.0-rc2 self install is not supported - please read the release notes as suggested before: http://xibo.org.uk/manual-tempel/en/release_notes_1.8.0-rc2.html#upgrading

Specifically you should upgrade to 1.7.8 first and then on-wards to 1.8.0-rc2

Ok in my production server I’ve 1.7.9 installed…so even with manual installation I can do upgrade and maintain the db data? Is correct?

Yes that is correct - although you should always take a backup just in case! :slight_smile:

A post was split to a new topic: Xibo 1.8.1 Installation issues