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
page is not Valid XHTML 1.0 Transitional!
- sone12
- Joomla! Champion
- Posts: 5440
- Joined: Wed Oct 11, 2006 1:12 pm
- Location: Kristiansand, Norway
- Contact:
page is not Valid XHTML 1.0 Transitional!
Last edited by sone12 on Wed Jun 13, 2007 8:27 pm, edited 1 time in total.
Kristian P. Granrud - Global Moderator
-
- Joomla! Intern
- Posts: 89
- Joined: Tue Jun 27, 2006 4:41 pm
- Contact:
Re: page is not Valid XHTML 1.0 Transitional!
Yup, I get that too.
Also in Beez I get a whole bunch of errors that cannot be found in the markup. weird, huh?
Also in Beez I get a whole bunch of errors that cannot be found in the markup. weird, huh?
Ian
- n2design
- Joomla! Apprentice
- Posts: 33
- Joined: Wed Jun 06, 2007 6:13 am
- Location: chicago
Re: page is not Valid XHTML 1.0 Transitional!
I built a tablesless site based off the beez template and it validates.
-
- Joomla! Intern
- Posts: 89
- Joined: Tue Jun 27, 2006 4:41 pm
- Contact:
Re: page is not Valid XHTML 1.0 Transitional!
Great,
But anyone have any notion as to why I am getting all tis junk dumped in the markup?
But anyone have any notion as to why I am getting all tis junk dumped in the markup?
Ian
- n2design
- Joomla! Apprentice
- Posts: 33
- Joined: Wed Jun 06, 2007 6:13 am
- Location: chicago
Re: page is not Valid XHTML 1.0 Transitional!
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.
Also get the web dev tools for firefox. It is your talking mirror.
-
- Joomla! Intern
- Posts: 89
- Joined: Tue Jun 27, 2006 4:41 pm
- Contact:
Re: page is not Valid XHTML 1.0 Transitional!
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/
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/
been using it for years but not a lot of use in this instanceAlso get the web dev tools for firefox. It is your talking mirror.
Ian