“Sharing Debugger” errors caused by W3TC

  • Resolved lemming2030

    (@lemming2030)


    4 years, 8 months ago

    Hello,

    social meta settings are managed on my site via “The SEO Framework” plugin, however, as it turns out, the issue I’m experiencing is related to W3 Total Cache.

    I noticed that the social share image is not present, when I want to share my home page URL on Facebook (it works fine for blog posts and pages, tho).

    When checking the URL on sharing debuggers from Facebook, Pinterest, Twitter and LinkedIn, here’s what I get:

    Facebook:
    Curl Error: 61 (BAD_CONTENT_ENCODING)
    Inferred Property: The ‘og:image’ property should be explicitly provided, even if a value can be inferred from other tags.
    Missing Properties: The following required properties are missing: og:url, og:type, og:title, og:image, og:description, fb:app_id

    Pinterest:
    “The data we scraped from your site could not be validated. Please make sure all required tags are present and you aren’t serving different pages depending on different user agents.”
    There’s a red exclamation mark for “Rich Pins enabled”

    Twitter:
    Everything works fine.

    LinkedIn:
    Everything works fine.

    If I disable the W3TC plugin, Facebook sharing works OK, with no issues.

    My host is WPX and I use their recommended settings for W3TC.

    I’d appreciate your help with this.

    Thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @lemming2030

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Can you please share your website URL and if you are using any other caching/minify solution?
    Thank you!

    Thread Starter lemming2030

    (@lemming2030)

    Hello @vmarko,

    thank you for your prompt reply.

    Please find the link here: https://docs.google.com/document/d/1l9brHPY-r85f7cvclqxcEq8S0rWNn6rDWxxa-MkM9lM/edit?usp=sharing

    I’m not using any other caching or minifying solution.

    Thanks.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @lemming2030

    Thank you. Is minify enabled in W3 Total cache?
    Also, I can see x-turbo-charged-by: LiteSpeed
    Also, are you using Cloudflare by any chance?
    Thank you!

    Thread Starter lemming2030

    (@lemming2030)

    Hello @vmarko,

    here are my Minify settings: https://www.dropbox.com/s/vmwa0a6chq95nva/w3tc.pdf?dl=0 (these are all defaults by WPX hosting).

    As for x-turbo-charged-by: LiteSpeed, I’m not sure what this means and if I can control it or not. :-/

    I’m not using Cloudflare, but WPX has its own CDN.

    I also need to point out that sharing my home page URL on FB worked in the past, but I’m not sure when it stopped working and if this was maybe due to W3TC, WordPress or any other updates.

    Thank you.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @lemming2030
    When you say it worked in the past, have you been using W3 Total cache then?
    Have you made any changes or updates since it was the last working?
    Since the BAD_CONTENT_ENCODING is the error, Potentially double gzip compression is in your env.
    Can you please disable the Gzip COmpression in Performance>Browser Cache and see if the issue persists?
    Thank you!

    Thread Starter lemming2030

    (@lemming2030)

    Hello @vmarko,

    that solved the problem, thank you. ??

    When you say it worked in the past, have you been using W3 Total cache then?
    Have you made any changes or updates since it was the last working?

    Yes, W3TC comes as standard with WPX hosting, so I’ve used it since day 1. I’m now using WPX for 6 months or so and there have been a few W3TC updates, but I don’t know when the sharing got broken. Other than that, I wasn’t touching the W3TC settings, because WPX has it pre-configured for optimal performance. They also haven’t changed their default settings since 2018.

    Do you recommend that I leave Gzip disabled? Or should I just leave it enabled?

    Thanks again.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @lemming2030

    Glad to know the issue is resolved!
    As I stated in the previous post, There is a double Gzip compression. SO you already have it enabled so you do not need to enable it in W3 Total Cache. Or you may want to find where gzip is enabled and remove it so you can use W3 Total Cache gzip.
    Either way, it’s working.
    We would really appreciate it if you could take a minute and post a review?here. This will help us to continue offering a top-notch product to users.
    Thanks!

    Thread Starter lemming2030

    (@lemming2030)

    Hello @vmarko,

    all right, thank you! I’ll leave it disabled and notify my host about this issue.

    I left a review. Thanks again!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘“Sharing Debugger” errors caused by W3TC’ is closed to new replies.