Understanding and Using Debug ModeMuch of a RidgeStar Interactive Site 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
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. The following element is an example of how a Debug result might appear: To see this in action, click to Locations and watch the SQL results... Restricting Debug OutputYou're also likely to notice that debug mode can produce a LOT of output at times. You can restrict the Debug output to only that which matches specific situations by adding "criteria" after the debug activation by specifying a comma and then the desired character string, as in: The restricted output string compares the origin location string of each output Backtrace entry and will include the output only if the specified case-sensitive character string is present in one or more of the backtrace identifiable calling points. In this example, the Debug entry is exposed because the string "ExampleFunction" was present in the Backtrace for the testing point above and the other debug expansions at the top and bottom of this page are suppressed because they do not contain the specified string. Use of this technique can be very effective at eliminating unwanted debug results that you may not have an interest in. Happy debugging! | |||||||
|