I upgraded the CMS(3.1.2) and Clients(3 r303.0) on Monday but the Twitter module since then is not showing any images.
We use Xibo in a docker container on Windows with the clients also on Windows machines
It does bring down the text of the tweet but just not the images in the clients or the Design window.
We are using Template 10 with a few overrides but it worked great before the update.
I have Cleared the Cache on the clients also
Is this a known issue ?
Or is there a fix for this issue?
Thanks
So when testing i have taken down the docker container and run a backup of versions 2.2.2 on the same server and this is working correctly bringing down the Twitter images and Tweets… so i think it might have been an issue with the newer version of the CMS
Is anyone else having this issue ?
Is this a known issue in this version?
We have tested this and don’t seem to have the same issue as you are reporting? Could you try the Verify All button from the Modules page and then do a cache clear in your browser privacy settings to see if that resolves it for you?
If that is not the case then please do come back to us.
Hi,
Thanks for getting in touch about the issue.
I have Just “Verify All” on the modules page and also cleared my cache in the browser but still getting the same issue.
This is in the Design View layout
We are using CMS 3.1.2 in a docker container on Windows 10
Players are 3 r303.0
I have reverted back to 2.2.2 CMS and this then works fine after exporting the layout from version 3.1.2 back into 2.2.2
I am not sure what else to suggest as it does not seem to be an issue that I can recreate in our cloud. I have checked with a colleague in the support team who can also confirm all appears to be working as expected.
When you cleared your cache did you do clear "cached images and files’ in the clear browsing data settings opposed to a Shift + F5?
We are using the local server instead of the cloud instance.
I cleared the Cached images and files from the Edge Browser by going into the settings, I didn’t use the shift+ F5
I have also tried the Server on another network that is not managed by our Local authority to rule out any issue with filtering but as it is working for the 2.2.2 on the same server using the same IP it can’t be this…
Is there any way I can send any logs to see if there is anything that might stand out so we can update to the newer version??
So logging onto the Admin Dashboard to view the affected layout, I have used both Edge and Chrome but both showing the same issue and also showing the same on the actual displays also.
Yeah, i can grab some of the logs - how do i enable logging for the system? and also do you have a contact to send them over to yourselves
So… i have tried to enable debugging but the page would not load was saying “that there has been an error contact support”
This instance has been updated several times from 1.8 i think…
So i have just taken the docker container down and done a fresh install for 3.1.2 in its own folder
copied in the Config.env file into the folder for the fresh install
started docker with this instance
imported the same layout and enabled Twitter module and put in the API details
Then tried that but only got a black screen
I’ve had a look at your log files and located some SQLSTATE errors that suggest an empty value is trying to be written to the fileSize entry in your database, which is not allowed. To troubleshoot this further please can you run these commands on the machine running your CMS.
PS C:\Xibo-Docker-3.1.3\xibo-docker-3.1.3> docker-compose exec cms-web bash
bash-5.1# curl -v “http://pbs.twimg.com/media/FVg2K6aX0AABqsR.jpg” --output /tmp/test.jpg
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0* Trying 199.232.172.159:80…
Connected to pbs.twimg.com (199.232.172.159) port 80 (#0)
GET /media/FVg2K6aX0AABqsR.jpg HTTP/1.1
Host: pbs.twimg.com
User-Agent: curl/7.80.0
Accept: /
Connection #0 to host pbs.twimg.com left intact
bash-5.1# ls -al /tmp/test/jpg
ls: /tmp/test/jpg: No such file or directory
bash-5.1# ls -al /tmp/test.jpg
-rw-r–r-- 1 root root 258540 Jul 14 12:42 /tmp/test.jpg
Thank you for providing the results to that test. Unfortunately we can’t explain why this issue is occurring on your 3.1.2 CMS installation. This issue also has not been replicated on our test setups or reported by another user. The fact that the module is working correctly when you use your 2.2.2 CMS is also unusual. I’m sorry that I do not have a more definitive answer to your issue.