Facebook Publish Error

Could you please include a link to the associated post on your site which raised this error?

I was posting that one : https://akuaturk.com/11/2012/panthalassa/dunya-denizlerinin-en-zararli-egzotik-istilaci-turleri/

I push the button publish, my post is published to my wordpress page. But not to the facebook page and gave me that error as a message in a yellow box (i suppose) just top of the your post publish clich here to view it alert of wordpress.

Oh right, i figure it out why it wasnt posting to page timeline. There is a section called “Facebook status on xxx timeline” in the writing area, if you do not put something in it, it does not publish and gives me that error. If you put something in it, it attachs what you put as a status message with the post you published.

In that case, i think there is something wrong with your code. Would you please check it out.

Hi all,

I have the same problem!

Failed posting to Ico Timeline. Error: {“message”: “(# 100) parameter description can not be more than 10 thousand characters.”, “Type”: “OAuthException”}

Using the WordPress SEO plugin with facebook, is that what is causing the problem?

I await a reply,

Thank you!

Hi,

For some obscure reason, while clean_description() function, located in open-graph-protocol.php is correctly accepting the default $trimmed = true parameter, the social-publisher.php located in /plugins/facebook/admin/social-publisher/ is passing false as parameter, enabling the full content to be activated as description in the feed object. To correct this, simply remove the false parameter on lines 340, 506 and 616 or specify true instead of false, both results are the same.

Hope it solves your problem ??

appcuarium’s fix doesn’t seem to work for me either.

tainkeh,

Please make sure you’re using the latest version of the plugin. The fix is pretty straight forward. The lines mentioned above must look like this:

$post_content = Facebook_Open_Graph_Protocol::clean_description( $post->post_content, true );

Well, it seems it worked, since our fix was included in the 1.3 update. Good job and thanks for this great plugin.

marking as resolved