Sharing with WordPress
This article will show you how to connect Clarify to your WordPress blog as well as how to upload a document.
We recommend using the WP REST API WordPress plugin.
The number one cause of support issues with Clarify center around issues uploading to WordPress using the legacy xmlrpc.php interface that comes with WordPress. Historically there have been security issues with WordPress and xmlrpc interface so many web hosting providers will shut down access to it if the server detects too many requests coming from a particular IP address.
Using this feature requires Clarify 2.0.7 or above and WordPress 4.7 or above.
You should be comfortable with installing and configuring plugins for WordPress.
You will need to download and install two plugins:
This plugin adds support for assigning tag to a post using a string rather than tag ids. From the Plugins page of your WordPress admin area, search for WP API Categories+Tags.
Alternatively you can locate the plugin at https://wordpress.org/plugins/wp-api-categoriestags/.
From the Plugins page of your WordPress admin area, search for WordPress REST API - OAuth 1.0a Server.
Alternatively you can locate the plugin at https://wordpress.org/plugins/rest-api-oauth1/.
The only plugin that requires configuration is the OAuth plugin. In the Users menu you will find a new Applications option. Click on it.
Fill in the Consumer Name and Description however you would like. For the Callback, enter the following:
Click Add Consumer when you are done.
When you see the following dialog appear enter the Client Key and Client Secret from WordPress and then click Authorize.
Next you are taken to your WordPress site in the default web browser. Click the Authorize button to allow Clarify to access your WordPress site in order to upload posts.
After clicking Authorize the WordPress sharing account will be added to Clarify. You can now upload content from Clarify to WordPress.
Clarify ships with one WordPress HTML template that is used when formatting your Clarify document for upload to WordPress. The template does not apply any sort of styling to the content that is uploaded. If you would like to create a custom HTML template that can be used when uploading to WordPress then please refer to the HTML templates manual.
- Enter your username and password.
- Clarify ships with one WordPress HTML template that is used when formatting your Clarify document for upload to WordPress. The template does not apply any sort of styling to the content that is uploaded. If you would like to create a custom HTML template that can be used when uploading to WordPress then please refer to the HTML templates manual.
- Test the connection to make sure you have entered your information correctly.
Now that you have configured your WordPress sharing account you will see a WordPress icon in the sharing toolbar. Click on it to upload your document to WordPress.
You will see this dialog when you upload the document. You can choose the blog, post type, status, and category (if applicable to the selected post type). Any tags you have assigned to the article will be assigned to the post you create in WordPress as well.
Clarify will list all of the available post types in your blog. The default choices allow you to create a Post or a Page. If you have any custom post types they will show up in the menu as well.
After you make your selections click the Upload button. When the upload is complete the URL to the WordPress page will be on the clipboard.
The next time you upload the Clarify document to WordPress Clarify will replace the existing post. When updating an existing WordPress post Clarify tries to optimize the update process by not uploading images which have already been uploaded. If a step image has been uploaded before then it will not be uploaded again if:
- The image still exists in WordPress and
- The image content has not changed.
If the image needs to be updated the behavior is different depending on whether you are using the xmlrpc.php url or the WP REST API pluging.
When using the WP REST API plugin the existing image on WordPress will be deleted from WordPress and a new image will be uploaded.
When using the xmlrpc.php url the exiting image on WordPress will be updated with the new image.
A couple of things to keep in mind. You should not modify any images that Clarify uploaded within WordPress itself if you plan on using Clarify to update the post later on. If you use a 3rd party WordPress plugin to replace an image in WordPress, Clarify won't know that you did and will not upload the latest image from the Clarify document. In addition, if you use WordPress to edit the image Clarify will not know that you made changes to it.
This article provides troubleshooting tips for known issues with posting to WordPress.
Note that these problems are all related to security issues associated with the xmlrpc.php file that ships with WordPress. We are currently working on a solution that uses a new JSON API for WordPress. It requires installing some plugins but so far in our tests does not experience any of the same issues. If you are having trouble posting to WordPress and would like to try the new solution we are working on then send an email to [email protected].
If you have iThemes Security installed make sure you don't have it set to deny all xmlrpc.php files. Switch it to only deny pingbacks and try again.
"Unable to reach the Wordpress server", message about your IP address being banned, or a mod_sec.html error
Some web host providers will blacklist an IP address that makes multiple requests to the xmlrpc.php file in a WordPress installation. This is due to the fact that the file has historically been used for nefarious purposes. Since Clarify documents often contain multiple images it is making multiple requests to the xmlrpc.php file on your server and your web hosting service may flag you.
You can contact your hosting provider and ask them to whitelist you so that you can upload to WordPress.
Another potential cause of the "Unable to reach the WordPress server" error could be a WordPress plugin.At least one user has reported issues with using the "EWWW Image Optimizer" plugin. You can try disabling plugins to see if one is causing a problem.