HELP!

  • Thread starter Thread starter PM
  • Start date Start date
P

PM

My site is made by FrontPage and there are 51 validation errors and my
keywords and description are not being read so my site does not come up
on Google at all. Missing attributes are a big problem and many
others. Is there someone that is brilliant that likes a good challenge?
I would sure appreciate it and sing his/her praises! Let me know! Best
to email me privately. Thanks in advance!
 
Best to email me privately.
Actually it's not.

This is a peer-to-peer group. Questions asked, and answered in the group
benefit everyone.

Bob Lehmann
 
Okay then... Not a problem.

Here is one of a few typical errors I am getting off the validator...
Hope someone can help!

Error Line 71, column 36: there is no attribute "LEFTMARGIN" .
<body bgcolor="#000000" leftmargin= "50" link="#6B6812" vlink="#463E02"
alink="#
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.
 
Post a link to the page, please.

The way to fix that error is to not declare your margins in the body tag -
use CSS instead.
 
1. If the keywords don't match text that is readable on the page, they will
be ignored.
Example, If you have a keyword "Cinderella" and Cinderella's not in the
"readable" text on the page the keywords are ignored.
2. The major search engines no longer use keywords.
The work with the page title that shows between the <title></title> tags and
the actual readable text on the page.
( plus some other things )

3. FrontPage only creates html specified by it's operator.!!
So, you need to switch to code view, find the leftmargin error and fix it,
which means removing the offending code, then right clicking and applying
the margin via page properties or an external CSS sheet.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
That one is pretty obvious - you have something called "LEFTMARGIN" in your
page. Make it lower case ONLY. Note this: "> (Remember XHTML is all
lower-case)"
 
1. If the keywords don't match text that is readable on the page, they
will be ignored.
Click to expand...

Actually, keywords are always ignored, except when they don't match - then
this may be used to penalize you. Or so current urban legend goes....
 
Change this -

</head>

to this -

<style type="text/css">
<!--
body { margin-left:50px; }
-->
</style>
</head>

and remove the margin attribute from the body tag.
 
Steve: In respect to #3, I did exactly that originally. THat is how I
created the margin. None the less, I removed the offending code which
of course bumped my table up against the left wall.. I then right
clicked... selected page properties, went to margins, checked the lower
box for left margin, put the 50 back into it. Then ftp-d the page again
and got the same error. Now what?
 
Murray: I tried this and my page was gone. I got it back of course but
the incertion and deletion did not work. I think I did it as you said
though. Directions seemed clear. Maybe now with the link and the
validator you can take a look at that instead my wasting so much time.
I should have thought of that from the begining. I appologize to all. I
am new to this. Beare with me please.
 
I'm a little confused about what it is you want to do at this point.

Anyhow, change this -

<style type="text/css">
<style>
..textonpage {

to this -

<style type="text/css">
..textonpage {

And also, change this -

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>

to this -

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

and tell me what you want beyond that.
 
Thank yoiu very much. However, I think it converted stuff because it
doesnt look right on the webpage with tha tlink there. I tried to fix
the distorted < code but that is as far as I can do on my own. Please
tell me how to fix the errors. I now have 10 more errors than I did
beffore this upload. Thank you for your help!
 
PS. When I typed it in exactly as you did it still diddnt look right.
It dropped my table down an inch or so. So I am thinking I do not have
this set right. Sorry that I am such a newbie!
 
Here is another question: I get alot of these errors and I really think
the FP is warping stuff such as my response to you regarding the
changes you suggested. How do I reset that. And take a look at this....
I have alot of these errors and I can see the problems on the html code
but do not know what to do about them. Please, please, please help! I
think this html is going to drive me crazy!

&nbsp;</td>
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 "&amp;" (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 &aelig;
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.
 
Back
Top