Need to make my website W3C valid.

I am looking for a programer to help fix a few erros on my site to help it pass the Validation.
This will take a few hours so if you can PM your rate per hour.

This will be an ongoing job and I am looking to have it started right away.

Many Thanks

From what I can se most of the errors I have are from Categories & Information.

Example

1/
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

2/
Line 219, Column 93: reference to external entity in attribute value
/index.php?route=product/category&path=8877998_8878021">Bath Screens</a></li> …

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.

If you can help can you PM me please.

Many Thanks

Problem is now sorted please close.

Jay once again has done some fine work for me.
Thanks again Jay.

Kind Regards

would have been nice to tell us what you did. im looking to resolve the same thing...

Me too, getting a lot of problems with ampersands instead of &

ditto to above posts ...

any solutions to the ampersand problem ?

thanks in advance

If you want to fix it yourselves you'll need to find all the places where the ampersands are not escaped, and do so...why does that need explaining?

I just fixed an issue regarding ampersands in the Sort feature. It stumped me at first, since merely changing the ampersands to their HTML entities in the "catalog/controller/product/catalog.php" file wasn't doing anything. Seems as though the entities were being changed back before being sent to the browser.

The simple workaround I used is this:

Open your "template/product/category.tpl" file and find this bit of code: Replace it with this bit of code: It merely, converts the ampersands in the URLs back into their HTML entities before serving it to the browser. It worked like a charm for me.

I haven't checked a lot of the other types of pages on my site, yet - so I'd be interested in hearing anyone's experience with other aspects of OC not validating.

Cheers!

It is very interesting topic as well as I got the perfect information why w3c is needed for my website. It is really excellent information you shared with us.

screamkitty wrote:I just fixed an issue regarding ampersands in the Sort feature. It stumped me at first, since merely changing the ampersands to their HTML entities in the "catalog/controller/product/catalog.php" file wasn't doing anything. Seems as though the entities were being changed back before being sent to the browser.

The simple workaround I used is this:

Open your "template/product/category.tpl" file and find this bit of code:

Code: Select all

<select name="sort" onchange="location = this.value">
          <?php foreach ($sorts as $sorts) { ?>
          <?php if (($sort . '-' . $order) == $sorts['value']) { ?>
          <option value="<?php $echo $sorts['href']; ?>" selected="selected"><?php echo $sorts['text']; ?></option>
          <?php } else { ?>
          <option value="<?php echo $sorts['href']; ?>"><?php echo $sorts['text']; ?></option>
          <?php } ?>
          <?php } ?>
        </select>

Replace it with this bit of code:

Code: Select all

<select name="sort" onchange="location = this.value">
          <?php foreach ($sorts as $sorts) { ?>
          <?php if (($sort . '-' . $order) == $sorts['value']) { ?>
          <option value="<?php $sortsafe = htmlentities($sorts['href']); echo $sortsafe; ?>" selected="selected"><?php echo $sorts['text']; ?></option>
          <?php } else { ?>
          <option value="<?php $sortsafe = htmlentities($sorts['href']); echo $sortsafe; ?>"><?php echo $sorts['text']; ?></option>
          <?php } ?>
          <?php } ?>
        </select>

It merely, converts the ampersands in the URLs back into their HTML entities before serving it to the browser. It worked like a charm for me.

I haven't checked a lot of the other types of pages on my site, yet - so I'd be interested in hearing anyone's experience with other aspects of OC not validating.

Cheers!

Thanks! I had the same problem on OC 1.5.1.2 fixed now