Thread Starter
junem0
(@junem0)
Thanks for that link. have quite some errors but about some I have no clue whatit’s about or where even to find the specified lines.A few here:
Line 82, Column 54: document type does not allow element “p” here
…'<p class=”show_onwall” id=”wallops”><input type=”hidden” name=”item_number”
Line 83, Column 46: ID “wallops” already defined
…lOps2 = ‘<p class=”show_onwall” id=”wallops”><label for=”show_onwall”>Show on
Line 147, Column 120: reference not terminated by REFC delimiter
…your voice in 7 easy steps   Next Post: <a href=”http://www.music.jun
Line 152, Column 43: end tag for “hr” omitted, but OMITTAG NO was specified
<hr width=”100%” color=”#000000″ size=”1″>………..
Line 156, Column 3: document type does not allow element “p” here; missing one of “object”, “applet”, “map”, “iframe”, “button”, “ins”, “del” start-tag
<p>A lot of people happen to speak too low or too high. Most of these people are
–i have a lot of these errors but my posts don’t have the “<p>” I don’t know why it’s been read while it isn’t there.
The color thing on the titles in the sidebar got solved but not the comment issue. Still looking.
The multiple id="wallops" is theme-related. Named ids should only be used once on a page but the theme obviously hasn’t accounted for more than one usage of a given display element.
&nbsp is correctly entered as . Likewise <hr> should be <hr />. Perhaps you copied in someone else’s poor markup?
Your posts do have <p> tags. WordPress adds them whenever you leave a completely blank line between 2 blocks of content. You can also add them by pasting content in from elsewhere – which is where you can hit trouble. My guess is that you have introduced some bad markup in posts within the vocals category and it is this invalid markup that is causing your problem. The only way to solve it is to track down the bad markup and fix it.
Thread Starter
junem0
(@junem0)
I didn’t know this: Likewise <hr> should be <hr />. I got it from this site: http://www.web-source.net/html_codes_chart.htm
“My guess is that you have introduced some bad markup in posts within the vocals category and it is this invalid markup that is causing your problem. The only way to solve it is to track down the bad markup and fix it. “
-you mean causing that the comment info after submit is not cleared?
http://www.web-source.net/html_codes_chart.htm
That’s referencing HTML. Your blog is using XHTML. Try http://www.w3schools.com/xhtml/
you mean causing that the comment info after submit is not cleared
No – the inconsistent text colors. Once most of the errors have been sorted, it might be possible to see if there is a comment form issue but, last time I looked, there were simply too many validation errors in the way – so to speak.
Thread Starter
junem0
(@junem0)
OMG I can start over again. I used html in everything I posted,templates…
Thread Starter
junem0
(@junem0)
Is it really xhtml because the post edit window has an html tab?
I changed several posts using <hr /> I have 10 more errors now.
Is it really xhtml because the post edit window has an html tab?
Yes. The post editor has nothing to do with whether your blog’s Doctype is HTML or XHTML. That has to do with your theme.
Thread Starter
junem0
(@junem0)
So where should i use xtml, in the posts and the .php files or only in the posts. I’ve used html in both and got no errors using a different validation link so why should i switch to xhtml?
Also how can the markup of a line interfere with the fact that the input submitted doesn’t get cleared. There is apparently something not defined in the comment.php
So where should i use xtml, in the posts and the .php files or only in the posts.
In all posts and php files/templates.
I’ve used html in both and got no errors using a different validation link so why should i switch to xhtml?
What validator was that? The link I gave you was to the W3C validator which, for all practical intent and purposes, can be considered to the THE definitive (X)HTML validator.
Also how can the markup of a line interfere with the fact that the input submitted doesn’t get cleared.
Invalid markup can create all kinds of unexpected problems, so it’s always a good idea to start any troubleshooting by validating the pages(s) first – them move onto other possible causes.
Thread Starter
junem0
(@junem0)
Once most of the errors have been sorted, it might be possible to see if there is a comment form issue but, last time I looked, there were simply too many validation errors in the way – so to speak.
The markup has nothing to do with clearing the form so instead of needlessly holding me up just let me know that you can’t help me so i can move on and look elsewhere.
Thanks
(@junem0)
15 years ago
Hi fellas.
Follow the link and scroll down towards the comments. see what’s going on. I input the info more than a week ago. It just won’t disappear.
http://www.music.junemoris.com/vocals/395/
Also take a look at the titles in the sidebar. click on several categories. The color should be white but in the vocals cat suddenly they are orange. In the guitar cat they’re white but if you click to add a comment they suddenly turn blue. Above the comment input box the amount of comments is also in blue.That’s how I set it up to appear in the comments template.However it mysteriously also changes the oclor of the title in the sidebar…?
Any thoughts or suggestions?