Several Desktop blog-editing applications use XML-RPC to allow you to manage your WordPress blog. The one I use is MarsEdit.
XML-RPC functionality has been turned on by default since WordPress 3.5 so after updating to WordPress 3.8.2 I was not expecting MarsEdit to report that XML-RPC services are disabled on this site.
Having spent some considerable time and effort cleaning this site after it had been hacked I was determined to make it as secure as I possibly could in an attempt to prevent it happening again.
This is a WordPress site running on an Apache server so one of the numerous measures I implemented was to use HTTP Authentication to password-protect the
Many of you will be familiar with the Jetpack plugin. This site uses Jetpack’s Stats module, previously the WordPress.com Stats plugin, to record and display post and page views.
The Stats module requires a connection to an account at WordPress.com where your self-hosted WordPress site is given a unique ID. This unique ID, associated with the site’s domain name, appeared partly responsible for the apparent recent loss of this site’s views.
Some while back I described a method for retrieving and displaying individual post view counts from WordPress.com for those who use the Stats module for site views.
This involved amending the theme’s files and having proved quite popular I thought I’d wrap this functionality in a simple plugin.
Back in July 2011 I noticed a problem with the WordPress Jetpack plugin and page navigation on this site. With the Jetpack plugin activated page navigation worked only if I was logged-in as admin. When logged-out page urls were being incorrectly re-written and causing 404 Not Found errors.
Now, some 9 months after having first raised the issue a WordPress.org forum member seems to have found a possible cause.