• Hi There!

    I love the plugin and I’m just using one marker on one page here: http://66.147.244.225/~jhoffma1/contact/

    But it is bringing up these errors in the W3C validator. Seems to be inserting a random </p> tag on the first error. I’m fairly new to wordpress, can I go in and fix these errors? I’m also using the latest version of the plugin. Thanks for the help!

    Line 155, Column 16: No p element in scope but a p end tag seen.

    </div></div></p>

    Error Line 209, Column 194: Element link is missing required attribute property.

    …-maps-marker/leaflet-dist/leaflet.css?ver=3.5.3′ type=’text/css’ media=’all’ />

    Attributes for element link:
    Global attributes
    href
    crossorigin
    rel
    media
    hreflang
    type
    sizes
    Also, the title attribute has special semantics on this element.

    Error Line 210, Column 23: Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.)

    <style type=’text/css’>

    Contexts in which element style may be used:
    If the scoped attribute is absent: where metadata content is expected.
    If the scoped attribute is absent: in a noscript element that is a child of a head element.
    If the scoped attribute is present: where flow content is expected, but before any other flow content other than inter-element whitespace, and not as the child of an element whose content model is transparent.
    Content model for element body:
    Flow content.

    http://wordpress.org/extend/plugins/leaflet-maps-marker/

Viewing 1 replies (of 1 total)
  • Hi Rainymountain,
    I wouldnt bother about these kind of validation errors too much – I checked my reference installation (http://current.mapsmarker.com/2013/02/19/jquery-and-leaflet-0-4-5/) against W3C validator and there were no issues related to my plugin. It is probably caused by your theme. Error in line 155 might be in the post you added the shortcode to – see in HTML mode when editing the post if there is an opening p-tag too and not just a closing one. The error on line 209 couldnt be reproduced on my site (again: theme issue? you could try to activate the default theme twentytwelve to check if this is the case).
    But as said before: I wouldnt spend too much time on being 100% compliant with W3C…
    best,
    Robert

Viewing 1 replies (of 1 total)
  • The topic ‘Plugin bringing up errors in the validator’ is closed to new replies.