Double Posting
-
When I make a post and publish … goes to facebook – great.
When I edit that post and update … also goes to facebook. So if I have like 3-4 updates or text edits in a row it blows up my facebook page with repeat posts.
What can I do about this?
These are also custom post types – which work fine, but the options window is not visible on the post edit screen to turn on and off … either all or nothing – which may be the issue, but I think it should check that the post exists before just publishing to facebook on every update of the post …
Also I noticed an odd thing when I went to look at my settings to see if there was an option somewhere. It said it wasnt connected and I had to re-authorize my account. Log said …
Not a WB user (1) and no overide – give up
Would love to get this worked out, so any help would be greatly appreciated.
Thanks
-
Okay, here is the info from the version that works initially, but fails later.
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): 76.25 JSON Encode: PHP JSON Decode: PHP WP_HTTP Status: WP_HTTP can access Facebook - All is OK ( Response Time was : 0.397522926331 seconds ) Curl Status: Curl is available and can access Facebook - All is OK, you can use the Curl Interface ( Response Time was : 0.52093911171 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 : ApacheThis is the server info for the version you most recently posted here in the link above for me to try.
Wordbooker Release: 2.1.29 Wordbooker Code Base: 2.2.0 Beta 21 - 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): 76.25 JSON Encode: PHP JSON Decode: PHP WP_HTTP Status: WP_HTTP can access Facebook - All is OK ( Response Time was : 0.406075954437 seconds ) Curl Status: Curl is available and can access Facebook - All is OK, you can use the Curl Interface ( Response Time was : 0.388490915298 seconds ) Curl Version: 7.24.0 Facebook Interface: WP HTTP Wordbooker Server Access: Wordbooker Secure Access Failed ( ) Wordbooker Server Access (insecure): Wordbooker Insecure Access Failed ( Wordbooker Secure Access Failed ( ) ) 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 : ApacheAnd then also I noticed that when I click “Use Curl for Facebook interface calls:” on this most recent version as well – I get the following error.
Warning: curl_setopt() [function.curl-setopt]: Invalid curl configuration option in /home/agmedia/public_html/besocial/wp-content/plugins/wordbooker/includes/wordbooker_facebook_curl.php on line 202The version that works initially … but then fails later … I do not get that above warning. Neither of them have “Use Curl” checked … I just did it to test and see.
This is what is wrong:
Wordbooker Server Access: Wordbooker Secure Access Failed ( )
Wordbooker Server Access (insecure): Wordbooker Insecure Access Failed ( Wordbooker Secure Access Failed ( ) )
JSON Version: 1.2.1For some reason the calls to my server are returning nothing at all to your server. I can see the calls being made and I can see my server returning the right number of bytes…. they just never make it through to your server.
Cool, thank you. So then what can we do? Is there something I need to ask the tech guys at hostgator?
I really don’t know
Those two checks are to:
https://wordbooker.tty.org.uk/check_access.cgi to check secure connections
and
http://www.tty.org.uk/wordbooker/check_access.cgi to check for non secure
All they do is return “Wordbooker Acccess OK” (and yes I know there are too many c’s in there – that’s what comes of hacking code in a hurry).
So why calls made to these return nothing (which is why they fail and why the diagnostic messages have ( ) in them) I do not know at all. I am at a total loss of what to do next…
Here is what I see at my end in my logs:
174.37.241.140 – – [06/Mar/2013:17:59:25 +0000] “GET /wordbooker/check_access.cgi HTTP/1.1” 200 22 “-” “WordPress/3.5.1; http://besocialwisconsin.com; wordbooker-2.2.0 Beta 21 – Hangar 18, Area 51
which shows it returned 22 bytes (which is the message) to your server.
Hmm. Weird that it works for 2.1.27, so I dont think its a server/site issue. Everything is perfect on 2.1.27 … just that I have to reset the token all the time. Frustrating (but not with you … very happy for your assistance and still praise the plugin).
Quick Question. Does this pull comments to a page that is linked to a new facebook post? Like if I share the link directly on facebook … or only if the page is published and pushed to facebook through wordpress?
Wordbooker can only process things it knows about – so if a post from your blog is shared directly on Facebook then Wordbooker cant know about it so can’t handle the comments.
Hey Steve. Any insight on the token issue? I know we were not really getting anywhere with it, but is there something I can ask my host to do, or something I need?
Also – curious on the facebook widget. You can see it in the sidebar on this page – http://besocialwisconsin.com/bars/oriley-conways-irish-pub/
I have it set to 300px wide which is great for computer and also phone, but when the site scales to ipads it over extends past the bounds of the widget area.
I tried using 100% in the code, but it didnt work. Is there a way to set it to 100% rather than a fixed width?
iframe[style] {width: 100% !important;}
Probably have to dig deeper to find out the exact selector to avoid corrupting other iframes … but I dont have any others, so it works for now.
Its NOT working under 2.1.27 because its not getting a long access token which is what all the extra checks are in to catch as expired tokens cause huge numbers of failed calls to FB which means I get messages about my API usage and failure rates all the time.
I have no idea what your hosting company have done to break the http fetch methods – its not even returning error messages… we need to work out why a perfectly good call returns nothing.. and thats not something I can really do.
Are you using iframes to render FB objects? Facebook don’t really support iframe rendering any more so you should make sure that option is not checked.
The topic ‘Double Posting’ is closed to new replies.