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.

Replies

6
  1. Andrew Misplon Staff 11 years, 29 days ago

    Hi Karim

    Sorry to hear about the hassle. Can you please explain what you mean by CSS errors?

  2. Karim Ellmann 11 years, 29 days ago

    Sure,

    I use the CSS validation service http://jigsaw.w3.org/css-validator/ to validate my site. I receive a lot warnings and errors if i go trought my site with this tool. Even if it is a completly “new” setup.

  3. Andrew Misplon Staff 11 years, 28 days ago

    Thanks for bringing this to our attention. The majority look like they’re being generated by Page Builder. If you’re interested, here is what a parse error is about:

    http://stackoverflow.com/questions/14111733/what-is-a-parse-error-and-how-do-i-fix-it

    I’ll create a bug report now. The team will address as soon as they’re able.

  4. Karim Ellmann 11 years, 20 days ago

    Thank you, sorry for the late answer, I had some stressfull days. To me it looks as well, like it is from PageBuilder

    Anything new from the bug report so far?

    Greetings

  5. Andrew Misplon Staff 11 years, 17 days ago

    That’s right, it’s being produced by Page Builder and or the Widgets Bundle plugin. Unfortunately no steps have yet been taken. The issue has been logged though, we’ll take a look as soon as possible.

  6. Andrew Misplon Staff 11 years, 17 days ago

    The guys were able to take another look now. The majority of the CSS errors seen seem to related to CSS3 compatibility code. That CSS will be progressively removed as we slowly, over time, stop supporting older browsers. But for now it needs to stay to help out older browsers. Hope that clears things up a little.

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