When I post:
a perfect title for emails… Why is there a topic anyways? It’s not an essay.
This is what I get in my Facebook page:
a perfect title for emails… Why is there a topic anyways? It’s not an essay.
When I post:
a perfect title for emails… Why is there a topic anyways? It’s not an essay.
This is what I get in my Facebook page:
a perfect title for emails… Why is there a topic anyways? It’s not an essay.
sorry for the wrong copy and paste. This is what I get in Facebook:
a perfect title for emails… Why is there a topic anyways? It’s not an essay.
hahaha!
actually I didn't forget to copy/past. Basically wordpress converts the texts so its somewhat incompatible with Facebook. There is "& # 8 2 3 0 ;" for "..." and " & # 8 2 1 7 ;" for " ' "
a perfect title for emails & # 8 2 3 0; Why is there a topic anyways? It & # 8 2 1 7 ; not an essay.
Can you post your support information
Is that in the title of the post?
I can't reproduce it with the current release...
these are my sites:
http://www.gransar.net
http://www.facebook.com/gransar
Can you please post your Wordbooker support information as I requested.
Also I see no posts from Wordbooker on your wall. So can you please provide screen shots showing the exact proble,.
As I've heard nothing and cannot reproduce this I'm marking it as resolved
Hey Steve. I have the same issue. It converts certain characters like apostrophe and the "&" symbol to the html code equivalent when posted to facebook.
Server Status
Wordbooker Release: 2.1.27
Wordbooker Code Base: 2.2.0 Beta 18 - Hangar 18, Area 51
Wordbooker ID: 254577506873
Wordbooker Schema: 5.6
WordPress: 3.5.1
Table prefix: BSW_
PHP: 5.2.17
PHP Memory Limit: 256M
PHP Memory Usage (MB): 74.75
JSON Encode: PHP
JSON Decode: PHP
WP_HTTP Status: WP_HTTP can access Facebook - All is OK ( Response Time was : 0.399888038635 seconds )
Curl Status: Curl is available and can access Facebook - All is OK, you can use the Curl Interface ( Response Time was : 0.45999121666 seconds )
Curl Version: 7.24.0
Facebook Interface: WP HTTP
JSON Version: 1.2.1
SimpleXML library: 0.1 (provided by PHP)
HTTP Output Character Encoding: pass
Internal PHP Character Encoding: UTF-8
MySQL: 5.5.23-55
Database character_set_client : utf8
Database character_set_connection : utf8
Database character_set_database : utf8
Database character_set_filesystem : binary
Database character_set_results : utf8
Database character_set_server : utf8
Database character_set_system : utf8
Database character_sets_dir : /usr/share/mysql/charsets/
Database collation_connection : utf8_general_ci
Database collation_database : utf8_unicode_ci
Database collation_server : utf8_unicode_ci
Server : ApacheWordbooker isn't doing any conversion and as you can see from here:
https://www.facebook.com/permalink.php?story_fbid=10151499849134836&id=284081594835
its not actually a problem.
This seems to be down to something odd in some WordPress installs so I'm going to have to put in a call to a html converter to solve the problem on some people's WordPress installs.
Thanks Steve. Or is there something we can fix on our end?
Its a very simple fix - I'll push it out in the next release once I've checked that putting the code into things doesn't do anything odd.
Should be fixed in 2.1.30 which I pushed out today.
Thank you. Can you also make this edit and post a new link to the beta version 2.2.0 You sent me that one for custom post type support.
Just getting around to this - sorry - do you still have the file referenced in the link above?
I posted a link to a newer beta on the Facebook Page :
You must log in to post.