Announcement

**nottheusual1** · 02-14-13, 07:05 AM

Re: W3C Markup Validation Service say no character encoding found

Put this inside your head tag. Replace UTF-8 with whatever is appropriate:

Code:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

**joseibarra** · 02-15-13, 04:34 AM

Re: W3C Markup Validation Service say no character encoding found

That seems to work, but the W3C validator complains about many things that I don't think I can do anything about, even the line I just added, it says:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" > <---this part shows in red You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

There is no space that I can see but I guess maybe Miva is adding it somehow (there are alot of them).

I looked at some other Miva stores and the Validation Service complains heavily on all of them for these kinds of things.

**jsdva** · 02-15-13, 05:33 AM

Re: W3C Markup Validation Service say no character encoding found

First off, you are missing your opening html tag. Doctype declaration then <html> then <head>. Sometimes, something at the beginning will cascade to the bottom of the page creating more errors when validating.

Then, you have the trailing slash on some of your tags and others you don't. ( /> or > at the end of a tag) Pick your doctype to determine if you need the trailing slash. XHTML strict uses the trailing slash, but XHTML transitional does not. http://www.w3.org/QA/2002/04/valid-dtd-list.html This alone will clean up a lot of errors. But, learning lesson here is that you code for the doctype, and don't but in doctypes willy-nilly...it does matter.

As for the links, Miva's long links will not validate, so either go to short links or ignore those errors.

border=0" This is a deprecated tag. Besides, you should put all styles into your style sheet.

I'll stop here. Fix the above, and validate again. Then see what else you need to fix. Once you get that html tag in and decide on your doctype, it will be much easier.

Jamie

**Gene->** · 11-13-13, 11:47 AM

Re: W3C Markup Validation Service say no character encoding found

I find this fix works on the PROD page Production Release 8 Update 12 , W3C validators choke on the ampersand entity not being echoed correctly. This solution took 5 validation warnings off of the PROD page:

PROD page produces 5 errors with the following 2 tokens on the PROD page

<mvt:item name="attributemachine" param="head" />
<mvt:item name="product_display_imagemachine" param="head" />

http://validator.w3.org/check?uri=ht...org%2Fservices

FIX

Hard code and it clears the errors:


<script src="/mm5/clientside.mvc?T=4e73658e&Filename=AttributeMa chine.js"></script>
<script src="/mm5/clientside.mvc?T=4e73658e&Filename=ajax.js"></script>
<script src="/mm5/clientside.mvc?T=4e73658e&Filename=runtime.js" ></script>
<script src="/mm5/clientside.mvc?T=4e73658e&Filename=MivaEvents. js"></script>
<script src="/mm5/clientside.mvc?T=4e73658e&Filename=ImageMachin e.js"></script>


Comments encouraged.

G