Hello I have trouble installing xibo 4 cms on my hyper V virtual machine under centos 7 if there is a charitable soul who can help me I am available discord (randadr # 4020) or other
Thank you Dan,
In a week I have learned version 4.0, and I can say thank you for your team, it turn out more easier, easy for everything, and you know what, I can import my template easely, I’m so happy 
My regards,
3 Likes
Signed up for a trial account just to see the new 4.0 version. See we can still add HTML/CSS to the Embedded Widget (no more JS). BTW, the HTML Code box is easier to read too for those little changes. The most important thing, the HTML/CSS actually is displayed correctly compared to before.
-
When will you have the API documentation updated? We’re working with the APIs and there’s no instruction for the widgets other than how they fall into a playlist.
-
Is there a GitHub page you can point us to for the 3.3v?
Appreciate the help while we wait for the Xibo AP Swagger API 4.0 gets updated.
Your JS can go into “HEAD content” as before.
That’s great to hear, thanks!
The way each widget is documented is slightly different in v4, and we should have those calls available with tomorrow 4.0.2 update.
You can put https://raw.githubusercontent.com/xibosignage/xibo-cms/release33/web/swagger.json in the “Explore” bar at the top of the swagger does to get v3’s version.
Thanks Dan for getting back with me. Do you think by the end of this month you’ll have the Modules and Widgets section of the APIs complete for the new version 4.0?
Annoyingly they didn’t get pulled through due to a missing bracket. If you put https://raw.githubusercontent.com/xibosignage/xibo-cms/654d60a6f453e3666d7b41d86229642a3fc5ada6/web/swagger.json in the explore bar at the top of the current docs you can see the two new calls which help adding widgets.
There will also be a new page in the main developer docs explaining how to use those calls, as well as what is and isn’t supported yet. I’ll come back here when that is live.
1 Like
Hi Kevin, I have the same problem in the production version 4.0.3. Is this issue solved?
Hi Digin. My issue was actually somewhat self-inflicted but the great team at Xibo helped me to figure out the cause of my particular issue and I got it corrected. My issue was that my DNS settings on the container weren’t configured correctly so my API key validation was failing. Hopefully your issue is something similar and easily fixable!