So you think you have an education

During a period of unemployment I went to learn something about computing.

This was in the late '80's early '90's. …

Today I tried to find out what college I went to to learn about the internet tube line thingie.

I went sooooo long ago I had forgotten the name of the place. I knew where it was though, roughly.

So I plugged in the website I came up with and got the courses offered link:

http://www.llandrillo.ac.uk/courses/2011-2012/location/default.aspx?loc=L

Being the place I got my IT qualification I though it should do better than this:

Server Error in '/' Application.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.Odbc.OdbcException: ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.

Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[OdbcException (0x80131937): ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.]
System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) +1156770
System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle) +95
System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions) +53
System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +55
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +29
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +4863708
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.Odbc.OdbcConnection.Open() +40
courses_location_Default.Page_Load(Object sender, EventArgs e) +1265
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

Version Information: Microsoft .NET Framework Version:2.0.50727.3625; ASP.NET Version:2.0.50727.3618

Having seen the word "[Microsoft]" in brackets I thought :
Must be me on linux.

So I looked up the page quality for the Home Page on the international mark up service offered by the web standards authority W3C:

Originally posted by W3C:

Markup Validation Service

Check the markup (HTML, XHTML, …) of Web documents
Jump To: Notes and Potential Issues Validation Output
Errors found while checking this document as XHTML 1.0 Transitional!Result: 31 Errors, 27 warning(s)
Address:
Encoding: utf-8
Doctype: XHTML 1.0 Transitional
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml

The W3C validators rely on community support for hosting and development.
Donate and help us build better tools for a better web.
OptionsShow Source Show Outline List Messages Sequentially Group Error Messages by Type
Validate error pages Verbose Output Clean up Markup with HTML-Tidy

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

Character Encoding mismatch!

The character encoding specified in the HTTP header (utf-8) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation.

