Bug CSS warnings: Chris Pederick's Web Developer 1.1.9

Hello Rockbox,

No, I do not get the 500 error message at all. I have checked around 10 times and didn't get it once.

As for the css warnings you get on your page , they are nothing to worry about. If you really need to fix those errors you will have to look for the errors in the css file indicated and figure out a way for the developer's tool to not flag them as errors.

You get a fatal error when you click any Kunena menu tab on that site. Try it.

There's something really wrong here! :dry:

I think we really need to see the Kunena configuration report in this case.

what browser are you using? I don't get any errors

We spent about half-an-hour discussing this issue. As it transpired, I kept getting these fatal errors when I browsed your site from one PC but I didn't get them on another one. I think it must have been something in my local browser cache. It doesn't matter and I retract my earlier remarks.

The essential question in this case is how do these errors manifest themselves as far as a normal visitor to your website is concerned? I believe that the answer is that these warning messages will not, in any way, detract from the end-user experience and I think that's what should always be foremost in your mind.

I visited your site today, using Firefox, and I saw nothing that detracted from the "user experience".

Many design tools will flag Javascript or CSS errors and, in most cases, this is fairly "normal". I have not seen too many websites that are immune from these warning messages ... even Microsoft's site! There is such a thing as over-analysis and the Law of Diminishing Returns. If your site was my site, I wouldn't worry about these warnings unless, as I wrote above, they detract from or adversely impact the "end-user experience".

Do these warnings, in your opinion, impact in any way on the end-user experience?

Thanks Sozz your help is appreciated and I understand what you're saying but I like the make things the best I can and the css is generally not a biggy to fix up, I thought it may be a matter of choosing the joomla css over Kunena, just a checkbox or something.
With millions of site aiming to get to first page of google the site with the most relevant info and purest coding comes first in my experience, also I haven't had these css warnings with past versions just the latest one on the latest Joomla, kunena has always been very pure sweet coding hence why I've gone with it!
So I'd still like to fix it as I'd like to use it as a template on a few other sites.
Cheers Sozz!

As you say, it all depends on what is the main purpose for which you have created your site.

For some people - for most people who use this forum - the main reason they have created their sites is because they want a reliable, durable, robust product that grows to meet their needs and that facilitates web-based discussions among their members. For some people, their main concern is to ensure that their website ranks foremost on Google. Occasionally these two objectives may be incompatible with one another, that is a site can be ranked foremost by Google irrespectively of whether the site is actually enjoyed by a community to discuss that community's interests.

This website ( www.kunena.org ) ranks fairly well in the search engine stakes. The forum here is actively used and enjoyed by its members. It may be a fact that this website (like thousands of sites on the net) would show that some CSS or Javascript issues by employing tools like Chris Pederick's Web Developer . And I have to say - with no offence to you or to the developer of Web Developer - so what? I'm not trying to trivialise or be dismissive here, I'm merely trying to put things into fair and proper perspective.

I haven't used Web Developer myself. I don't know if members of the Kunena development team have used Web Developer - I can't speak for them - but maybe someone should look into this. Have you, Rockbox, used this tool on www.kunena.org and what findings have you discovered about this site? Do those findings reflect the same things as you have at your site?

If you discover different issues at your site (different from what you see here at www.kunena.org ) then you probably should ask what are the sources of those differences? This site uses the same basic K 1.7.2 software with the Kunena Blue Eagle template that is created when people install the installation kit from the download page.

Rockbox wrote:

With millions of site aiming to get to first page of Google the site with the most relevant info and purest coding comes first in my experience.

Interesting philosophy. What comes foremost for me is a site that is used and enjoyed by those who are interested in the activities of the site no matter how they discovered it; Google is only one part of that process of discovery.

Yes, some search engines do penalise developers who have sloppy code. Sometimes the penalties are minor and sometimes they're not and sometimes it's worthwhile cleaning up the code to the best that you can. But, at some point along the path, the Law of Diminishing Returns kicks in and that's also something you should keep in mind, too.

A few things to think about here and, no doubt, keep us all entertained for a long while to come.