Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Chuck Reynolds

    (@ryno267)

    According to your source you’re not using this plugin.
    Hope you got your issue handled though.

    Thread Starter kiwieart

    (@kiwiearthmothercom)

    Hi Chuck,

    I was using it, but had to reset defaults, because it caused problems. Any pointers?

    Plugin Author Chuck Reynolds

    (@ryno267)

    without a specific definition of “it caused problems” I’m afraid I don’t know what exactly to help you with or where to look for said problems.

    Thread Starter kiwieart

    (@kiwiearthmothercom)

    The facebook debug page says
    Warning
    Error parsing input URL, no data was cached, or no data was scraped.

    Plugin Author Chuck Reynolds

    (@ryno267)

    Again I can’t test anything as you’re not using the plugin but what the debuger says now is fine, but with warnings – see: https://i.imgur.com/oL31IFu.png
    And a single post for reference: https://i.imgur.com/w0CyMj5.png
    Same thing… too small of image or none provided – even now w/ the other plugin being used.

    Re: “Error parsing input URL”… that’s typically a server problem but as far as I can tell at this point – you’re not getting that warning from FB anymore. You just need bigger images in your posts and then you should be fine going forward.

    Thread Starter kiwieart

    (@kiwiearthmothercom)

    I applied your plugin and loaded up a large image (I keep doing that but for some reason I still get the same issue about image size – it’s 400 pxl x 600 px – but still have the error parsing message again? And I have the error parsing message:
    Error parsing input URL, no data was cached, or no data was scraped.
    When shared, this is what will be included
    https://www.kiwiwearthmother.com
    https://www.kiwiwearthmother.com

    Plugin Author Chuck Reynolds

    (@ryno267)

    Okay. You definitely have a random issue but your problem is not my plugin or anything with WordPress (probably)… you have:
    1. a DNS routing problem on www.
    2. a server problem
    3. possibly an .htaccess redirect problem
    4. something with an https certificate isn’t configured right either (using mxtoolbox.com to test)

    https://www.kiwiearthmother.com (note the www) initially broke when trying to load. It later loaded okay. https://kiwiearthmother.com loads fine.

    I’d talk to your host and/or a developer and look at your host error_log’s. See if there’s anything in there that can shed some light on what’s going on… If it’s a DNS problem then you need to either talk to your host or your registrar (where you bought the domain).

    As far as the image. This is the one being pulled for your homepage: https://kiwiearthmother.com/wp-content/uploads/2015/03/mother-earth3-320×228.jpg
    It is too small for FB as per their rules… so it’s using this one instead https://kiwiearthmother.com/wp-content/uploads/2015/03/Profile-picture3.jpg

    For the home page if you set a fallback image, that’s big enough for FB, in WPFBOGP settings, then FB will use that image for the homepage.
    Single posts will look first for a featured image, and then go to images it can pull out of the content and always fallback to whatever the fallback image is in settings.
    This is all described in the plugin description but FYI.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘The 'og:image' property should be explicitly provided,’ is closed to new replies.