W3C errors – meta tag

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi @gkalfakakou,

    Sorry, but this is already out of our support scope.

    I checked the results of your W3C Validator. I can see that the warnings linked to our plugin are only regarding the type attribute included in calling the scripts. See – https://share.getcloudapp.com/Kou1xyO0.

    Your Theme calls the scripts this way by default. So, we don’t have control over this.

    Could you try reaching out to the developers of your theme? Ask if this is something they can resolve.

    Let me know if they’ll need our help in handling this.

    Regards,
    Kenneth

    Thread Starter gkalfakakou

    (@gkalfakakou)

    `Hello Kenneth,
    Thank you for your quick response.
    It’s not the warnings for the W3C that I care about, it’s the 2 errors.
    I have found the code that creates the meta tag (woocommerce-google-adwords-conversion-tracking-tag/classes/pixels/trait-product.php, line 246), it creates an input element with type=hidden if it’s in the body, which is correct. But it also creates a meta element with a type=hidden when in the head. The meta element, as far as I know, doesn’t have a type.
    Could you please help me to find a way to correct this without me changing any core plugin files because it won’t be updatable anymore?
    Thank you in advance,

    Hi @gkalfakakou,

    I asked our developer about this. He admitted that the Pixel Manager doesn’t generate a W3C valid code for some objects. He said that it’s a workaround for tracking some products.

    It works without issues on all browsers. So, you can just treat this as a warning and ignore it in the meantime.

    In the earlier versions of the Pixel Manager, it’s important to load product information as soon as possible. On some pages, it’s not possible to do that within the <body> for some reason.

    So our developer moved it up into the header. Unfortunately, it generates a non-W3C compliant code. But again, it works flawlessly in all browsers.

    We may fix this in the future, but we can’t give an exact date yet for when we can release it.

    I hope that helps.

    Let me know if you have other concerns.

    Regards,
    Kenneth

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘W3C errors – meta tag’ is closed to new replies.

Tags