Error 500 or blank page accessing Schedule with debug switched Off

Bug #316295 reported by Alex Harrington
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Xibo
Fix Released
Low
Dan Garner

Bug Description

I'm getting an error 500 in IE and a blank page in Firefox accessing the Schedule page when no displays are defined.

Related branches

Revision history for this message
Alex Harrington (alexharrington) wrote :

Triggers the following in the log.

<errormsg>No licensed Displays</errormsg>
<errornum>256</errornum>
<errortype>User Error</errortype>
<scriptname>/sites/xibo.longhill.org.uk/htdocs/xibo-server/server/lib/pages/schedule.class.php</scriptname>
<scriptlinenum>100</scriptlinenum>

description: updated
Revision history for this message
Dan Garner (dangarner) wrote : Re: Error 500 or blank page accessing Schedule

This is more of a fault with the error logging procedure.

With debug off halt errors should still be displayed to the user.

Changed in xibo:
assignee: nobody → dangarner
importance: Undecided → Low
milestone: none → 1.0.0
status: New → Confirmed
Revision history for this message
Dan Garner (dangarner) wrote :

Having thought about it this is actually a fault of both.

The Debug class should always output E_USER_ERROR to the browser - this is used widely to indicate an error that should cause a halt and output something meaningful to the browser. Currently it is only doing this when Debug is On.

Also the Schedule class currently checks for enabled displays in the __construct. This is OK but it is not good generating a HALT error there - as the message will be outputted before any UI is built.

Solution:
Fix the Debug class to do what was intended.
Improve the Schedule class to delay the output until the displayPage method is called (there by outputting the error within the UI)

Dan Garner (dangarner)
Changed in xibo:
status: Confirmed → Fix Committed
Changed in xibo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.