WordPress.org

Ready to get started?Download WordPress

Forums

Facebook
HTML code shown on Facebook post (10 posts)

  1. Vic
    Member
    Posted 2 years ago #

    The summary line between the Title and the Article is showing <p> and </p> on my Facebook page post. How do I get rid of that or the entire summary section all together? Thank you!

    See snip:
    http://www.viclouis.com/wp-content/uploads/2012/08/Capture.png

    http://wordpress.org/extend/plugins/facebook/

  2. nalonsospc
    Member
    Posted 2 years ago #

    I am having this problem as well. When I enter a summary it shows <p> tags.

  3. Andrew.Bloom
    Member
    Posted 2 years ago #

    I think they have fixed this is the GitHub developer version...

    Get it at: https://github.com/facebook/wordpress/

  4. nalonsospc
    Member
    Posted 2 years ago #

    I'm on VIP so this isn't an option for me.

  5. lorielue
    Member
    Posted 2 years ago #

    I just downloaded this plugin, i am having the same issue.

  6. mverta
    Member
    Posted 2 years ago #

    Same issue!

  7. semfreak
    Member
    Posted 2 years ago #

    Correct Andrew, This has been fixed in 1.3. You can download the zip here: https://github.com/facebook/wordpress/ it has not yet been released into the WordPress plugin database.
    -Jason

  8. wtwp
    Member
    Posted 2 years ago #

    I'm having same problem as well as this: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.whattowearpost.com%2Fcoco-noir-new-fragrance-from-chanel%2F.

    It also shows this on my blog: Warning: http://www.whattowearpost.com/coco-noir-new-fragrance-from-chanel/ is unreachable

    How can I resolve this ASAP?

    Thanks in advance.

  9. Corineb
    Member
    Posted 2 years ago #

    Having the same problem. When will the solution be released into the WordPress plugin database.

    I am not a programmer..... just using wordpress and handy plugins like yours.....

    So I don't know what VIP or GitHub is.......

  10. rslindell
    Member
    Posted 2 years ago #

    Per @semfreak My understanding is that we need to wait for 1.0.3 to be available, which should have addressed this issue.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic