We have a few Raspberry Pi 3’s running the older version of Screenly OSE working nicely but we had to buy a Raspberry Pi 4 due to shortages, there was only the development version I think at the time, for the RPi4 so I don’t have an image of the older Screenly for it.
When trying to use Anthias on the RPi 4 it’s a bit of a struggle, the only way I can get it to successfully install is by using the OS install from the imager and then run the .sh install, which is fine, but once it does run it doesn’t display our internal notification pages anymore.
Anthias just displays a white screen, the pages are built using WordPress, I didn’t build them so I can’t speak to what’s going on there but there were basically built to size and display correctly with Screenly OSE, and they do so well still.
Most other web pages do display correctly, so maybe this is something to do with how WordPress dishes things out?
There is also another page we have running on CivicPlus, that tries to load for a second but goes to white screen as well, I have no idea what they are using on the back end.
I have test just running chromium as an auto launch on the latest Raspi OS and it works well to display the pages but the framing is all wrong as it was tweaked to work on Screenly OSE and whatever it uses to display those pages.
I’d rather use Anthias but if I can’t get it to work is there a way to fall back to whatever webviewer the older Screenly releases were using?
Manually install it perhaps?
I can see the Qt5 webviewer releases in there but have no idea how to utilize them in anyway.
If it’s possible to install just the older webviewer components on an install of Raspi Lite or something, without the webserver, that would be cool, we just need the ability to display the page and not the GUI necessarily.