| Re: Valid CSS & HTML, Google and Urchin |
| by tjnemez on 2004/6/12 20:26:38 should be no issues getting css validated. |
| Re: Valid CSS & HTML, Google and Urchin |
| by digital01 on 2004/6/12 17:59:48 Does anyone know how to fix the PHPSESSID errors? I just tried to validate my site and it gave me several errors about this code: le="color: #000000"><?php <a href="/xoops/modules/news/index.php?storytopic=0&start=5&PHPSESSID=a6cc634e058ed82a76e365efc7b48134"> It doesnt agree with the & right before the PHPSESSID. You can see the results of the validation here Does anyone know how and where to go to fix this? Thanks. |
| Re: Valid CSS & HTML, Google and Urchin |
| by philroy on 2004/1/21 23:46:02 Sunsnapper...thanks for the comments, but as I mentioned, I'd already figured that out...my last remaining question is about Urchin. WarDick....Yes, Yes!, yes.....and, no, they may not care, but I like clean code. Any comments on Urchin anyone? Phil |
| Re: Valid CSS & HTML, Google and Urchin |
| by WarDick on 2004/1/21 22:02:19 Is it important to be validated? Is it something to be concerned about? Other than the display of pages on browsers? Do search engines really care? |
| Re: Valid CSS & HTML, Google and Urchin |
| by sunsnapper on 2004/1/21 21:46:51 As a test, you can set up a blank XOOPS site with no modules or blocks and try to validate it. I think you will find that it validates. As you bring each module on, items will validate or not based upon how well the templates for the module comply to xhtml coding standards. Also, note that some of the validation errors you get when you parse xoops.org are either & signs in the title of a message or validation errors in a particular Custom Block. The only errors that are raising my eyebrows are the PHPSESSID errors. Not sure if that will be fixed, or even if it is a legitimate error. Also, the theme you choose to use needs to be xhtml compliant (or compliant with whatever doctype is stated for the theme) or everything else is moot. |