Navigation
Archive / A problem with facebook sharing: og:description not working
This is archived content. Visit our new forum.

Tagged: 

  • Author
    Posts
  • February 2, 2017 at 11:35 am #1355468

    David
    Participant

    Hi guys

    Im having a problem with the social sharing. Im using yoast and I have Enable Open Graph turned on in the Customizing. When the page is shared its not displaying the og:description. I have tried to work around this but I keep hitting a brick wall.

    The url in this case is http://halogaia.com/year-calendar/self-discovery-paradise-27-april-1-may-2017/
    But it applies to all the urls.

    Thanks a stack
    David

    February 2, 2017 at 1:35 pm #1355596

    Darshana
    Moderator

    Hi there,

    You can turn off your Opengraph at Appearance > Customizer > Social > Opengraph.

    Once you’re done, please clear/purge your caches if you have a caching plugin installed. Then go to facebook debug tool ( https://developers.facebook.com/tools/debug/ ) and add your site’s url that having opengraph issue. Then click fetch new information (you will have to repeat multiple times until it clears its own facebook cache).

    Hope this helps.

    February 3, 2017 at 2:46 am #1356452

    David
    Participant

    Hi Darshana

    Thanks for getting back to me. The problem I still getting errors that I cannot fix. I have scraped it alot of times and Im getting no where.

    Now the descrption is saying “save…” ????? I have no idea how to sort this out.

    Im getting:
    Extraneous Property
    Objects of this type do not allow properties named ‘article:publisher’.
    Extraneous Property
    Objects of this type do not allow properties named ‘DC.date.issued’.
    Share App ID Missing
    The ‘fb:app_id’ property should be explicitly provided, Specify the app ID so that stories shared to Facebook will be properly attributed to the app. Alternatively, app_id can be set in url when open the share dialog.
    Parser Mismatched Metadata
    The parser’s result for this metadata did not match the input metadata. Likely, this was caused by the data being ordered in an unexpected way, multiple values being given for a property only expecting a single value, or property values for a given property being mismatched. Here are the input properties that were not seen in the parsed result: ‘og:locale:locale, og:type, og:title, og:description, article:publisher, og:image:url, DC.date.issued, og:site_name’

    Thanks again for your help

    February 3, 2017 at 2:54 am #1356458

    David
    Participant

    Sorry I think its working…..my bad, the page didnt load properly my side….it seems to be working!!!

    YOU A STAR THANKS A MILL!!!!!!! 🙂

    February 3, 2017 at 3:09 am #1356470

    Lely
    Moderator

    Glad this is now sorted out David!

    Thank you for updating us.

    Cheers!

  • Author
    Posts