Page 1 of 1

page is not Valid XHTML 1.0 Transitional!

Posted: Wed Jun 13, 2007 8:25 pm
by sone12
The templates will not validate at http://validator.w3.org/

Here is the errors:

1 Error  Line 172 column 489: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

...no,location=no'); return false;" rel=nofollow><img src="images/M_images

Re: page is not Valid XHTML 1.0 Transitional!

Posted: Mon Jul 02, 2007 10:05 pm
by ijyoung
Yup, I get that too.

Also in Beez I get a whole bunch of errors that cannot be found in the markup. weird, huh?

Re: page is not Valid XHTML 1.0 Transitional!

Posted: Tue Jul 03, 2007 9:09 am
by n2design
I built a tablesless site based off the beez template and  it validates.

Re: page is not Valid XHTML 1.0 Transitional!

Posted: Tue Jul 03, 2007 9:54 am
by ijyoung
Great,

But anyone have any notion as to why I am getting all tis junk dumped in the markup?

Re: page is not Valid XHTML 1.0 Transitional!

Posted: Tue Jul 03, 2007 1:46 pm
by n2design
got a link, maybe i can see what junk your talking about.

Also get the web dev tools for firefox. It is your talking mirror.

Re: page is not Valid XHTML 1.0 Transitional!

Posted: Tue Jul 03, 2007 3:15 pm
by ijyoung
I have posted this elsewhere:

This is what is being found by validator:

Below are the results of checking this document for XML well-formedness and validity.

  1. Warning Line 164 column 886: cannot generate system identifier for general entity "f6051a5a517ff30a47ad04f5a13390c1".

      ...ef="component/user?task=lostPassword&f6051a5a517ff30a47ad04f5a13390c1=538849b

      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.

      ✉
  2. Error Line 164 column 886: general entity "f6051a5a517ff30a47ad04f5a13390c1" not defined and no default entity.

      ...ef="component/user?task=lostPassword&f6051a5a517ff30a47ad04f5a13390c1=538849b

      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.

I cannot, however, see this in the markup.

See http://www.iyesolutions.co.uk/Joomla1.5/
Also get the web dev tools for firefox. It is your talking mirror.
been using it for years but not a lot of use in this instance