Support » Plugin: Social » [Plugin: Social] Scheduled Broadcasting

  • I was having great difficulty broadcasting scheduled posts. I had connected my accounts, both to my profile, and in the plugin settings. I also went through each scheduled post and verified the accounts to be used for the Social Broadcast.

    Every post states that the post will broadcast to Twitter and Facebook … and once the post is published, they never broadcast automatically; only manually.

    Now that I’ve verified that I don’t have any conflicting plugins, I uninstalled version 2.5 and installed version 2.5b2.

    Now everything works just fine. Thanks for the great plugin!


Viewing 14 replies - 1 through 14 (of 14 total)
  • I’m having the same issue. I alerted the developer about it here but they never responded.

    Hopefully this bug can get squashed, as it’s incredibly annoying having to manually press the broadcast button on scheduled posts.

    I’m scheduling posts several days in advance, and I find that they’re getting broadcast to Twitter, but not to Facebook Pages. I get this message:

    Social failed to broadcast the blog post [POST TITLE] to one or more of your Social accounts.
    Facebook: [NAME] (Error validating access token: Session has expired at unix time 1338508800. The current unix time is 1339609154.)
    Facebook: [NAME] (Error validating access token: Session has expired at unix time 1338508800. The current unix time is 1339609154.)
    Possible fixes:
    Social was not successful in broadcasting this post (perhaps the service is down?), please try broadcasting again. If you receive this message repeatedly, you can try the support forums.

    When I go into the post to try to manually broadcast to the Facebook Pages, I get the same error, with a different current time:
    Facebook: [NAME] (Error validating access token: Session has expired at unix time 1338508800. The current unix time is 1339613081.)

    I’m thinking Social gets the authorization when I schedule, then it’s expired by the time the post publishes. Can the code be run, or re-run, at publishing time?

    I found this post which looks like it might have a solution in case the code is not already doing this:–handle-expired-access-tokens/

    Awesome find, pictureitsolved.

    You might have just stumbled upon the answer to the scheduled broadcast bug!

    Alex, any word on this issue being investigated?

    Out of curiosity, I translated the Unix times. The current times match today, but the session expiration time was almost two weeks ago, not just a few days ago.

    1338508800 Fri, 01 Jun 2012 00:00:00 GMT
    1339609154 Wed, 13 Jun 2012 17:39:14 GMT
    1339613081 Wed, 13 Jun 2012 18:44:41 GMT

    @dkerrigan, is this still a problem for you?

    I saw this post, suggesting disconnecting and reconnecting the Facebook accounts
    and it worked for me.

    It turns out the account owner had changed their password.

    Scheduled posts are still not being broadcast to Twitter or Facebook. Manually published posts broadcast correctly.

    I recently had a scheduled + broadcast post work exactly as expected:

    I’m on WP 3.5 and Social 2.7.

    I’m also on WP 3.5 and Social 2.7.

    I also have WP3.5 and Social 2.7

    If I create the post on the Web Browser Social works like a charm. If I do it and schedule on the iOS then it doesn’t get the Social activated and I need to log in and do it manually.

    I am looking to schedule only for Twitter, and would love some help.


    Sorry, reading more I understand that the question regarding auto-broadcast when you publish via XML-RPC or email.

    There are 2 admin on my account. One of them never goes there not post. The one that post it is me. I try deleting the iPhone account and log again. nothing.

    I click default on Social for the Twitter but every time I get the same message on the post:

    “This post is scheduled to be published at a later date. However, it is not scheduled to be broadcasted to any of your social accounts.”

    On the Social Plug in I have my Twitter account and Social is authorized on the Twitter side. It is mark as default.

    I really have no clue how to make it work.

    thanks for the help!

    Hi everybody,

    I also have troubles with Social and scheduled posting on Twitter for my WordPress site.

    On Social 2.6, all worked fine and since the update on Social 2.7 just the manual posting is working…
    On a scheduled article, Social seems to have planified the broadcasting but it doesn’t occur.
    No settings in Social have been modified.

    Someone could help me with a solution ?


    I’m running WP 3.5.1 and Social 2.8 and am having a similar problem: scheduled posts broadcast unreliably (read very rarely), while manually broadcasting works fine. Unfortunately, the whole point of Social is so that I don’t have to broadcast manually!

    In the log, I’m getting things like
    [SOCIAL – 2013-04-03 13:16:36] URL search returned no statuses for post #2575.

    Doing it manually, I see
    [SOCIAL – 2013-04-03 13:32:59] Running request: Broadcast/action_options
    , which is missing from the failed attempts.

    Any advice?

    Until yesterday, I had the same problem: posts were published but not broadcasted to Facebook or Twitter. I used WP 3.something (the version about 3 months old) and Social 2.7.

    Last night, I upgraded to WP 3.5.1 and Social 2.8. My last scheduled post was successfully broadcasted to Facebook and Twitter.

    Since I will be on some kind of charity vacation for some weeks, I won’t change anything more to the system and I really hope, scheduled posts will be broadcasted over the next weeks… 🙂

    I’m having the same issues….only now today when I went in to manually broadcast them I got this fatal error:

    Catchable fatal error: Object of class stdClass could not be converted to string in /home/content/37/8102337/html/theatreideas/wp-includes/formatting.php on line 509

    anyone have any ideas?

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘[Plugin: Social] Scheduled Broadcasting’ is closed to new replies.