Currently available for projects large and small.

Currently available for projects large and small.

I’m really sad that the collaborative online writing and editing tool that I’ve been using, Editorially, is to close.

The team behind it announced the closure in a blog post on Wednesday;

We’re proud of the team and tool that we built together and incredibly thankful that so many of you were willing to give it a try. And we continue to believe that evolving the way we collaborate as writers and editors is important work. But Editorially has failed to attract enough users to be sustainable, and we cannot honestly say we have reason to expect that to change.

I haven’t been a particularly heavy user of Editorially, but my use of it had been growing and it was gradually becoming an important part of my workflow for some tasks. I’d been planning to try and make more use of its collaborative possibilities in the future. So its closure on May 30th is a real disappointment.

I thought it was a really good example of an elegant user interface and was a pleasure to use. So it is distressing that such a well designed tool has failed to become sustainable.

Goodbye Editorially and thank you.

Grit & Oyster provides and supports websites built with WordPress. Which is a simple enough definition of what I do — but in order to clarify things for clients and to ensure that I can maintain a high level of quality I’ve been working on some new definitions of the services I offer. 

I have designed four distinct services to meet the needs of a range of different individuals and organisations. 

  1. For individual professionals, freelancers, campaigners and bloggers looking for a personal home page or portfolio website there is the GritPress network. This is currently in development and will enter a beta phase soon.
  2. Small and medium sized organisations and businesses looking for someone to sort them out a website may be interested in signing up to the GritHost network.
  3. Larger organisations or those with more complex websites looking for the reassurances of someone to look after their installation might benefit from my WordPress Concierge service.
  4. Finally, I am available as a freelance WordPress developer for hire for custom development projects.

This weekend (4th & 5th of January 2014) the data centre where the main server that I use to host websites and provide web services suffered a temporary power failure. This resulted in the server experiencing a significant fault which meant that the websites were not available throughout the weekend.

The full service was resumed this morning.

I’d like to sincerely apologise to all customers affected for the inconvenience caused. The problem was entirely due to circumstances beyond my control. However, I will be reviewing my set up and procedures to see if there are any lessons I can learn.

This is a series of videos that take you through the basic steps of hosting and building a website using WordPress. It is a useful guide to choosing a hosting solution and describes what you need to do to get a WordPress website set up using ‘one-click-install’ on a shared host (the most common approach for those switching to WordPress for the first time).

The videos are provided by WPMU DEV.

This is how to change the default display behaviour of the Jetpack plugin’s sharing buttons feature.

I’ve been using Jetpack to provide sharing buttons to Twitter, Facebook and the like on my personal site and was having an issue with where they were being positioned in a post. Because Jetpack adds the button code onto the end of the post content using a filter, they weren’t playing nicely with the elements in my theme that came after the post content. This was particularly noticeable when display the quote post format as the buttons were getting all wrapped up in a blockquote tag.

So I searched for a solution and eventually ended up with some code that strips out the buttons from the post content and then adds them back into the theme in the place where you want them displayed. Although I’ve not been using it, this code also does the same for Jetpack’s ‘like’ feature.

In your theme’s functions.php file add the following:

function jptweak_remove_share() {
if ( function_exists( 'sharing_display' ) ) remove_filter( 'the_content', 'sharing_display',19 );
if ( function_exists( 'sharing_display' ) ) remove_filter( 'the_excerpt', 'sharing_display',19 );
if ( class_exists( 'Jetpack_Likes' ) ) {
remove_filter( 'the_content', array( Jetpack_Likes::init(), 'post_likes' ), 30, 1 );
add_action( 'loop_start', 'jptweak_remove_share' );

Then where you want the sharing and like buttons to be displayed in your template files add this:

if ( function_exists( 'sharing_display' ) ) {
sharing_display( '', true );

if ( class_exists( 'Jetpack_Likes' ) ) {
$custom_likes = new Jetpack_Likes;
echo $custom_likes->post_likes( '' );

I actually wrapped the last bit of code in its own function and called that in the template for neatness sake.

The various if statements should ensure that everything works smoothly whether or not you have the particular Jetpack feature switched on or not.

The sources for this code are:


Currently available for projects large and small.

Currently available for projects large and small.