Post saving failing because of slow Twitter OAuth
-
Hello,
while our post saving has worked, it resulted in a white screen instead of taking us back to post editing.
Here is the entry from PHP slow log:
[06-Nov-2017 16:19:22] [pool site] pid 20909 script_filename = /srv/www/site.com/wp-admin/post.php [0x00007f45400158a0] curl_exec() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc-cl/apis/tmhOAuth.php:643 [0x00007f4540015710] curlit() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc-cl/apis/tmhOAuth.php:396 [0x00007f4540015640] request() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc-cl/tw.api.php:43 [0x00007f45400154b0] doPostToNT() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc/nxs_ntlist_class.php:340 [0x00007f45400151e0] publishWP() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc-cl/tw.php:271 [0x00007f4540015120] nxs_doPublishToTW() /srv/www/site.com/wp-content/plugins/nxs-snap-pro-upgrade/nxs-snap-pro-upgrade.php(26) : eval()'d code:1 [0x00007f4540012f50] nxs_doSMAS2() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/NextScripts_SNAP.php:103 [0x00007f4540012c60] nxs_snapPublishTo() /srv/www/site.com/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/NextScripts_SNAP.php:82 [0x00007f4540012b30] nxs_snapLogPublishTo() /srv/www/site.com/wp-includes/plugin.php:503 [0x00007f45400129d0] do_action() /srv/www/site.com/wp-includes/post.php:4045 [0x00007f4540012900] wp_transition_post_status() /srv/www/site.com/wp-includes/post.php:3518 [0x00007f4540012540] wp_insert_post() /srv/www/site.com/wp-includes/post.php:3664 [0x00007f4540012460] wp_update_post() /srv/www/site.com/wp-admin/includes/post.php:376 [0x00007f4540012210] edit_post() /srv/www/site.com/wp-admin/post.php:238
I checked inc-cl/apis/tmhOAuth.php and see:
'curl_connecttimeout' => 30, 'curl_timeout' => 10,
I adjusted curl_connecttimeout down to 10 seconds.
It seems it was waiting close to full 40 seconds allowed as the post was saved, but then it just showed a white screen.
Using cron is not a solution for us as we need our post to be on Twitter immediately. If it fails to be posted right away, then it needs to be scheduled with a Cron. Does it work that way?
Thanks!
- The topic ‘Post saving failing because of slow Twitter OAuth’ is closed to new replies.