|
|
|||
|
|
|
The WebRing.com System
Invalid Code: This page explains this error message from WebRing.com and provides several possibilities to identify the root cause and correct the error.
Invalid Code: ID/U# Mismatch One of the errors most commonly reported to the various help forums at WebRing.com is Invalid Code: ID/U# Mismatch. The error message looks something like this: This page explains this error message and provides several alternate possibilities to identify the root cause and correct the error. Clicking the Link If you click on the link that says "Click for assistance" you will go to a web page on the WebRing.com system that will attempt to help you correct the problem. The most common cause of emails to me and to help forums is confusion about this page, and, in particular, confusion when the system says that what you need is already what you have. The information below attempts to help resolve this, and other similar issues. Immediately After New Membership Sometimes when users click the link they receive a page that says that the ID and U# that is on the page is already what is required. This causes confusion and is the most frequent cause of emails about this particular error. The most common cause of this particular error is "server delay". Many people new to the WebRing.com system are used to dealing with a single computer and a single database. The WebRing.com system is spread among multiple databases running on multiple servers. The advantage is that it is easily "scalable". It can grow and expand easily. The disadvantage is that it requires all of these various databases on the various servers to communicate with each other. Also, many people expect that the "results" that display are derived from a direct inquiry to the database. Frequently this is not the case. In order to "save time", the WebRing.com system pre-answers questions so it won't have to answer them every time they are asked. Take, for example, the red, yellow and green indicators that indicate whether a site is correct or not. These indicators are pre-set by the system. They do not indicate the "current status" of the site. They indicate the status the last time it was checked. Because it takes time for the servers to communicate, it takes time for a new membership to be "recognized" by the various servers involved. The result is that a new membership will sometimes display this error even though everything is ok. If your membership is very new (less than one day old) and everything looks ok, it is highly likely that this is the situation and this error will resolve itself with time. My suggestion: wait a bit. Wait a day. It will probably clear. Incorrect Code If it is not immediately after a new membership, the two most likely causes are
Server Communication Failures If the page says that the ID and U# you have are what you are supposed to have, and if you have waited a day, then it is likely that there was a server communication failure. The simple fix for this is to nudge the servers to talk with each other again. Here are the steps.
Incorrect Code There are several common causes of this:
Correcting the Code In all of these cases, the analysis is the same. Check your code. Confirm that the ID and U# that are assigned are actually the ID and U# on the page. When you find that the ID or U# is different, get the new, correct code and install it on the page. How to Correct the Code
Critical Information Whenever you change the registered page you must get new JavaScript. The JavaScript is based on the registered page. For more information on this, see my page that explains how the JavaScript works. I Am Here to Help If you have any questions, please don't hesitate to ask. Feel free to email me.
A
Personal Note:
I'm sorry. While I have long adopted webrings in the WebRing.com system, because of the Oct.2006 changes, I am no longer doing that. However, please note that "deleting" your webring is a fruitless exercise. The system will just restore it and place it up for adoption.
Articles About the WebRing.com System Webring Sections and Subsections The Webring Section is a large section of my website. I have divided it into four major "subsections".
Each "subsection" has it's own special "logo". As you travel in the various subsections you will find, near the bottom of each page, links to pages within that subsection and also links to the other subsections. To go to any subsection, just click on the "logo" or on the text link for that subsection.
Webrings: General Information This subsection includes general information about webrings. Webrings can be hosted by a variety of different services. This section deals with the overall concepts and issues, not with any one particular "brand" of webring. It includes my Webring FAQ, links to articles about webrings, and general help information. Click here or on the graphic.
The Wazillion Navbars Project This subsection is a historical section about the Yahoo! WebRing system. It was begun during the early days of problems with the Yahoo! WebRing system in September 2000. It ended when the Yahoo! WebRing system spun off into the independent WebRing.com system in October 2001. I maintain it for the historical record. Click here or on the graphic.
Webrings I Own and Belong To This subsection shows all the webrings I own and links to all the webrings to which I belong. This includes webrings in Ringlink, RingSurf, Bravenet and the WebRing.com system as well. If you are looking to join one of my webrings, this is a good place to start. If you wonder about the webrings I belong to, this is the place to go. Click here or on the graphic. |
|
This page created: Tue, 06.May.2003
Last updated: |
|
|
|
NOTICE - This site is currently undergoing extensive restructuring. Failing links are being identified and removed and the HTML is being corrected and revised to better use CSS Structures. I appreciate your patience while this effort is underway. Please feel free to email me about any errors you detect. Completion is currently estimated for December 2011. ■ Check out my ezine Snippets and blog My Ephemerae.
|
|
|
|
|
||
|
|
|
|
|
|