This is the best answer http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.prosoftwarez.com%2Fsystem_performance.php%2Fsystem-performance%2Fregistry-cleaner%23feedbacks

BTW you can grab a valid starrating plugin from [url=http://ru.b2evo.net/bstat/stat.php?plugin=starrate]here[/url].

sam2kb wrote:

This is the best answer http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.prosoftwarez.com%2Fsystem_performance.php%2Fsystem-performance%2Fregistry-cleaner%23feedbacks

BTW you can grab a valid starrating plugin from [url=http://ru.b2evo.net/bstat/stat.php?plugin=starrate]here[/url].

thank you sam2kb, it is not about the file archive, and about those validation errors, i d like to eliminate them too, however it doesn't point to the exact place of error, unlike the web developer toolbar, click does not take you directly to error line, anyhow will see, cheers

If you check the "show source" box then click "revalidate" validator.org will show you what it sees as the page source and link the lines with errors to the correct point in the page source. Kinda groovy!

EdB wrote:

If you check the "show source" box then click "revalidate" validator.org will show you what it sees as the page source and link the lines with errors to the correct point in the page source. Kinda groovy!

thanks Ed, (: but it still does not point to the exact file which includes that lines, sometimes even core files or installed plugins contain error lines,

btw, i have discovered a property of ".post postpublished" causes starrating to mess, i ve looked for it but couldn't find which property does it or in which file this class defined

Very true! What I've sometimes done is added a <!-- FilePath/FileName Comment --> to each of the files in skins/myskin/ and skins/ to help me track down where something has gone wrong. For stuff that seems to be in the core it's not that easy, but a bit of detective work helps narrow it down. Agent Ransack is a good tool for that if you can find something neato in the page source to look for. Like a table with a class for example. Or better still one of the random <!-- comments --> that show up every now and then.

btw, just to mention, dont know which property of ".post .postpublished" caused this, but instead of trying to digg it out; i just got rid of it (: thanks for your responses

I gave the link to archive where I fixed character "<" is the first character of a delimiter and there is no attribute "onClick" errors.

It doesn't solve your problem, but you will get rid of some validation errors.

sam2kb wrote:

I gave the link to archive where I fixed character "<" is the first character of a delimiter and there is no attribute "onClick" errors.

It doesn't solve your problem, but you will get rid of some validation errors.

thanks sam2kb, actually validation is very important, for example, i have used an extra closure tag </div> in the post loop in the single.main.php and every post one after another was going one div up like 1st post "page-wrapper-content-post published" 2nd post "page-wrapper-post published" and so on .. ((:

i wouldn't lose anything if i replace the complete plugin folder with yours, would i

edit: geeez..! i got rid of "post published" div in order starrating not to be messed, but as it's not in the post loop now, it gets another post ID unrelated with the post.. if the post is div30 rating also should be div30 right ?

You wouldn't loose nothing and you will be able to translate it, if you want so. You can replace only plugin php file and add locales folder, nothing else is changed.