CMS 3.0.0 theme->rootUri() does not honor CMS_ALIAS properly as 2.3 does

CMS Version

  • 3.0.0

Installation Method

Docker

Operating System

CentOS

Issue

  • I am using CMS_ALIAS on 2.3

  • I just upgrade 3.0 from 2.3

    • theme-rootUri() does not conform 2.3 behavior (honor CMS_ALIAS) properly.
      For example, for value CMS_ALIAS=/xibo_test
  • In 2.3

...
<script src="/xibo_test/dist/vendor.bundle.min.js?v=3.0.0&amp;rev=7deaa0cccbb13f489d894bb699fbac8ffa1d11ab"></script>
...
<script src="/xibo_testdist/vendor.bundle.min.js?v=3.0.0&amp;rev=7deaa0cccbb13f489d894bb699fbac8ffa1d11ab"></script>
  • I cannot change CMS_ALIAS=/xibo_test to /xibo_test/ since it breaks apache config in your entrypoint.sh
  • Is it possible to have a quick solution? Otherwise, I have no choices but rolling it back to 2.3

Reference

  • Screen capture on bad theme->rootUri() on 3.0

image

  • my config.env
## CMS Configuration

## Please make a copy of this file as config.env, and then
## edit it to suit your environment

## MYSQL
# You're running with your own remote MySQL server
# Enter the connection details here that Xibo should use
# You'll need to ensure that the database already exists (and is empty)
# and the user specified has all privileges on that database
MYSQL_HOST=xxxx
MYSQL_PORT=3306
MYSQL_DATABASE=xxxx
MYSQL_USER=xxxx
MYSQL_PASSWORD=xxxxx

## SMTP Server Configuration
## The CMS needs to be able to send email to you
## Please enter credentials for a suitable SMTP server
## Defaults will work for GMail - replacing your GMail username
## and password as appropriate. You will also need to enable access
## for less secure applications on your GMail account for this to
## work. See https://support.google.com/accounts/answer/6010255

## SMTP Server Hostname
CMS_SMTP_SERVER=xxxx
## SMTP Username
CMS_SMTP_USERNAME=xxxx
## SMTP Password
CMS_SMTP_PASSWORD=xxxxx
## Use a TLS Connection YES/NO
CMS_SMTP_USE_TLS=YES
## Use a STARTTLS Connection YES/NO
CMS_SMTP_USE_STARTTLS=YES
## Rewrite domain (the domain your email will appear to come from)
CMS_SMTP_REWRITE_DOMAIN=xxxx
## Hostname that we should identify ourself to the remote server as
CMS_SMTP_HOSTNAME=xxxxx
## Can the From line be overridden in the outbound email
## NB GMail will rewrite the From address anyway so it's not important
## for GMail - YES/NO
CMS_SMTP_FROM_LINE_OVERRIDE=YES

## It is sometimes necessary to configure the webserver running inside
## the container to know the DNS name by which you will normally
## access the CMS. For most installations this is unnecessary and can
## be left as default, however, if you know this, it won't hurt to
## set it
CMS_SERVER_NAME=xxxxx

CMS_ALIAS=/xibo_test

## Xibo can email various reports and charts. To do so a charting service
## is required. Xibo uses QuickChart.io, which has been provided as a container
## in the Docker Compose files.
## If needed, you can change the URL of the Quick Chart service to one you provide
## externally to Xibo's Docker Compose environment
# CMS_QUICK_CHART_URL=http://cms-quickchart:3400

CMS_USE_MEMCACHED=true
MEMCACHED_HOST=cms-memcached
# MEMCACHED_PORT=11211

Edited

  • I just tried override the entrypoint.sh such that i have CMS_ALIAS=/xibo_test/ while keeping the apache config the same. It still does not work
  • Include the corresponding implementation for 2.3 & 3.0

Thank you for reporting this issue - we’ve fixed the problem and made an image called release30 available.

You can update your docker-compose.yml file and replace release-3.0.0 with release30, then do a docker-compose pull and then a docker-compose up -d

Great. It works perfectly. Thanks for the fix

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.

The Xibo Community site uses cookies. What are cookies?