Conflict with SG Optimiser

  • Resolved Keirwatson

    (@keirwatson)


    4 years, 5 months ago

    I have been trialing GB with my GP blog and really like the new functionality it provides, especially for designing full-width posts.

    However, after successfully publishing my first GB post, I decided a few days later to add page-breaks and add some additional content using GB.

    The new content displayed perfectly in the editor and preview, but when it went live all of the styling was stripped out of the new GB parts.

    After a lot of head scratching I traced the conflict to SG Optimiser plugin, and had to turn off “Remove Query Strings From Static Resources
    Removes version query strings from your static resources improving the caching of those resources.”

    I don’t understand why that works, why it only affects new edits and did not arise for the original post, or if there is a work-around.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Tom

    (@edge22)

    Hi there,

    Query strings are actually very important in most cases, including GenerateBlocks. They tell the browser whether a static resource has been changed or not so the browser can refresh the file (release its cache).

    Every time you update your page, GenerateBlocks will re-build its stylesheet to include any changes that may have taken place. At which point, the query string is updated so the browser will fetch the new version of the file.

    Without that query string, the browser will continue to use the old version of the file.

    If you must remove query strings, you can tell GenerateBlocks to load the CSS inline in Settings > GenerateBlocks. That way it won’t generate a file and won’t rely on query strings.

    Hope this helps!

Viewing 1 replies (of 1 total)
  • The topic ‘Conflict with SG Optimiser’ is closed to new replies.