This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

w3c error validation

9 years ago · Last reply by Andrew Misplon 9 years ago

http://prntscr.com/c8qj4j

Here is the screenshot of validation a website with site origin page builder, hope to fix it. I know for default that style tags cannot be inside the body tag instead inside the head tag, but this plugin put this styles inside body tag that made this error in validation. Can’t find a way to change it from wp_footer to wp_head to fix this.

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

9
  1. Andrew Misplon Staff 9 years, 6 months ago

    Hi Dexter
    Do you have a public URL where we can take a look at what’s going on? If you need to keep this URL private from other users, just select “Private Reply” on the bottom right of the comment box.

  2. Dexter John Chua Private 9 years, 6 months ago

    This is a private message.

  3. Dexter John Chua Private 9 years, 6 months ago

    This is a private message.

  4. Dexter John Chua 9 years, 6 months ago

    Good day,

    I don’t really know whats happening, if I post a comment with the URL, i can’t see the reply i made with the URL.

  5. Dexter John Chua Private 9 years, 6 months ago

    This is a private message.

  6. Dexter John Chua Private 9 years, 6 months ago

    This is a private message.

  7. Andrew Misplon Staff 9 years, 6 months ago

    Thanks for sharing. The footer style block only gets used as a fallback, when content is rendered after the head. To style it, Page Builder has to insert the style block in the last place it can. There isn’t any fix available, what you’re seeing is already a fix. It could be a plugin conflict so you might try testing the site with all plugins not authored by SiteOrigin disabled and see if the style block moves.

  8. Dexter John Chua 9 years, 6 months ago

    Already tried disabling all plugins except PageBuilder( SiteOrigin ) but still render that way, so that means I should just exclude this from error fixing.

    Thanks for response

  9. Andrew Misplon Staff 9 years, 6 months ago

    The final check might to switch to a default theme like Twenty Sixteen with all non-SiteOrigin plugins disabled and see if the behaviour continues. Or yes, you could ignore this one and move on. Sorry I don’t have specifics on why this fallback has been used.

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread