Problem: Because of some changes with the w3c validator, Scrutiny is no longer receiving the expected response back from the public instance of the validator.
At present, it seems a little random which w3c server will deal with your request and therefore whether Scrutiny shows results. If you have this problem then the validation results will have empty warnings and errors columns:
Workaround: The Validator S.A.C. application is free to use, and installs a version of the w3c validator locally for you. It seems that the app contains a version of the validator that is compatible with Scrutiny. With a little setting up, Scrutiny can use this local instance of the validator and will show results once more.
This has always been better than using the public instance because there are no limits (the public instance had a limit of 100 pages in one batch) and you can go to Preferences > Validation and set your delay to zero, with impunity, thus validating all of your pages much faster:
The Validator S.A.C application can be found here:
http://habilis.net/validator-sac/
After downloading and running, follow the instructions below 'Advanced Topics' on that page.
To switch Scrutiny over to use your local instance of the validator, go to Preferences > Validation and click the text 'http://localhost/w3c-validator' and the address will be pasted into the location box.
(NB after making that switch, it may be necessary to quit and re-start Scrutiny)
No comments:
Post a Comment