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 always 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 the “Use WP-Cron” setting.  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 either:
    1. Editing your Page, Post or Custom Post Type, or
    2. Clicking on WP to Buffer Pro > Logs, searching by Post ID.

Make 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: Logs: Post

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 (Edit Post > View WP to Buffer Pro Log > Export Log)
  3. A copy of any on screen errors you see whilst trying to publish a Post to Buffer.

cURL error 28: Connection timed out after 5001 milliseconds

Please work with your web host to ensure all of the following outbound connections can be made:

  • api.bufferapp.com can be made over SSL (port 443), using cURL through the command line
  • 104.16.97.40 can be made over SSL (port 443), using cURL through the command line
  • api.bufferapp.com can be made over SSL (port 443), using cURL through PHP
  • 104.16.97.40 can be made over SSL (port 443), using cURL through PHP

SSL certificate problem: unable to get local issuer certificate

cURL error 60: SSL certificate problem: certificate has expired

This is the web host’s responsibility to resolve, as the error relates to the system sending the cURL request – i.e. your server – (and not the server receiving the request).

See https://stackoverflow.com/questions/24611640/curl-60-ssl-certificate-unable-to-get-local-issuer-certificate for steps they can take to resolve.

For IIS users, see https://www.bluevalleytech.com/techtalk/blog/error-60-ssl-certificate-problem-unable-to-get-local-issuer-certificate-when-running-php-under-windows-iis.aspx

Certain characters / emojis do not display correctly

If you’re using characters such as Ä and Ö or emojis, and they either do not save in a status update (or display differently), there is a misconfiguration in your WordPress and/or database configuration.  You must verify that:

  1. Your MySQL database tables encoding is set to UTF-8 Unicode (utf8mb4).  Confirm this by viewing each WordPress database table information in your database editor (such as phpMyAdmin or Sequel Pro):
    Page Generator Pro: Debugging Issues: Database Settings
  2. Your MySQL database tables collation is set to a type of utf8mb4_ (ideally, utf8mb4_general_ci, but if this is already set to a type of utf8mb4_, the value can remain as-is).  Confirm this by viewing each WordPress database table information in your database editor (such as phpMyAdmin or Sequel Pro):
    Page Generator Pro: Debugging Issues: Database Settings
  3. Your WordPress database character set is set to utf8mb4.  Confirm this by editing your wp-config.php file, noting the below setting:
    Page Generator Pro: Debugging Issues: wp-config Settings
  4. Your WordPress database collate set is blank. Confirm this by editing your wp-config.php file, noting the below setting:
    Page Generator Pro: Debugging Issues: wp-config Settings

Mixing different database encoding, collation and WordPress’ database character sets between database tables and WordPress will result in content issues not just for WordPress to Buffer Pro, but for other plugins and content in general.

Buffer API Error: HTTP Code 403. #403 – Sorry, this access token has been suspended. Please contact support.

See the Documentation on how to:

  • Deauthorize the Plugin at WP to Buffer Pro > Settings > Deauthorize
  • Re-authorize the Plugin at WP to Buffer Pro > Settings > Authorize

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

Buffer API Error: #1000: Looks like there’s a problem with an image. Up for taking a look and trying again?

Buffer API Error: #1030

Buffer API Error: #1003

For images to be read by Buffer, and therefore social networks, the image must be publicly accessible.  Through an incognito session, not logged into your WordPress web site, ensure that:

  1. The Featured Image’s URL is directly accessible through your web browser, as a non-logged in WordPress User
  2. You are not using any ‘force login’ or similar Plugins that require a login to access the image
  3. You are not requiring HTTP Basic Authentication to access the image
  4. Your firewall Plugin or server is not blocking direct access to the Featured Image URL
  5. Any hotlinking protection Plugin is not blocking direct access to the Featured Image URL
  6. Your host accepts incoming connections from:
    1. buffer.com
    2. api.bufferapp.com
    3. wpzinc.com
  7. Buffer doesn’t accept image URLs with spaces, accented or special characters in the image filename.  You can install the Media File Renamer Plugin, which will automatically remove these when you upload image(s) to WordPress.
  8. For Instagram Profiles, the image must meet the required aspect ratios and minimum dimensions: https://support.buffer.com/hc/en-us/articles/360037965494-Instagram-s-accepted-aspect-ratio-ranges

