Goodness that’s quite a few errors! Some of the things it picked up I’d have to question the reliability. If I’m reading the results right, it appears to be adding spaces and calling those errors. I’ll take a more thorough look and see what I can do. Not sure how much of it is my posts or how much is the template, but good info to know.
But errors aside, they wouldn’t necessarily keep me from making the modifications I listed above would they?
I’d have to question the reliability.
You shouldn’t. Trust me: those are all real errors and 99.99% caused by the user/blogger: either by posting or by adding faulty code to the template files.
Plus, it’s *cascading*. Start at the top and fix error #1 first. Usually, you’ll end up finding that fixing *one* error causes the rest to fall back into place.
All good advice and I really do appreciate it!
Looks like I have to reconsider the theme I’m using, although I can’t say for sure. A lot of that stuff appears to be referencing things that I wouldn’t have a clue to modify to even generate such errors (like #1).
On that note, things that I have changed and see errors on is why I’m questioning some of the reliability of the validator. Error #4 is one such item. It’s not recognizing the “target” attribute? Isn’t that standard or am I using it wrong?
And errors 2, 3, 5 and 6 are all related to an image that I have in my uploads folder. That’s one file that I’ve put in several of my posts using the Upload/Browse All feature when writing a post. Isn’t that the way that feature is supposed to work – to be able to pull the same image from before and put where I want?
I’m open to making the changes needed, but as you pointed out doodlebee, I’m hoping that fixing the early ones will resolve the later ones because that’s quite an intimidating list. 🙂
Can someone help me get started on how I should fix #1?
The target attribute isn’t valid in various XHTML versions. If you’re going to have XHTML (like wordpress), you can’t use the target attribute.
As for #1, just delete language="javascript" – it’s deprecated.
<script language="javascript" type="text/javascript" src="http://www.familywebwatch.com/blog/wp-content/plugins/fancytooltips/fancytooltips.js"></script>
it told you the problem.
that needs to be this:
<script type="text/javascript" src="http://www.familywebwatch.com/blog/wp-content/plugins/fancytooltips/fancytooltips.js"></script>
if thats being called via a plugin, then you’ll need to edit the plugin inseting it.
Re image: since the image has a unique ID – you cannot use it more than once. IDs can be used only once in a page. Eventually, removing the ID part from its code you’ll be able to re-use it.
error #1. – comes from the fancytooltip gizmo
(hint: check the Show source and click Revalidate: every error line # will become a link taking your to the exact location of the error)
Thanks everyone. Gonna roll up my sleeves and dive into this thing. I’ll report back. If anyone has comments in the meantime, I’ll be keeping an eye open for them. 🙂
When having troubles figuring out what the XHTML rules are: http://www.w3schools.com/xhtml/default.asp
Thanks, moshu. One quick question about the image thing. You said removing the ID part from the code — can you elaborate on that please?
I’ve only used the upload/browse all feature for this one image, so it’ll be easy enough to re-upload it to the other posts, but if I understand correctly, doesn’t that mean that the image in question is going to show up in the browse all box for each instance I’ve used it?
Are you using the damned wysiwyg thing? (otherwise you would see the code that is generated when putting the image in the post 😉
Oh I see what you’re talking about now. Yes, it’s there and will be removed. I thought you were referring to code in one of the the WP files. 🙂
Okay, I’ve done some work and finally got it to validate. Still have some questions though.
I changed my theme to mandigo and that drastically reduced my errors. I also deactivated my widgets and am currently using the standard sidebar.
It’s when I add some javascript for “MyBlogLog” that causes my blog to not validate. I’ve kept it in my sidebar for now in case it needs to be referred to, so my blog currently does NOT validate for that reason.
I’ve read here and in other documentation that javascript doesn’t play well in WP, or with PHP to be more accurate, but there is a workaround: http://codex.wordpress.org/Using_Javascript
However, I’m not quite clear on how to implement the solution described on that page. The example on the link above refers to emailpage.js. I don’t have a file; rather I’m inserting code to call the file that resides over at MyBlogLog. Is there still a way I can implement the solution by using the header and other code described in that example?
I’ve also included a table of buttons at the bottom of the sidebar. To add space I’ve been using the break tags. For reasons I don’t understand when I try to validate with that code in there, I get an error saying that it’s not allowed in that context. Why?
Breaks are not allowed in lists.
