Display Fonts Issue

Get Help CMS Installation
1

To be completed by the original poster:

CMS Version

4.4.4

Installation Method

Custom install

Operating System

Debian 12

Issue

Can’t display the Fonts page from the admin page after upgrade from 4.4.3 to 4.4.4

image
image471×703 30.1 KB

2

Same here with 4.4.4, docker-version on debian 13.
But to be honest, i dont know if it worked on the previous 4.4.3 because we never used the fonts page.

3

Font page works here on xibo-docker CMS v4.0.10, v4.4.0 and v4.4.3

4

Hello, after debugging,

i found that this issue is the result of that the next function has been removed in

/lib/Controller/Font.php between the 4.4.3 to 4.4.4

private function getValidExtensions()
{
return [‘otf’, ‘ttf’, ‘eot’, ‘svg’, ‘woff’];
}

When I add this Function i can see the Font page.

5

another solution

Replace line 89 in /lib/Controller/Font.php

‘validExt’ => implode(‘|’, $this->getValidExtensions()

by

‘validExt’ => implode(‘|’, $this->fontFactory->getValidExtensions()

6

Thanks all, this has already been flagged and fixed with the full issue report here:CMS 4.4.4: "Unexpected Error" prevents access to the Fonts page · Issue #3877 · xibosignage/xibo · GitHub

7

Hey, please give us an advise how to solve this problem? The mentioned files are not in my Docker-folder as far as I wan see?

Dan was also not very helpful here (no information, no ETA, no word about an intermediate verison): Please provide updated 4.4.4 Docker image due to problem with Font configuration page · Issue #3882 · xibosignage/xibo · GitHub

How to solve this in Linux/Docker?
Is there an intermediaate release (eg 4.4.4.1?)?

8

Downgrade to v4.4.3 for time being…

9

The fix will be included in 4.4.5, but I couldn’t find any information about the release date.

10

Hi Gustel,

We recommend switching to release44as we don’t have a 4.4.5 path planned.

Just for future reference, Github is not used for discussion and we tend to close them out quickly. If you require discussion or assistance then posting here in our community is encouraged to engage with fellow members and also the Xibo team :slight_smile:

Thank you for your support.

11

Good morning,

Now I’m a little surprised, especially since the issue was added to Milestone 4.4.5 on GitHub, and dan also mentioned on GitHub that 4.4.5 with the fix isn’t available yet?

12

Good morning,

We are going to introduce a v4.5 in the same timeframe as it would take for v4.4.5. I shall look to see about reviewing the milestone tags on the GitHub repo to clarify and avoid further confusion.

Thank you