Information
Logon

FAQ

Logonhelptranslate
LastDisplayField Addresses and Status |San Francisco Youth Soccer

RidgeStar.com and Referees.biz Help PagesPrintable

RidgeStar has scattered useful documentation in several places:
1) on this site
2) on www.RidgeStar.com
3) on www.referees.biz

Here are links to some of the information that might be helpful

Date-> Comparator - Use > < <> and the like to look at specific date ranges

Date Formats-> - Identifies what dates will be accepted and what they will be interpreted as.

Error message - Change the actual wording of error messages by making a Setting=Messagexxxx

Fragment-> Wild Card - Use _ (Underscore) as a single wild card and % as a multiple wild card in fragment fields.

Help bubble - help Place a help bubble after error messages by making a Topic with Tag=Messagennnn

Term bubble - term Place a popup with a defined Term by using [ term={defined word} ] Terms are defined at Information:Terminology

Page Design-> - Describes the fundamental page design of each page on the site. Gives terminology of the different areas.

Symbols-> - The names and meanings of all those little guys in the ixxxx.png format. (Right click on a symbol and look at Properties to find a symbol name.) This from the Ridgestar.com site. This is list is more comprehensive (takes a while to load).

Text Format-> - As used in the Topics, and Issues Mechanism. Paragraphs, Line breaks, bold, reference to the site name, and more

Text Format - More Text Format options. Underline, inserted symbols.

Token format - 'Tokens' is the RidgeStar term for the instructions included in square brackets. The 'Token' instructions are ended when a space is encountered. That is why you need to use the tilde ' ' as a space if you want a text formatting token to encompass more than one word. HOWEVER there is a problem if you use the Token [ :imagename ] to insert an image into text (such as in an Event or Topic/Text element). The trailing square bracket must have a space after it. If you put a character, such as a period after the trailing bracket, you will generate an error symbol error .

Topics & Text-> - How to add and format 'static' pages to the site. Used for Stuff to Know and FAQ. Can also be used to create pages linked to from Events or even emails.

Setting values - Report a setting value with [ csoSetting ] If the setting has multiple values you can use something like [ csoSetting ][ Strength ]

Debugging commands

For the 5.2 and up systems, there is developer, setsql, and debug (as well as properties and diagnose, although I'm not sure you ever used those).
Developer is something I use when I'm hyperfocused on some specific task within a routine I'm working on. It will produce almost random sorts of output, depending on .... whatever it is that I'm working on.
SetSQL should always show you the SQL string it's about to execute. For 5.2 systems, this'll be all nicely packaged and look to the human like a "normal sql string". Pre 5.2 systems will still dump it out, but...it (the SQL string) may or may not appear cleanly (could be split into the Bind segment and the command segment).
Debug dumps out the gory details of all the routines calling each other and what they pass and return. As you correctly note, it's a lot of information (thus, the syntax debug=1,{qualifier} is very useful to home in on what you're seeking). Debug 1 and 2 have disappeared from 5.2 and up systems, as there was insufficient "granularity" between what they meant. For your purposes, SetSQL will be most useful as it's the closest thing to what the pre 5.2 systems called debug=1. The 5.2 debug=1,{fragment} is most closely the pre 5.2 debug=2 or even the occasional debug=3 (that's why it produces so much "output" and why I found it necessary to add the ability to filter it via fragment). It (5.2's Debug) could be way more information than you'll find useful...or not, if you're just trying to follow the flow (but, if I was you, I'd avoid the debug=1 option unless you plan to use a fragment to focus it on something (like a specific Routine, etc.).
?propeties=1 in the URL tail to see which pages have PageText established.

Debugging commands details

?debug=1,5432 will provide information on the customizable Top and Bottom PageText

*