Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't seem to validate for XHTML...

Status
Not open for further replies.
listen to what the validator is telling you. you need an opening <html> tag (and closing) in every HTML page.

fix those errors from top to bottom. often the first one resolves many (if not all) others.



*cLFlaVA
----------------------------
[tt]mr. pibb + red vines = crazy delicious![/tt]

[URL unfurl="true"]http://www.coryarthus.com/[/url]
 
I fixed the missing html tag but the rest still remain. The majority of the errors are telling me that the tags don't exisit in xhtml transitional.

Sorry for being a noob.
 
So what's the solution then? Is there certain adobe code that will never validate with xhtml?
 
Have you checked to see if they have a standard DTD?

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller
 
Have you checked to see if they have a standard DTD"

You mean a custom adobe DTD? To tell you the truth, I have no idea...The document defaulted to xhtml transitional.

"remove those csscriptdict tags. remove the invalid attributes."

Well didn't Golive put those in for a reason? Also saying 'remove the invalid attributes' isn't really helpful. If I just remove the attributes, I'll lose the content they were there for.

Or am I missing something?
 
Well didn't Golive put those in for a reason? Also saying 'remove the invalid attributes' isn't really helpful. If I just remove the attributes, I'll lose the content they were there for.

So replace them with valid CSS attributes instead. If you're going to use a front-end program to generate the HTML for your page, then you should be prepared to fix the garbage it spits out. Most people in this forum do not use WYSIWYG editors for that very reason.

-kaht

Looking for a puppy?

silky-icon-left.gif
[small]Silky Terriers are small, relatively odorless dogs that shed no fur and make great indoor pets.[/small]
silky-icon-right.gif
 
Or am I missing something?
Most likely. What you have out there looks like some kind of intermediate page (like GoLive isn't finished with it, or it hasn't been 'published' or whatever GoLive does when it completes).

All of the other comments posted here are valid. The <csscriptdict import="import"> tags aren't valid anywhere and the "height" tags aren't valid in XHTML.

Greg
"Personally, I am always ready to learn, although I do not always like being taught." - Winston Churchill
 
Nope.

GoLive produces horrible code and normally breaks anything you have fixed each time you reopen the page in GoLive.

The csscriptdict tags are put in by GoLive as it assumes you will be opening the page in GoLive again and they mark areas to mean something to GoLive.

Dreamweaver has similar proprietary tags that it uses to identify particular areas. Although I think Dreamweaver may use comments instead which is an altogether better solution.

Best advice. If you want to produce robust code then ditch GoLive. Alternately only ever use GoLive and live with the guff it spews.

<honk>*:O)</honk>
Foamcow Heavy Industries - Web site design in Cheltenham and Gloucester
Earl & Thompson Marketing - Marketing Agency Services in Gloucestershire
 
So it seems simple now:
Errors 1-3: Relate to a GoLive proprietary tags that are not understood by any browser, so you can delete them in notepad.
Errors 4-6: Refer to attributes that are not valid, i.e. don't exist in XHTML. Replace them with their css equivalents like [tt]height: 1px;[/tt] and [tt]background: url(...);[/tt] inside the style attribute.
Error 7: You're putting a div (block level element) inside a span (inline element) -- which is wrong. Put another span inside if you need a nested element or change the top span to div.
 
Actually I may be wrong about the csscriptdict tags
They are certainly proprietary but I'm not sure what GoLive uses them for.

From memory I *think* they refer to a set of generic javascripts that GoLive uses. It may upload this library as a seperate file alongside your site.

I don't have GoLive installed so I can't verify this but I have worked on a number of sites that were originally created with GoLive and basically needed to be redone.


<honk>*:O)</honk>
Foamcow Heavy Industries - Web site design in Cheltenham and Gloucester
Earl & Thompson Marketing - Marketing Agency Services in Gloucestershire
 
I use GoLive and all my sites validate. Those tags that no browser understands are there for GoLive to keep track of templates, components, action scripts, etc... GoLive has an option to strip all these tags when uploading to the server, all he has to do is turn that option on.

As for the other items, i don't know how they got there. He may have hand coded them or copy/pasted from someone elses code, etc... I'd say the things he's trying to do with them can be accomplished through other correct means. For example move the height attribute from the tr tag to the td tag.
 
GoLive has an option to strip all these tags when uploading to the server, all he has to do is turn that option on.

Ahhh, I know that at least one of the original authors of the site I fixed used to upload with an external FTP app rather than using GoLive. That would explain how they got left in.

<honk>*:O)</honk>
Foamcow Heavy Industries - Web site design in Cheltenham and Gloucester
Earl & Thompson Marketing - Marketing Agency Services in Gloucestershire
 
*Guilty face*

I would never use an external FTP program...

*Runs away
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top