4 replies to this topic

[rolf_huijbrechtshotmailcom]

Hi, I have added Custom CSS styles in the stationpro admin interface and they work fine. But a file called custom.css is referenced in the stationpro stylesheet file and apparently that file does not exist. http://jigsaw.w3.org...rning=1&lang=en Please advise how to resolve this. Thanks!

[bryan-hadaway]

If you're trying to reach it through the editor and can't find it... it's because it's not reachable there, as well as a number of other files.

I understand the importance of validation, but with WordPress you'll likely end up in a revolving door of never ending validation problems.

There are a number of things that are considered "errors" by W3C, but that doesn't ACTUALLY mean that they're errors that can or will mess anything up. A lot of it has to do with CSS3 not being popular enough yet.

I recommend checking your site via this link and going from there:

http://jigsaw.w3.org...er?profile=css3

To reach certain files like custom.css you need to locally and via FTP, manually go into:

wp-content/themes/stationpro

Thanks, Bryan

[rolf_huijbrechtshotmailcom]

Thanks for the info Brian. 1. I have run the CSS Validator again with the CSS3 profile, and the same error popped up: URI : http://www.infozine....3-2-4/style.css 33 File not found: http://www.infozine....css/custom.css: Not Found 2. I used FTP to check that file custom.css manually and indeed it does not exist in the stationpro folder. 3. I noticed that the Custom CSS styles are effectively written into the file custom.css in the previous V2.1.1 of StationPro, and that using StationPro V3.2.4 those styles are now injected in the webpage (which is okay as well). So what should I do next? The goal is to minimize the number of CSS "errors" on my website.

[bryan-hadaway]

http://jigsaw.w3.org...e/&profile=css3

That's the CSS validation page for your website.

There is nothing here to be alarmed by. Most of the problems are because of: -moz, -khtml and -webkit. These aren't technically errors. They're selectors for browsers like Mozilla Firefox for styling purposes.

The reason they are considered "errors" in W3C is because they are not universal standard compliant selectors recognized by most major browsers.

If you remove these you will basically lose rounded corners in your design, that about it.

custom.css is found in the /css/ folder within your theme folder. If it's not there, check in your local theme files and upload it if you find it.

Thanks, Bryan

[rolf_huijbrechtshotmailcom]

>custom.css is found in the /css/ folder within your theme folder. >If it's not there, check in your local theme files and upload it if >you find it. The file custom.css does not exist in the original stationpro zip file nor on my website. So I have created a dummy file custom.css in the /css folder and now it is okay of course. Thanks for your help.