BlogStomp is a third-party alternative to creating blog posts directly inside your WordPress site. We do not officially support third-party software but we understand the desire to use these tools. Here are some troubleshooting tips if you see issues while using BlogStomp.

Verify you have the correct site URL  

Common issues generally revolve around an incorrect URL address. We will use the website https://example.com/  for clarity.

  1. The Blog URL is "http://" or "https://' sensitive so make sure you have the correct HTTP protocol added. Incorrect usage will result in an error from Blogstomp when trying to connect. A quick tip is to copy/paste your url from your live site.
    http://example.com/ (✗)
    https://example.com/ (✓)
  2. Ensure you do not have any url extensions such as https://example.com/blog
    https://example.com/blog  (✗)
    https://example.com/  (✓)
  3. If your site does not canonically use "www", do not use "www" in the site address.
    https://www.example.com/  (✗)
    https://example.com/  (✓)

Verify you have the correct WordPress login credentials

If you have any questions regarding your login credentials, contact Showit Support for assistance in recovering them. 

Troubleshooting Tips

If you are able to verify the connection in BlogStomp but unable to publish posts successfully, try the following recommendations:

  1. Publish posts during non-peak website traffic times (7pm PST- 5am PST)
  2. Publishing fewer images inside blog posts
  3. Use smaller image sizes inside blog posts

Will BlogStomp work for everyone? 

The variation for success using BlogStomp depends entirely on it's use by you as well the given server load for our hosting servers at any given time. BlogStomp works by creating "POST" requests that get sent through WordPress's XMLRPC API. The XMLRPC API dates back to early WordPress days and is now an older and less secure option for publishing blog posts to Wordpress. Two major factors that can determine the success for posting with BlogStomp are are typically based on the number of images in your post and the current server demand at any given time.

If you have a blog post with 100 images, each image will make it's own "POST" request to the server. BlogStomp sends all these request at the same time which can result in 100 requests for a specific resource on the server in a very short period of time. If these requests happen to hit the server during peak traffic times, the server will be unable to process them and return an error back to BlogStomp.

Majority of server resources are dedicated to delivering current content to user who visit your website. This can mean excessive "POST" requests may not be able to be processed at any given time if the server is unable to allocate resources, or if BlogStomp is attempting to send too many "POST" requests due to images in a very short period of time. We suggest trying again later or reducing the number of images in your post.


  

Did this answer your question?