|
Understanding Checker Results
The checker will say PASS or FAIL. But the checker has details that can sometimes be confusing, but very often hold clues to why a site PASSes or FAILs. To help you understand and overcome problems, I offer a variety of test results along with explanations.
At one time, when you submitted your site to its very first ring, this would have been your test result:
The checker hasn't yet tested your site thus it can neither PASS nor FAIL. If your site was approved at this point to join a ring running on Conditional Approval, your membership would be suspended. Conditional approval requires a test result of either PASS/PASS-L in order to be active. Eventually, the system was tweaked to do an immediate check of a submitted URL, this way, subsequent submissions would PASS if the coding was installed properly for the first Ring application. This saved some work on the part of both the member and manager. While this precise screen is rarely seen anymore, it remains on this page for the purpose of being thorough. Screens you will see now appear and are defined below.
SSNB PASS
If you are using the Server Side Navigation Bar, you need only concern yourself with the section of the test shown in parenthesis. When the checker finds the correct combination of User ID and U# on the registered URL, the membership will PASS. The PASS means that the correct SSNB was installed by the member. This means that the Navigation could be faulty, but that would then be the fault of the RingMaster, not the member.
HTML PASS
If you are using the HTML version, ignore the details in parenthesis, as you won't have a USER ID or U# within the HTML. You need only concern yourself with the minimum required links. You may see some elements FAILing, but the overall test PASSes, as shown below
SSNB PASS-L
As you can see in contrasting this graphic with the SSNB PASS, the only difference is the "-L". The details are the same, only the location of the navigation has changed. It is essentially like the SSNB PASS except that NavBar stack is not displayed on the registered URL. If you need clarification of the differences between PASS and PASS-L, I have a page dedicated to it.
HTML PASS-L
Again, in contrasting this graphic with the HTML PASS, the only difference is the "-L". The details are the same, the location of the navigation is altered. It is essentially like the HTML PASS except that NavBar stack is not displayed on the registered URL. If you need clarification of the differences between PASS and PASS-L, I have a page dedicated to it.
General FAIL
Most FAILures are due to the code being absent from the registered URL (or properly linked as dictated by the rule of PASS-L. Some FAILures are confusing because the navigation appears on the site and there is little evidence of the problem in the details. Many FAILures appear just as the one in the graphic below, with two lines full of FAIL. Most FAILing sites can be fixed by examining the two-dozen reasons why sites FAIL.
Wrong U# SSNB FAIL
This one is prominently hidden. In other words, the facts are right in front of you, but if you don't know what the details mean, this won't even stand out as being a problem. Remember, that to get the SSNB to PASS, you need two elements: correct User ID and correct U#. In this one, the ID is right, but the U# is wrong. This is usually because the member holds multiple positions in the Ring and has installed the NavBar for a different membership or the URL was recently edited rendering the installed NavBar invalid (even though the Ring may still be visible on it).
404 URL FAIL
This is an easy FAILure to figure out because the 404 error is right there in the details. It FAILs because the registered URL cannot be found. Rarely it's due to incompatibility between the checker and the site host. Sometimes it's because a site is temporarily unresponsive or was removed. Many times it is due to a misspell in the URL. Look at the URL in site management. Copy and load it, see if it's accessible.
RM Preference FAIL
This is an HTML-only FAIL. When using SSNB you have the links that are required, but with HTML, the checker is looking for any links required by the RM (only problem is that sometimes the RM establishes required links without coding them into his Ring's NavBar!) So, you could post the provided HTML and still FAIL because of a RingMaster error. In addition to the details shown below, you'll also see a notation on site management that reads: Your Site is currently suspended: It shows as not PASSing according to RingMaster preference..
Wrong ID SSNB FAIL
This one is mighty bizarre on so many levels. This is a rare bird, indeed, and usually the result of an incomplete migration. What complicates this is that the member doesn't always know that there is a migration problem. The membership can show in the User's account but not be considered migrated by the system. If you as the member see details like what is circled below, contact the manager and ask him to check to see if the membership is migrated (and, if it's not, request that he assign it to your ID). If you as the manager see these details, immediately assign the membership to the ID that is associated with that stack. (Yes, some members only migrated selected memberships!)
|
