Understanding and Using Debug Mode
Much of a RidgeStar Interactive Site
is interactive, operates in real-time, and is driven by the current status of one or more Database Tables. Many of the web pages produce information, like results lists, based on a dynamically created SQL (Structured Query Language) construct that is executed by the backend database.
Additionally, various functions on the site contain multiple internal messages, value settings, etc. that are useful when looking at how a particular page or function is operating from an "Internals" standpoint. Much of this information is of no consequence to a typical Visitor and, in fact, to 99% of the SiteManagers. However, when something isn't quite going right and one of the RidgeStar technicians needs to debug a bit of logic, we may need to "trigger" certain internal elements (such as dumping of internal arrays, calling lists, etc.) without being forced to manually change the pages.
- Turning ON Debug mode
- You can activate debug mode by adding the keyword sequence "debug=1" to any interactive page. You need to understand how HTTP uses the question mark (?) and ampersand (&) to separate keywords from the page name, but here's an example using this page of what you'd put in the Address/Location area:
http://ridgestar.com/debugmode.php?debug=1
- Turning OFF Debug mode
- To disable debug mode, add the keyword sequence "debug=0" to any interactive page, as
http://ridgestar.com/debugmode.php?debug=0
What happens when Debug is on?
The specific output associated with Debug Mode differs from page to page depending on what the RidgeStar Technician programmmed for Debugging purposes on the page.
