Support » Fixing WordPress » How to see coding errors? (Open tags)

  • I ran on my site ( and it came up with a passel of errors (26, actually), like “Line 77, Column 10: end tag for element “a” which is not open.”

    My assumption was that these were errors in the template, but when I search the template files, I can’t find them. I tried the posts themselves, but still can’t locate the errors. Not sure how to use the line and column IDs…counted from the top, but that’s unwieldy and I didn’t find anything. I did “show source” and pasted the whole thing into a doc in GoLive – the only errors I can find are 1482 BRs without a close tag in XHTML 1.0 transitional (which is what the validator used) – I think that’s a WordPress issue? In any case, those aren’t the error I’m seeing in the validator. Is there a plug-in or software that will look at the site the same way the validator does and show me where the errors are? Any ideas why I’m seeing one thing in GoLive and another in the online validator?

    Thanks in advance!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Select the Show Source option when you validate, and then you can click on the line number to be taken to that spot in your code. You can deduce which theme file, post, etc. contains the error by looking at the surrounding code and text. Code errors can be in posts, pages, widgets, theme files, and added by plugins.

    Also invest in an HTML editor such as EditPlus, HTML Kit or the like. Also, if you use the FireFox browser, grab the Web Developer Tools. You can view and edit CSS and HTML on the fly, and you can right-click on a web page, View Source and it will be shown color-coded, which makes it much easier to spot problems.

    “Show source” is what I did. What shows is info like ” Line 77, Column 10: end tag for element “a” which is not open
    I really can’t deduce anything – there’s nothing of the sort on the line numbers when they are indicated in GoLive. GoLive *is* an HTML editor; I’ll try out the Firefox tools. Perhaps their info will match.

    Last time I used Go Live was 6.0 (does that tell you how old I am?!), and I cannot remember if it color codes the code (there has to be a better way to say that, but I hope you know what I mean). Firefox Dev tools should get you going well enough. And once you start using them, you’ll find it hard to live without them. 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘How to see coding errors? (Open tags)’ is closed to new replies.