Well, all I can say is that the upgrades are coming with both advantages and disadvantages.

This is mainly useful for the author because now many audience from outside Triond will be surely interested in leaving a comment atleast for the sake of a link.

The disadvantage with this is that it is based on Wordpress solution and becomes similar to writinghood, bizcovering (it already became). They now and then give problems while commenting..

This should be FIXED..

error has to do with an anchor not properly closed thus, throwing error later on in the page. That is why parts of the content ‘overlap’ on-load. -Poor coding (well, error-coding at least)

Even then, the sites are written with a proprietary lean, -they favor InternetExploder and not any ‘compliant’ browser that adhere to World Wide Web Consortium suggestions. IE is a very bad browser despite the fact that it shows you what it thinks you wanted to see. That is the problem. A compliant browser shows you what is written..

Errors tend to look like this:
line 245 column 55 – Warning: missing before
line 245 column 318 – Warning: discarding unexpected
line 311 column 99 – Warning: discarding unexpected
line 311 column 150 – Warning: discarding unexpected
line 311 column 158 – Warning: is not approved by W3C
line 375 column 6 – Warning: missing
line 648 column 30 – Warning: element not empty or not closed
line 868 column 94 – Warning: unescaped & or unknown entity “&website_channel_article_id”
line 868 column 128 – Warning: unescaped & or unknown entity “&rnd”
line 868 column 1 – Warning: element not empty or not closed
line 656 column 4 – Warning: proprietary attribute “aria-required”
line 659 column 4 – Warning: proprietary attribute “aria-required”
Info: Doctype given is “-//W3C//DTD XHTML 1.0 Transitional//EN”
Info: Document content looks like HTML Proprietary

The ‘missing “” before “” ‘ is a page-busting event in it’s own right so, -no wonder the page renders strangely on Firefox.

great work team!