VALIDATION/XHTML PROBLEMS: ClustrMaps HTML is causing my page to fail a W3C validation test, or my blog/service provider to modify or reject it. What can I do?
As of 21st September 2006 you will see, on your Admin page, several choices for your HTML code, including one that is XHTML1.1 compliant. All are much cleaner than the older code. You can just substitute the new code for you old code. Alternatively, if you want to stick with the old code, There are several issues that can be manually edited/fixed: 1. Neither the ‘border’ attribute nor the ‘onError’ code we use are XHTML 1.1 compliant; we’re working on a more elegant solution, but you could either live with it ‘as is’ for now (which is what we would recommend), or as a temporary ‘workaround’ you could manually edit out the offending code… in particular (a) just delete border=1 and (b) also delete everything from the beginning of onError right up to the final closing ‘>’ (but don’t delete that closing ‘>’ itself). Please note, however, that the onError code serves an extremely useful ‘failsafe’ purpose: in the very rare and unlikely event that our server goes down, you’ll just get a ‘b
As of 21st September 2006 you will see, on your Admin page, several choices for your HTML code, including one that is XHTML1.1 compliant. All are much cleaner than the older code. You can just substitute the new code for you old code. Alternatively, if you want to stick with the old code, There are several issues that can be manually edited/fixed: 1. Neither the ‘border’ attribute nor the ‘onError’ code we use are XHTML 1.1 compliant; we’re working on a more elegant solution, but you could either live with it ‘as is’ for now (which is what we would recommend), or as a temporary ‘workaround’ you could manually edit out the offending code… in particular (a) just delete border=1 and (b) also delete everything from the beginning of onError right up to the final closing ‘>’ (but don’t delete that closing ‘>’ itself). Please note, however, that the onError code serves an extremely useful ‘failsafe’ purpose: in the very rare and unlikely event that our server goes down, you’ll just get a ‘b
