Hi,

 

I've just currently designed a Joomla based site & when I run it through the validator it has errors where modules are inserted.

 

Is it something I am doing wrong or is this the case with Joomla based sites?

Why does it need to be validated? If it works in all browsers?

Why does it need to be validated? If it works in all browsers?

 

so true.

 

You could spend a few hours validating it all when you could be doing soemthing better with your time. If it works in all browsers thats the battle over really

Why does it need to be validated? If it works in all browsers?

 

Exactly. If it works then it works. Don't go trying to fix something that's not broken.

 

 

BUT....

It of course depends on the validation errors you are receiving, for example they may cause a problem in the long run or when older mark-up gets depreciated.

 

got a link

 

 

 

I understand where your all coming from but is this normal with a CMS based design?

like Mike said depends on what errors are being reported

I understand where your all coming from but is this normal with a CMS based design?

No.

 

Although one of the things that I hate most about Joomla is the plugins and extensions usually suffer from the most terrible HTML and have to be re-coded to make the pages validate.

 

Although it's sort of a fair point asking why validation matters if the site looks right in all browsers, I don't think it's a helpful way to work in the long run. Making sure all your HTML validates makes you a better coder, and means you make fewer mistakes as time goes by, and spend less time fixing errors in non compliant browsers.

 

Check your template for unclosed tags before you start digging into modules etc.

No.

 

Although one of the things that I hate most about Joomla is the plugins and extensions usually suffer from the most terrible HTML and have to be re-coded to make the pages validate.

 

Although it's sort of a fair point asking why validation matters if the site looks right in all browsers, I don't think it's a helpful way to work in the long run. Making sure all your HTML validates makes you a better coder, and means you make fewer mistakes as time goes by, and spend less time fixing errors in non compliant browsers.

 

Check your template for unclosed tags before you start digging into modules etc.

 

I understand where you are coming from with all this, but in the current time, in web design at the moment a bit shaken with all the different coding technologys and HTML 5 and CSS3 adding to the mix along with browsers like IE fighting back. Making it harder to validae and work in browsers?

He is likely talking about HTML validation which wouldn't take into account CSS. Also the W3C has a HTML5 validator so your point again is also mute.

 

Why does it need to be validated? If it works in all browsers?

 

Because it shows you know your craft and you know that you care about what you are doing. It's about taking pride in what you are doing. This is aside from alleviating potential display problems due to bad code.

 

Read this page: http://validator.w3.org/docs/why.html

 

There also reports that the browser can render valid pages quicker but I don't have anything to back that up, and could be nothing more than a myth or just plain false.

Edited December 22, 201015 yr by cibgraphics

He is likely talking about HTML validation which wouldn't take into account CSS. Also the W3C has a HTML5 validator so your point again is also mute.

Exactly. The diversity of document types out there shouldn't detract from making the best effort you can to create high quality code. If anything, it makes it more important. Same with CSS, you should write valid CSS, be it version 2 or 3. If you're using lots of CSS3, make sure your pages degrade nicely in unsupported browsers.

 

Choose the document type you're happiest working with, then learn how to code it well, and validate as you go. I'm still using xHTML strict, but no doubt I'll adopt HTML5 when older versions of IE go back to hell.

 

 

Because it shows you know your craft and you know that you care about what you are doing. It's about taking pride in what you are doing. This is aside from alleviating potential display problems due to bad code.

 

Creating great code doesn't mean Valid code. I always try to use Valid code but on some projects it is just not a possibility.

Creating great code doesn't mean Valid code. I always try to use Valid code but on some projects it is just not a possibility.

And if you're experienced and already working from a solid, workable code foundation, where you know what the possible future issues might be, there's nothing wrong with that.

 

But for those still learning, I think validation is very important.

And if you're experienced and already working from a solid, workable code foundation, where you know what the possible future issues might be, there's nothing wrong with that.

 

But for those still learning, I think validation is very important.

 

 

Fair point.