If all of the above criteria are met, and the status’ image setting = Use Feat. Image, Linked to Post or Use Feat. Image, Not Linked to Post, you will need to reconnect the profile in question to your Buffer (https://buffer.com, not our Plugin): https://faq.buffer.com/article/294-publish-reconnect-social-account

If the issue still persists, please open a support request with Buffer to disconnect and connect the social media profile in question to your Buffer account, as this resolves the issue.  Disconnecting and connecting differs from re-connecting.

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

For Instagram and Pinterest, a Featured Image must be set on the Post, as these social networks require an image.

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:

WordPress

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

Buffer

At https://publish.buffer.com, for each Social Media Profile:

  • Click on the Profile
    WordPress to Buffer Pro: Change Profile Timezone: Profile
  • Click on the Settings tab
    WordPress to Buffer Pro: Change Profile Timezone: Settings
  • Click on Posting Schedule child tab, below the Settings tab
    WordPress to Buffer Pro: Change Profile Timezone: Posting Schedule
  • Change the Timezone as necessary to match the Timezone you defined in WordPress
    WordPress to Buffer Pro: Change Profile Timezone: Field

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

Buffer API Error: HTTP Code 400. #1011 – Hmm, it looks like you don’t have permission to post (to those subprofiles)

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.
  • If you’re using a Frontend Post Submission or Auto Blogging Plugin (User Submitted Posts, WP Property Feed, WPeMatico etc), refer to the Documentation

Taxonomy Tags are not working

  • Double check that the Tag you are using in the status message is correct.
  • If you’re using a Plugin to register Custom Taxonomies, the third party Plugin must register the Taxonomy on WordPress’ init hook.
  • If you’re using a Frontend Post Submission or Auto Blogging Plugin (User Submitted Posts, WP Property Feed, WPeMatico etc), or the taxonomy tag still does not work, refer to the Documentation and enable the Use WP Cron option.

We appreciate it takes some time to work through the below, but please don’t skip a point or rush to open a support request. We find 95% of Featured Image issues are truly resolved when stepping through all of the below steps.

  1. In the Plugin’s Settings for the Post Type in question, confirm that the status is configured to a value other than No Image
  2. In the Plugin’s Setting for the Post Type in question, if Override Defaults is enabled for a given enabled social media profile, confirm that the social media profile specific statuses are configured to a value other than No Image
  3. If using Per-Post Settings, confirm that the status is configured to a value other than No Image
  4. If using Per-Post Setting, if Override Defaults is enabled for a given enabled social media profile, confirm that the social media profile specific statuses are configured to a value other than No Image
  5. Ensure that you have a compatible SEO Plugin installed, per the Use OpenGraph Settings section in the Featured Image Settings Documentation
  6. Validate the URL you are sharing with Facebook and Twitter’s debug/validator tools, correcting all errors relating to redirects and og:image tags:
    1. https://developers.facebook.com/tools/debug
    2. https://cards-dev.twitter.com/validator
  7. If Facebook’s Debugger shows that the og:image property’s URL is on a different domain / subdomain to the URL that is being shared (e.g. your site is at www.yoursite.com, and the image is on images.yoursite.com), you’ll need to verify domain name ownership of both domains/subdomains.  Please refer to Buffer’s and Facebook’s steps to verify your domain.  It’s best to verify both the web site domain and any subdomains you’re using.
  8. Click the shared Post on e.g. Facebook or Twitter, and note the final URL in the browser.  Compare the structure of this to the Permalink setting at WordPress Admin > Settings > Permalinks.
    1. If the final URL includes a trailing forwardslash, your Permalinks must be configured to include a trailing forwardslash:
      WordPress to Buffer Pro: Featured Image: Permalink: Include Trailing Forwardslash
    2. If the final URL excludes a trailing forwardlash, your Permalinks must be configured to exclude a trailing forwardslash:
      WordPress to Buffer Pro: Featured Image: Permalink: Exclude Trailing Forwardslash
  9. 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.
  10. If you’re using a Frontend Post Submission or Auto Blogging Plugin (User Submitted Posts, WP Property Feed, WPeMatico etc), the Use WP Cron setting must be enabled.  Refer to the Documentation for more information
  11. Enable the Force Trailing Forwardslash option. Some SEO Plugins strip this, which may result in an incorrect OpenGraph image being read.
  12. Attempt to publish/update the WordPress Post in question, and observe whether the Featured Image appears in the Buffer queue:
    WordPress to Buffer Pro: Featured Image: OpenGraph: Buffer Queue Example

If, following all of the above, the issue persists, feel free to open a support request to include:

  • URL that is failing
  • Screenshot of Buffer queue, showing the URL in question
  • Direct link to shared URL on e.g. Facebook, Twitter
  • Copy of Plugin’s export configuration

Instagram Direct Posting Fails

If a Post is sent to an Instagram Business Profile, and you receive a reminder on your mobile device instead of Buffer directly Posting this to Instagram, check:

  1. Ensure that your Instagram profile is truly connected as an Instagram Business profile in Buffer. Even if you believe it previously was, please do take a moment to check again via https://buffer.com
  2. Reconnect your Instagram account to your Buffer profile (Buffer.com > Instagram Profile > Settings > Reconnect)
  3. Ensure that you are not publishing immediately from the Plugin (therefore queueing by adding to start/end of queue or a custom time)
  4. Ensure that you are specifying a single Image (not multiple Images)
  5. Ensure that the image is within a 4:5 to 1.91:1 aspect ratio
  6. Attempt to share a Post via another method (e.g. through Buffer.com or perhaps a browser extension) to see if the Post will directly schedule without needing a reminder.

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. Ensure any minification Plugins, such as WP Rocket, are not minifying WordPress to Buffer Pro’s CSS or Javascript files
  2. Have your web host increase the PHP post_max_size config option to at least 20MB.
  3. 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: https://www.wpzinc.com/documentation/wordpress-buffer-pro/user-access/
  4. Add the following to your wp-config.php file:
    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    Once done, attempt to save statuses, then carefully review the information in the resulting wp-content/debug.log file

  5. Check for an error notification on screen, and follow its instructions as necessary
    WordPress to Buffer Pro: Debugging: Settings not Saving: Error Notification
  6. Open the browser’s console log, and watch for any messages or errors when attempting to save statuses. To open the console:
    1. Google Chrome: Press Control + Shift + J (Windows/Linux) or ⌘ + Option + J (Mac)
    2. Firefox: Press Control + Shift + J (Windows/Linux) or ⌘ + Shift + J (Mac)
      WordPress to Buffer Pro: Debugging: Settings not Saving: Browser Console Log

If opening a support request for this, we’ll require the following from above:

  1. Copy of wp-content/debug.log file
  2. Screenshot of any on screen error notifications
  3. Screenshot of browser’s console log
  4. Copy of Plugin configuration

Forwardslash missing from URL

See https://www.wpzinc.com/documentation/wordpress-buffer-pro/general-settings/#force-trailing-forwardslash

Unable to Edit Posts

If attempting to edit a Post, Page or Custom Post Type results in a long load time over 2 minutes, you may need to deauthorize and re-authorize the Plugin with Buffer one time, to obtain a newer, more secure Access Token.

To do this:

  1. Visit http://yoursite.com/wp-admin/admin.php?page=wp-to-buffer-pro-settings&wp-to-buffer-pro-disconnect=1
  2. Authorize the Plugin with Buffer, per Docs

Status added to WordPress Cron for sending to Buffer, but no status sent

If Logs contain this message, however no statuses are subsequently sent to Buffer (and this log entry does not update), this is due to WordPress’ Cron system not being enabled or incorrectly functioning.

To resolve:

1. Confirm WordPress Cron Enabled

Check for the following line in you wp-config.php file:

define( 'DISABLE_WP_CRON', true );

If this exists, you’ll need to check with your web host:

  • If your web host intentionally disables WordPress’ Cron, they’ll need to instead trigger WordPress’ Cron manually.
  • If your web host does not intentionally disable WordPress’ Cron, you’ll need to remove the above line in the wp-config.php file.

2. Enable WordPress Debugging

Add the following to your wp-config.php file, performing the steps/tasks that you were unable to perform and including a copy of the resulting wp-content/debug.log file:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

3. Confirm Cron Tasks Running with WP Crontrol

  1. Install and activate the WP Crontrol Plugin
  2. Access via WordPress Admin > Tools > Cron Events
  3. If any error or warning is displayed, this must be corrected with your web host.  For example, but not limited to:
    1. There was a problem spawning a call to the WP-Cron system on your site
    2. DISABLE_WP_CRON is enabled
  4. If non-Plugin Cron Events show exclamation points, this indicates the WordPress Cron system is not running.  Please work with your web host to resolve.
  5. Publish or Update a WordPress Post, to trigger the creation of a wp_to_buffer_pro_publish_cron event
  6. Confirm the existence of the wp_to_buffer_pro_publish_cron event via WordPress Admin > Tools > Cron Events