Tim
Forum Replies Created
-
The success log entry confirms the post was scheduled on Social Post Flow. It doesn’t indicate whether the post was then published from Social Post Flow to the social network (even with “Post Immediately”, there’s a slight delay before it’s actually published to the social network).
A few things worth knowing:
- The plugin shows a disconnected indicator on any profile that has lost its connection to Social Post Flow.
- You can enable email alerts at https://app.socialpostflow.com/profile to be notified when a post fails to publish to a social network.
- Email alerts are always sent when a profile’s connection cannot be refreshed and is disconnected — so if X had silently disconnected, you should have received an email.
Noted — thanks for the detailed report and the file reference.
This is a regression from Buffer’s new API, which no longer auto-parses OpenGraph metadata from the URL. The plugin now has to supply the description directly, which is why the long-content fallback became visible.
A fix this week will read from common SEO plugins first (Yoast, Rank Math, SEOPress, All-in-One SEO), fall back to the post excerpt, and finally to truncated content (~300 chars) where neither is available.
Double posting on update means a third party Plugin is triggering another update here.
You’re welcome to:
- Deactivate other Plugins, testing until the issue resolves
- Provide the name of the conflicting Plugin for further analysis
You’re welcome to check the Plugin’s settings, ensuring you only have one status defined for X.
If you continue to see multiple publishing:
- Triple check no other integrations are also set to publish to X
- Deactivate other Plugins, testing until you find the conflict.
It’s no longer possible, as Buffer’s API no longer reads the OpenGraph metadata from the URL shared.
The Title and Description are therefore populated from the Post’s title and excerpt. If you’re seeing all text of the post, you’ll need to define the Post’s excerpt in WordPress: https://wordpress.com/support/excerpts/
Forum: Plugins
In reply to: [Post to Social Media - WordPress to Hootsuite] Hootsuite API Error (400)Walk through your status settings at WP to Hootsuite > Settings > Posts, editing each status and ensuring all fields are completed. Any blank fields – such as schedule – must be set to e.g. Post Immediately.
@darren_s Buffer have increased the API limits, so this should now be resolved. Feel free to reach out to them at support@buffer.com if you continue to see the “Too many requests from this client. Please try again later” message.
@pointsi worth trying again. If you still see the same Connect Profiles screen, disconnect, connect and triple check the Buffer account you’re logging into on the OAuth authorization screen. If in doubt, do this in an incognito browser window as this’ll ensure you’re prompted on Buffer’s side to login to a Buffer account.
Buffer have increased the API limits, so this should now be resolved. Do let me know if you still encounter this issue. Thanks!
Buffer have increased the API limits, so this should now be resolved. Do let me know if you still encounter this issue. Thanks!
@slewisma – honestly, yes. If Buffer resolves the underlying API issues (rate limits, token refresh failures, image handling, link previews), I’d happily keep maintaining the plugin. It’s not something I want to walk away from after 14 years.
But Buffer already said the rate limits were fixed once, and they weren’t – so the June 7 sunset stands unless there’s clear, sustained improvement before then. Once they fix things and prove it holds, I’ll happily reverse the decision and post an update.
Every email to support@buffer.com from real users helps make that case.
@slewisma, I completely agree. The Buffer API issues have hit smaller users hardest, which is exactly why this is being raised with Buffer directly.
If you can spare 2 minutes, please email support@buffer.com and let them know this is affecting your nonprofit clients. Reports from real users carry more weight than ours alone, and it’s the most effective way to push them to fix it.
We’ve maintained WP to Buffer since 2012. Sunsetting it isn’t a decision taken lightly — but the underlying API has become unreliable to the point where supporting the plugin would mean knowingly shipping a broken product. That’s not something I’m willing to do, especially to the volunteer-run charities you mention.
The “Too many requests” error is a rate-limiting issue on Buffer’s API, not the plugin. It’s affecting customers across multiple sites since their May 27 API launch. The issue has been escalated to Buffer’s team, but there’s been no response.
To help apply pressure, please also email support@buffer.com directly — the more reports they receive, the faster it gets prioritised.
Given the scale of the issues with Buffer’s new API since launch — most of which are outside our control — both WordPress to Buffer (free) and WordPress to Buffer Pro will likely be sunset on June 7, unless there are serious improvements from their API.
The recommended alternative is Social Post Flow, a separate publishing service we operate that doesn’t rely on Buffer’s API: https://www.socialpostflow.com/
Migration is straightforward — connect your social accounts directly to Social Post Flow rather than going through Buffer.
- This reply was modified 2 weeks ago by Tim. Reason: Clarifying sunsetting only if the API issues are not resolved
The “Too many requests” error is a rate-limiting issue on Buffer’s API, not the plugin. It’s affecting customers across multiple sites since their May 27 API launch. The issue has been escalated to Buffer’s team, but there’s been no response.
To help apply pressure, please also email support@buffer.com directly — the more reports they receive, the faster it gets prioritised.
Given the scale of the issues with Buffer’s new API since launch — most of which are outside our control — both WordPress to Buffer (free) and WordPress to Buffer Pro will be sunset on June 7.
The recommended alternative is Social Post Flow, a separate publishing service we operate that doesn’t rely on Buffer’s API: https://www.socialpostflow.com/
Migration is straightforward — connect your social accounts directly to Social Post Flow rather than going through Buffer.
Resolved in 6.0.3, available now.
See Docs, noting options to:
- Manually delete all Log entries: https://www.socialpostflow.com/documentation/wordpress-plugin/log-settings/#clear-log
- Define how many days log entries should be preserved before being automatically deleted: https://www.socialpostflow.com/documentation/wordpress-plugin/log-settings/#preserve-logs