Windows client's playing old layouts

Get Help
1

Hi. Something strange happened to me.

I’m using CMS and client version 1.7.6. There’s 3 old layouts created on last March. I haven’t used my Xibo CMS for about 2 months until yesterday when I created a new layout and scheduled it to play for 3 days (Saturday night to Tuesday) on 2 different players (windows and android), but in fact it’s only running on Windows because Android client’s license expired.

Well, the issue is that the client is playing the old layouts and the new one too, one at a time. But I want to play only the new one. I also deleted cache on c:\xibo library, but nothing happened: the client was still downloading old contents. I re-checked the schedule out, there was only the new layout set from Saturday to Wednesday, so there were no other layouts set… that’s the strange thing
So, I drastically had to delete old layouts from CMS library and there it worked!

Ah… I forgot to tell you that on April (in the middle of March and May testing) I tested Spring hosting, so I had to set the Spring URL and code on the client, and when the 14th day trial expired I stopped testing Xibo from everywhere for about a month. So last Saturday I resumed my testings and I set back the URL to my CMS. I once thought that it was a cache problem till I deleted the cache as I mentioned before.

So, is this an issue or there’s something bad configured in the CMS? or there’s a restriction to change to different CMS’ on the same client?
I had to delete the old layout to solve the issue, but I think this way can’t be the solution.

I appreciate the potential wise answer. Thank you!

Diego.

PS: by the way, the new layout plays a flash content (one file swf) that contains 5 slides, but it does not play the first one. In the preview, it plays fine, but in the client the first slide is missing. What could be happening? (Windows 8 client).

2

That’s a bit odd, just so you know - no this should not have happened and no there are no restrictions like that.

Not sure really, perhaps if we’d have logs/status screen/CMS access we’d find something, but since you already solved the issue by other means, that’s not possible anymore - unless you will find yourself in a similar situation again.

I know we had some issues like that in earlier versions, you might want to check 1.7.7 CMS/client to see if this issue persists.

3

Yes, it was the 1st time this odd thing happened to me.
As I mentioned before, I tested the Spring CMS with the same client changing URL and code and then I switched it back to my testing CMS… but I deleted all those content files in the client. Perhaps the client app ‘got confused’… I don’t know.
Next time I’ll give you my credentials to see what happened, i didn’t realize it.
Thank you!

PS: by the way, the CMS is not responsive… I tested in my cell phone and I could not update contents nor nothing because of the modals that I couldn’t reach the save nor cancel buttons. Are you planning to make the CMS responsive for next releases? eg: if a store client wants to update layout on the fly with his cell phone, he can’t.

4

You’re right, as it is the CMS is not designed with mobile users in mind, it might change in the future, but it’s not our priority at the moment.