Xibo

invalid layout error

Asked by Badre-edine

Hello,

Sorry fo disturb, but this is my last way to figure out what exactly is my issue : i've installed xibo v1.6.0 displays under Win7, all went well during the installation, but when trying to schedule a Layout this can't pops out on the display it can show only the default layout, on logs i got ... invalid Layout

So i ve tryed to reinstall the server but this one using the v1.4.2, this works well and no error is poping out. since the last version has many functioality and bug fix's i wanna use it, but how resolve my issue.

Any help will be greatfull

Many thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Alex Harrington
Solved:
Last query:
Last reply:
Revision history for this message
Dan Garner (dangarner) said : 		#1

We would need a little more information from the 1.6.0 installation to work out why you are having this problem. In particular we will need to see a screenshot of the client information screen when you think it should be playing the layout you have scheduled.

This is accessed by pressing "i" on the keyboard and will show us all the necessary information for what is happening inside that client.

Revision history for this message
Badre-edine (badre-edine) said : 		#2

Hi,

First i wanna give a special thanks to all staff who made this tool ... and thank you for your return and taking care of my case

Here's a shot form the log file :
UI Thread|21/05/2014 12:41:56|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|21/05/2014 12:42:03|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 6
UI Thread|21/05/2014 12:42:07|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|21/05/2014 12:42:13|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 6
UI Thread|21/05/2014 12:42:17|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|21/05/2014 12:42:23|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 6
UI Thread|21/05/2014 12:42:27|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout

MAny thanks

Revision history for this message
Alex Harrington (alexharrington) said : 		#3

Your layout is invalid. Perhaps because it has no regions, or regions which
are empty?

Revision history for this message
Badre-edine (badre-edine) said : 		#4

i made a layout template (witch with no media attached on the regions), and with it i made 4 other layouts with diferent media element and then i attached each one as a default layout for each dispaly.

do you think that this hole thing (since i passed 2 weeks trying to troubleshoot it) is about my empty media template ?

I'll try creating new Layout with no template for each display ...

Revision history for this message
Badre-edine (badre-edine) said : 		#5

in the v142 i did create for each display a layout with no template and it works fine .... i ll try to recreate my layout with no templates in v160

Revision history for this message
Best Alex Harrington (alexharrington) said : 		#6

All layouts must have at least one region, and all regions must have at
least one media item in them.

If your layout doesn't conform to that then it's invalid and won't be shown

Revision history for this message
Badre-edine (badre-edine) said : 		#7

Iyes Indeed, i happy to annonce you that after remaking all layouts, that's works correctly, however i still see some repeated errors on logs

58815 2014-05-22 14:20:25 <errormsg>mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead</errormsg>
<errornum>8192</errornum>
<errortype>Deprecated Call</errortype>
<scriptname>G:\Xampp\htdocs\xibo\3rdparty\oauth-php\library\store\OAuthStoreSQL.php</scriptname>
<scriptlinenum>77</scriptlinenum>

Any ideas on this please ?

Revision history for this message
Alex Harrington (alexharrington) said : 		#8

They're only warnings. Assuming you're running the maintenance script
correctly they'll be purged from the database periodically so you can
safely ignore them

Revision history for this message
Badre-edine (badre-edine) said : 		#9

All right then Alex, Thanks a lot for your support and help on this topic. hope will be in touch for better things :-)

Revision history for this message
Badre-edine (badre-edine) said : 		#10

Thanks Alex Harrington, that solved my question.