Debugging Issues

Videos are not designed to be a substitute for instructions. Please refer to the detailed Documentation below.

At times, WordPress to Buffer Pro may not be able to send your status to Buffer through the Buffer API.

Before opening a support request with us, please ensure you’ve completed the following steps:

  1. Enable Logging.  This can be done via WordPress Administration > WP to Buffer Pro > Settings > Enable Logging.
  2. Disable WP-Cron.  This can be done via WordPress Administration > WP to Buffer Pro > Settings > Use WP Cron?
  3. Review the logs of the failed Post.  This can be done by editing your Page, Post or Custom Post Type and making a note of any error messages that appear in the Log window.  If the Buffer: Response provides a meaningful error message, take a moment to review that and act as necessary.  For example, if the error states that your Buffer queue is full, or that the status message is similar to the previous message, then you’ll need to make changes.
    WordPress to Buffer Pro: Logging

When sending your support request, be sure to include:

  1. An Export of your Plugin Settings (WP to Buffer Pro > Import/Export > Export)
  2. An Export of your Plugin Log (Step 3 > Export Log)
  3. A copy of any on screen errors you see whilst trying to publish a Post to Buffer.

Please note: If we receive a support request that does not demonstrate all of the above items have been completed, we will ask that you complete them.  On average, we can resolve tickets 85% faster this way.

Common Issues

Buffer API Error: 400 Bad Request. Invalid image url parameter supplied

Buffer doesn’t accept image URLs with accented / special characters in the image filename.  You can install the Media File Renamer Plugin, which will automatically remove these special characters when you upload image(s) to WordPress.

Buffer will then accept the image you are trying to include with your status update, and no error will be returned.

Buffer API Error: 400 Bad Request. Oops! You need to schedule your update for some time in the future!

Any status that is sent to Buffer must be immediately or in the future.  If you receive this error, there are a few possible reasons:

  • The status is using the Custom Time option and, relative to the Post’s publication or updated date, the days, hours and/or minutes entered result in the status being scheduled in the past.
  • The status is using the Custom Time (based on Custom Field / Post Meta Value) option and, relative to the Custom Field’s value, the days, hours and/or minutes entered result in the status being scheduled in the past.
  • There is an inconsistency between the WordPress timezone and Buffer timezone.

To resolve WordPress and Buffer timezone differences:


  • Navigate to Settings > General
  • Set the Timezone option to your timezone
    WordPress to Buffer Pro: Timezones: WordPress Settings


For each Social Media Profile:

  • Click on the Profile
    WordPress to Buffer Pro: Define Timezone: Buffer: Social Media Account Selection
  • Click on Settings > Posting Schedule
    WordPress to Buffer Pro: Define Timezone: Buffer: Settings Menu
  • Change the Timezone as necessary to match
    WordPress to Buffer Pro: Define Timezone: Buffer: Timezone Field

Once complete, statuses will then schedule at the correct time.

Custom Field Tags are not working

  • Double check that the Tag you are using in the status message is correct.  Examples:
    • Custom Field Name / Key = test.  Use {custom_field_test}
    • Custom Field Name / Key = _location.  Use {custom_field__location} (note the double underscore!)
  • Gutenberg: If you are using Gutenberg, and the Custom Field / Post Meta is stored outside of Gutenberg’s blocks (for example, registered in a meta box below the Gutenberg editor), ensure that you are using WordPress to Buffer 3.6.8 or higher.
  • REST API: If you are using the REST API, ensure that the Custom Field in question is registered in your code using WordPress’ register_meta() function.

Featured Image setting is not honored

Since December 18th, 2017, Facebook require that you verify domain name ownership when using what Buffer call “Link attachment customizations” (i.e. specifying a different image than the Featured Image for a Page, Post or Custom Post Type).

Please refer to Buffer’s and Facebook’s steps to verify your domain.

Featured Image does not display on shared Posts when set to use OpenGraph Settings

  1. Ensure that you have a compatible SEO Plugin installed, per the Use OpenGraph Settings section in the Featured Image Settings Documentation
  2. If you are using the Post Immediately option on a status, consider using the Custom Time option, and setting it to post 2 – 3 minutes after the Post publication.  This allows third party caching plugins, such as W3 Total Cache, sufficient time to build the published Post for Buffer (and the social networks) to read the valid OpenGraph data.

Settings not saving or changing

Buffer accounts with numerous social media profiles, coupled with several public Post Types, will result in a large number of settings available for configuration.  When this number exceeds a limit in PHP, settings will not save or change.

To resolve:

  1. Have your web host increase the PHP max_input_vars config option to 5,000.
  2. (Pro version only) Consider using the User Access and Enable Specific Post Type options to only display the Post Types and social media profiles that you want to configure.  See Docs: