I tried to upgade XIBO from 4.1.2 to 4.2 without success. So I decided to start form scratch. I created a database and user and copy XIBO to my shared hosting. The installation went well, but at the login page I see the following message.
The CMS is temporarily off-line as an upgrade is in progress. Please check with your system administrator for updates or refresh your page in a few minutes.
Is this because of the previous failed upgrade? And how can I solve this?
I just installed XIBO 4.2 on a new shared hosting account and I have there the same problem.
The CMS is temporarily off-line as an upgrade is in progress. Please check with your system administrator for updates or refresh your page in a few minutes.
In the first installation screen every check has a check mark. Second screen no failures using an existing database. Last screen the message above.
I did the same installation with version 4.1.2. without the issue above.
You need to run the database migrations which will require you to have a console on the server, which may not be possible on shared hosting. The method we support for the install is with Docker as set out on the website and the supported environments page of the documentation. If you opt to use other methods then we can’t always help you to resolve problems you encounter unfortunately
Hi Alex, I did a database migration via the terminal with following command
php vendor/bin/phinx migrate -c phinx.php
but that went wrong. So I did an new installation with version 4.2 with a new database, but that went wrong too. A new installation with version 4.1.2 went well.
You’d need to be more specific about what went wrong - logs etc. It would be best to open a new topic about your specific issues as they’re not general issues with the v4.2.0 release. I’ll move your posts over now, and perhaps you can provide some more details about how you have things setup and what the problems you have are when you run migrate please.
I’d check that your shared hosting is using MySQL and not MariaDB. MariaDB is known not to work with 4.2.0 - see Xibo CMS v4.2.0 Released - #5 by pitoco02
I assume you are still using MariaDB, experienced the same issued with MariaDB, Using mysql instead solved the issue of “The CMS is temporarily off-line”
Yes, I’m using MariaDB. So that is the problem, but I thought that MariaDB is better than MySQL. So is this a bug in version 4.2 or by design?
It’s not a bug. You’re using the wrong database engine for the CMS to run on. If you tried to run it on MSSQL or Oracle it wouldn’t work either, and that also wouldn’t be a bug.
If it is not a bug, why it is not possible to use MariaDB in 4.2.0, but possible in 4.1.2. So it’s by design then.
It is possible to use MariaDB, but its not supported by default by Xibo.
It means that all changes that you need, you must do by your own risk.
Jus check whats Alex sent to you:
Just change the query quoted in this file, run the PHINX again, and you will be able to use the CMS with no problems using MariaDB as far as i tested in my own server.
MariaDB is a fork of MySQL. They actively support a different syntax to MySQL. We only develop and test with MySQL and not MariaDB. We state in the requirements that you need to use MySQL. If you use MariaDB it may work, but where MariaDB uses different syntax to Xibo it won’t - and Xibo will break. It’s not a bug in Xibo - it’s that you’re using the wrong database engine.
Greeting Alex…happy new year sir. its been awhile. I have test his problem just now and got the same error too. i used docker-compose.yml with mysql 5.7…i didnt change anything but i got the same erro
i then started a new one with mysql 8.0 as preset in the original docker-compose.yml and getting blank page…no error… at time database user related issue… then i go into the env. file to add db user and db name there there i get unable to connect error…i am trying to figure out what the issue is regarding v4.2.0. i know the env. file will have just database password line
Fatal Error - sorry this shouldn’t happen.
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for cms-db failed: Name or service not known
i used the template that came with the docker zip file for v4.2.0
regarding v3.3.12, i have added my theme for the logo but it doesn’t take effect. it works only when i use docker-compose.yml… not when i chose to use remote mysql to start xibo docker. i have the files in the right folder with file permission 777 and still… in the cms settings, my theme does not come up on the list
has anyone found a solution to this? when i migrate i get an error
sortedbuy@snowdon-lon xibo-cms]$ php vendor/bin/phinx migrate -c phinx.php
Phinx by CakePHP - https://phinx.org.
using config file phinx.php
using config parser php
using migration paths
- /home/sortedbuy/xibo-cms/db/migrations
warning no environment specified, defaulting to: production
using adapter mysql
using database sortedbuy_xibocms
ordering by creation time
== 20250121120000 UpsertCoreEmergencyAlertInModule: migrating
PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'AS newRow
ON DUPLICATE KEY UPDATE
`enabled` = new...' at line 2 in /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Db/Adapter/PdoAdapter.php:192
Stack trace:
#0 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Db/Adapter/PdoAdapter.php(192): PDO->exec()
#1 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Db/Adapter/AdapterWrapper.php(157): Phinx\Db\Adapter\PdoAdapter->execute()
#2 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Migration/AbstractMigration.php(199): Phinx\Db\Adapter\AdapterWrapper->execute()
#3 /home/sortedbuy/xibo-cms/db/migrations/20250121120000_upsert_core_emergency_alert_in_module.php(34): Phinx\Migration\AbstractMigration->execute()
#4 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Migration/Manager/Environment.php(108): UpsertCoreEmergencyAlertInModule->change()
#5 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Migration/Manager.php(388): Phinx\Migration\Manager\Environment->executeMigration()
#6 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Migration/Manager.php(359): Phinx\Migration\Manager->executeMigration()
#7 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Console/Command/Migrate.php(122): Phinx\Migration\Manager->migrate()
#8 /home/sortedbuy/xibo-cms/vendor/symfony/console/Command/Command.php(298): Phinx\Console\Command\Migrate->execute()
#9 /home/sortedbuy/xibo-cms/vendor/symfony/console/Application.php(1040): Symfony\Component\Console\Command\Command->run()
#10 /home/sortedbuy/xibo-cms/vendor/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand()
#11 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/src/Phinx/Console/PhinxApplication.php(70): Symfony\Component\Console\Application->doRun()
#12 /home/sortedbuy/xibo-cms/vendor/symfony/console/Application.php(171): Phinx\Console\PhinxApplication->doRun()
#13 /home/sortedbuy/xibo-cms/vendor/robmorgan/phinx/bin/phinx(28): Symfony\Component\Console\Application->run()
#14 /home/sortedbuy/xibo-cms/vendor/bin/phinx(119): include('/home/sortedbuy...')
#15 {main}
@paul_ksi The solution to this is in this same topic… just take a look at the conversation above
Or just wait the next release as alex said in the original topic:
Hello,
I installed Xibo CMS 4.2.0 on my Windows localhost in a custom way without using docker. After completing all the steps, it was supposed to redirect me to the login page. But I get the error in the screenshot I attached and no matter how hard I try, I can’t get past this section. Can you please provide me support? I am using Xampp version 8.2.12. phpMyAdmin is using MariaDB as database server type. It uses 10.4.32-MariaDB - mariadb.org binary distribution and version.
@Gorkem_Aslan The solution to this is in this same topic… just take a look at the conversation above
Or just wait the next release as alex said in the original topic:
Hello @pitoco02 I did the steps you mentioned above as in the first screenshot. But again I got an error like in the 2nd screenshot. Do you think I made a mistake while adding the codes, I am transmitting the code in text form, can you please edit it? When I press the Home key, it sends me to the same page again, can you help me?
<?php
/*
* Copyright (C) 2025 Xibo Signage Ltd
*
* Xibo - Digital Signage - http://www.xibo.org.uk
*
* This file is part of Xibo.
*
* Xibo is free software: you can redistribute it and/or modify
* it under the terms of the GNU Affero General Public License as published by
* the Free Software Foundation, either version 3 of the License, or
* any later version.
*
* Xibo is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Affero General Public License for more details.
*
* You should have received a copy of the GNU Affero General Public License
* along with Xibo. If not, see <http://www.gnu.org/licenses/>.
*/
use Phinx\Migration\AbstractMigration;
/**
* Add a new connector (National Weather Service - NWS) to connectors table
* @phpcs:disable PSR1.Classes.ClassDeclaration.MissingNamespace
*/
class AddNationalWeatherServiceConnectorMigration extends AbstractMigration
{
public function change()
{
$this->table('connectors')
->insert([
'className' => '\\Xibo\\Connector\\NationalWeatherServiceConnector',
'isEnabled' => 0,
'isVisible' => 1
])
->save();
}
$this->execute('
INSERT INTO `module` (`moduleId`, `enabled`, `previewEnabled`, `defaultDuration`, `settings`)
VALUES (\'core-emergency-alert\', \'1\', \'1\', \'60\', NULL) AS newRow
ON DUPLICATE KEY UPDATE
`enabled` = newRow.enabled,
`previewEnabled` = newRow.previewEnabled,
`defaultDuration` = newRow.defaultDuration,
`settings` = newRow.settings;
');
public function change(): void
{
// Insert or update core-emergency-alert into the module table
$this->execute('
INSERT INTO `module` (`moduleId`, `enabled`, `previewEnabled`, `defaultDuration`, `settings`)
VALUES (\'core-emergency-alert\', \'1\', \'1\', \'60\', NULL)
ON DUPLICATE KEY UPDATE
`enabled` = VALUES(`enabled`),
`previewEnabled` = VALUES(`previewEnabled`),
`defaultDuration` = VALUES(`defaultDuration`),
`settings` = VALUES(`settings`);
');
}
}
@Gorkem_Aslan
It’s not correct.
I recommend that you wait for 4.2.1, which has the correction for this code
@pitoco02 so how can I edit this code and when is 4.2.1 coming out?
No!
In 4.2.1 theres no need to change any code.