↑ Top
Validation Output: 31 Errors
Line 11, Column 4: "if" is not a reserved name
<![if !IE]><link rel="stylesheet" type="text/css" href="css/non-ie.css" /><![en…


Line 11, Column 7: character data is not allowed here
<![if !IE]><link rel="stylesheet" type="text/css" href="css/non-ie.css" /><![en…

You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
putting text directly in the body of the document without wrapping it in a container element (such as a

aragraph

), or
forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
using XHTML-style self-closing tags (such as <meta … />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
Line 11, Column 78: "endif" is not a reserved name
… !IE]><link rel="stylesheet" type="text/css" href="css/non-ie.css" /><![endif]>


Line 84, Column 75: character "&" is the first character of a delimiter but occurred as data
…>Guidance & Support

This message may appear in several cases:
You tried to include the "<" character in your page: you should escape it as "<"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 164, Column 93: required attribute "alt" not specified
…elsh-for-adults/">

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 252, Column 32: there is no attribute "onMouseover"

  • element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 252, Column 79: there is no attribute "onMouseout"
    ….imagename.src=image1.src" onMouseout="document.imagename.src=image1.src" href…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 250: there is no attribute "src"
    …ss" value="always">

    element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 312: there is no attribute "type"
    …v/xh0VaAmo5AU?fs=1&hl=en_GB" type="application/x-shockwave-flash" allowscr…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 362: there is no attribute "allowscriptaccess"
    …/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="3…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 387: there is no attribute "allowfullscreen"
    …scriptaccess="always" allowfullscreen="true" width="310" height="215">…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 400: there is no attribute "width"
    …cess="always" allowfullscreen="true" width="310" height="215">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 413: there is no attribute "height"
    …cess="always" allowfullscreen="true" width="310" height="215">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Line 269, Column 418: element "embed" undefined
    …cess="always" allowfullscreen="true" width="310" height="215">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
    incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
    Line 296, Column 31: document type does not allow element "style" here
    <style type="text/css">.flickr_badge_image img {border: 1px solid #c7c7…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a "style" element in the "body" section instead of inside "head" — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
    Line 297, Column 160: cannot generate system identifier for general entity "display"
    ….flickr.com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=us…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 297, Column 160: general entity "display" not defined and no default entity
    ….flickr.com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=us…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 167: reference not terminated by REFC delimiter
    ….com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 297, Column 167: reference to external entity in attribute value
    ….com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 297, Column 167: reference to entity "display" for which no system identifier could be generated
    ….com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 159: entity was defined here
    …w.flickr.com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=u…
    Line 297, Column 175: cannot generate system identifier for general entity "size"
    …ge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=437…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 297, Column 175: general entity "size" not defined and no default entity
    …ge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=437…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 179: reference not terminated by REFC delimiter
    …ode_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=4378749…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 297, Column 179: reference to external entity in attribute value
    …ode_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=4378749…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 297, Column 179: reference to entity "size" for which no system identifier could be generated
    …ode_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=4378749…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 174: entity was defined here
    …dge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43…
    Line 297, Column 182: cannot generate system identifier for general entity "layout"
    …_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%4…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 297, Column 182: general entity "layout" not defined and no default entity
    …_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%4…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 188: reference not terminated by REFC delimiter
    …e?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 297, Column 188: reference to external entity in attribute value
    …e?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 297, Column 188: reference to entity "layout" for which no system identifier could be generated
    …e?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 181: entity was defined here
    …e_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%…
    Line 297, Column 191: cannot generate system identifier for general entity "source"
    …ount=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 297, Column 191: general entity "source" not defined and no default entity
    …ount=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 197: reference not terminated by REFC delimiter
    …&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Websit…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 297, Column 197: reference to external entity in attribute value
    …&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Websit…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 297, Column 197: reference to entity "source" for which no system identifier could be generated
    …&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Websit…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 190: entity was defined here
    …count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag…
    Line 297, Column 207: cannot generate system identifier for general entity "user"
    …andom&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></scrip…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 297, Column 207: general entity "user" not defined and no default entity
    …andom&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></scrip…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 211: reference not terminated by REFC delimiter
    …m&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 297, Column 211: reference to external entity in attribute value
    …m&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 297, Column 211: reference to entity "user" for which no system identifier could be generated
    …m&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 206: entity was defined here
    …random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></scri…
    Line 297, Column 227: cannot generate system identifier for general entity "tag"
    …layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 297, Column 227: general entity "tag" not defined and no default entity
    …layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 230: reference not terminated by REFC delimiter
    …layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 297, Column 230: reference to external entity in attribute value
    …layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 297, Column 230: reference to entity "tag" for which no system identifier could be generated
    …layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 297, Column 226: entity was defined here
    …layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script>
    Line 485, Column 10: end tag for "ul" which is not finished

    Most likely, you nested tags and closed them in the wrong order. For example

    is not acceptable, as must be closed before

    . Acceptable nesting is:

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a

    child element, lists require appropriate list items (

      and
      require
  • ;
  • requires
    and
    ), and so on.
    Line 495, Column 74: character "&" is the first character of a delimiter but occurred as data
    …ext" style="margin-left:20px;">Advice & Guidance: 01492 542 338/9<br…

    This message may appear in several cases:
    You tried to include the "<" character in your page: you should escape it as "<"
    You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
    Another possibility is that you forgot to close quotes in a previous tag.
    Line 509, Column 106: cannot generate system identifier for general entity "continue"
    …llo.ac.uk/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 509, Column 106: general entity "continue" not defined and no default entity
    …llo.ac.uk/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 509, Column 114: reference not terminated by REFC delimiter
    …k/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A443%2Fa%…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 509, Column 114: reference to external entity in attribute value
    …k/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A443%2Fa%…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 509, Column 114: reference to entity "continue" for which no system identifier could be generated
    …k/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A443%2Fa%…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 509, Column 105: entity was defined here
    …illo.ac.uk/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3…
    Line 509, Column 200: cannot generate system identifier for general entity "passive"
    …panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
    Line 509, Column 200: general entity "passive" not defined and no default entity
    …panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 509, Column 207: reference not terminated by REFC delimiter
    …panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
    Line 509, Column 207: reference to external entity in attribute value
    …panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
    Line 509, Column 207: reference to entity "passive" for which no system identifier could be generated
    …panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
    Line 509, Column 199: entity was defined here
    …panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email

    ↑ Top
    Home About… News Docs Help & FAQ Feedback Contribute

    This service runs the W3C Markup Validator, v1.2+hg.

    Copyright © 1994-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.

    I'd have thought a college in Britain would have valid website standards. It would seem they are all just Microsft clowns or clones or whatever the word is.

    At least it explains my problems with computing. A perpetual lamer.

    But even as a lamer, I would have gone to the web validation site and got it checked out.
    What do |I do now.

    Write and tell them?
    Hardly. They have IT tech and teachers teaching IT tech as far as I know. Or maybe they got out of that line after so many failures like me wanted our money back (I didn't get it but I managed to slip in their not for students site and found some comments about my bad temper. To which I added a few comments of my own.)

    So now it's pay back time.
    Not really.

    My problem is I need the address for my CV.
    Would you add a college like that to your CV?
    Or smear it into obscurity with the wrong name or something and hope it gets by the board?

    TBH I don't care that much. I don't have much in a recent CV and the job on offer isn't that good a job.
    Can someone out there please supply me with a reference?

    Advertisements

    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s