Loading Profile...
EMPLOYEE
update to the way we post to facebook
In response to user feedback, we have made a couple of changes to the way we post updates to facebook:
1. we think we fixed a bug with encoding of non-English characters in Facebook posts (but haven't yet tested extensively, so let us know if you still have problems). HTML entities like rich quotes may still cause a problem (e.g. things like ’ characters), we're still working on possible fixes to that.
2. by default we post a nicely formatted post, with title/link/description, and not a status update
3. however, if you change your settings (under "advanced settings" in twitterfeed) to post "title only" or "description only", rather than the default "title & description" setting, then we send the relevant content as a status update (in the same format it would appear on twitter)
We made this change because the vast majority of users prefer the way we post by default, but some users may want to post shorter, unformatted, status updates, and these would very often already use the "title only" option.
Hope this makes sense, please let us know any comments and any problems you may find.
1. we think we fixed a bug with encoding of non-English characters in Facebook posts (but haven't yet tested extensively, so let us know if you still have problems). HTML entities like rich quotes may still cause a problem (e.g. things like ’ characters), we're still working on possible fixes to that.
2. by default we post a nicely formatted post, with title/link/description, and not a status update
3. however, if you change your settings (under "advanced settings" in twitterfeed) to post "title only" or "description only", rather than the default "title & description" setting, then we send the relevant content as a status update (in the same format it would appear on twitter)
We made this change because the vast majority of users prefer the way we post by default, but some users may want to post shorter, unformatted, status updates, and these would very often already use the "title only" option.
Hope this makes sense, please let us know any comments and any problems you may find.
Follow this update to get notifications on your dashboard.
-
Inappropriate?Works very well with the new changes. -
Inappropriate?My settings state "Title Only", but my last post was posted with a complete description.
I hope this is fixed now. -
Inappropriate?any progress on the ’ encoding issue. Out of interest does decoding as the encoding declaration on the RSS before posting to FB not work (pretty sure if it was that simple would have been fixed already).
With xml feed we have has issues when the actual encoding is not know - guessing doesn't really work.
I’m frustrated
4 Comments
Add a comment
-
I believe the encoding for non-english characters should work now - if not, could you show us an example so we can try and replicate the issue. -
Hi, the titles of stories on this RSS feed that have the right single quotations marks encoded as ’ are coming up as ’ in facebook - fine in twitter.
http://dntest1.wordpress.com/feed/
Let me know if you need anything else.
Thanks -
Ah yes - it seems that non-english characters work, but there's still an issue with HTML entities like the rich quotes you mention. I'll try and find you if this is something we can fix at our end, or if the issue with FB - when I initially looked I could see way to post these HTML entities to FB correctly, but will keep looking.
-
does decoding it first at your end then posting to FB not work?
-
Inappropriate?Hi any feedback on this? thanks
