Support » Plugin: Social » "Social" 2 Sites, Different Issues

  • Resolved KimJCastleberry


    On my main site, Social has a tendency to throw a 500 error when I click on “Broadcast” from within the post editor. Also the Facebook connect from the profile page will not connect at all… and the one from the settings page will disconnect immediately after you broadcast. The plugin has some issues but I can’t pinpoint where they are coming from. However, once I can get it to broadcast to twitter, it pulls in the tweets very nicely. (WP 3.2.1, TwentyEleven Theme) This blog was running commentluv and is now running commentluv premium (which does have some minor conflicts with Social)

    On my beta site (WP 3.2.1, Thesis 1.8.2 Theme), the plugin activates fine, but when trying to pretend to be a visitor and connect via twitter or FB throws two warnings on a otherwise white screen:

    Warning: Attempt to assign property of non-object in /beta/wp-content/plugins/social/social.php on line 2285

    Fatal error: Cannot use object of type stdClass as array in /beta/wp-content/plugins/social/social.php on line 2288

Viewing 9 replies - 1 through 9 (of 9 total)
  • Beta 2 of Social 2.0 is available for testing, we’d love to know if it fixes the issues you were seeing in the 1.x version:

    Alex I appreciate your followup. Some of the big league database cleanup I did solved parts of the problem listed. However, this version seems to have solved almost everything else.

    I did note that I cant seem to get the FB page (once set up, and that took some finding to realize it had to be in my profile) to stay auto selected for default broadcast. I had to renable it until I gave up – and then enable it on a per-post basis. However, it connected and published just fine.

    One thing I cant test atm is if this fixed the fact that the other version was hijacking gravatar images in my top commentator widget (and replacing it with mine oddly enough). I will need some time to reinstall that and see if it leaves it alone. My guess would be it will but it was a strange quirk.

    This is hot!

    Is there plans for G+ as soon as the API is together? I wonder if it’s out of scope to hope that eventually something like can also see integration for comment retrieval.

    It’s live on my site at atm if you want to take a look.

    PS: Andy Bailey did some re-coding on commentluv and commentluv premium to get the css to work well in the post-selector dropdown to make this pair of plugins play nice together.

    When Google+ has an API, we will certainly give it a look.

    Hey Alex, I was swinging through to note that I was doing alright on 2.0b2, though it had a few quirks.

    I stopped by github and noticed you have a 2.0b3 so I upgraded to that.

    I immediately noticed that it seems to be handling FB Pages better (keeping them toggled to default etc). I also noticed that the error that it was throwing (which was nonconsequential) when w3tc was activated has gone away. Two steps in the right direction.

    Anything else noteworthy in this iteration you’d like me to give a good kick to?

    Testing installation, WP 3.3 RC1, hostgator hosting, social 2.0 stable.

    This is the popup I get when trying to connect Twitter/FB. The frame says 403 but the page shows 404.


    “You don’t have permission to access /wp-admin/index.php on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.”

    There was also a minor hiccup during (clean) installation where it installed and activated but then told me it needed up to upgraded and was deactivated until I let it go through an upgrade cycle.

    I get a similar error on HostGator/WP3.2/social2.0/ when trying to attach accounts on either FB or Twitter in the settings pane. It DOES NOT do this in the author profiles when adding individual accounts. Likewise, this error appears when trying to connect from the actual post.

    I contacted Hostgator… it was hitting a mod_security rule on their server. They were able to release this rule on our domain.

    Hey Andy, yeah looks like the common error is definitely Hostgator mod_security related. I’ve got some fans that have added the plugin that are now hitting it too. I’ll have to pass this along.

    Alex, any chance of getting this sorted out from your side or is everyone going to have to address Hostgator?

    As HostGator seems to be the only host exhibiting this problem and they have shown a willingness to loosen their draconian security settings, we do not currently have plans to change the code to address this.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘"Social" 2 Sites, Different Issues’ is closed to new replies.