Mike Jolley

WordPress Developer

Github to WordPress.org deploy script — November 26, 2015

Github to WordPress.org deploy script

Today I polished, documented, and open sourced a bash script I’ve been using to do plugin deployments from Github to WordPress.org (plus I wanted an excuse to use the new WordPress.com desktop app which is awesome by the way). It’s based on code Barry Kooij sent me a while back. You can find it here:


It handles Github tagging, removing junk files, and SVN tagging with minimal effort. It also has a quick checklist to stop you forgetting to set things in the readme.txt like the stable version (I’ve been guilty of forgetting this in the past).

Once downloaded to your machine, the script requires a Github access token, and a few edits to tell it which plugin you’re deploying.

After you’ve added the details specific to your project, you simply need to open it’s parent directory in terminal, and run the command:

sh release.sh

It then prompts you for a version, branch, and handles the deployment process.


The above demo is from a release of WP Job Manager I did today showing it working nicely. Hope it’s useful!

Debugging “unexpected token” in WooCommerce 2.4+ — November 12, 2015

Debugging “unexpected token” in WooCommerce 2.4+

When the WooCommerce checkout is processed it requires that gateways return an array (which is then converted into JSON) telling the checkout whether or not it was successful. It’s been this way since v1. Here is a basic example from the PayPal gateway:

return array(
    'result'   => 'success',
    'redirect' => $paypal_request->get_request_url( $order, $this->testmode )

The above for example returns a successful response and tells the checkout to redirect the user to the URL provided.

In 2.4+ this was made more strict in that the response must be valid JSON. Anything else in the response (such as HTML, notices or whitespace) will invalidate this JSON and you may see an error along the lines of:

SyntaxError: Unexpected token

WooThemes own gateways have all been tested for 2.4, however, we’ve seen some less-supported gateways break due to returning invalid content.

I’ve seen a few vocal users complaining about this recently on the forums (some even feeling the need to attack me personally, thanks guys) and thought it best to post a few steps on how you can narrow down the issue.

First off its always best to rule out your plugins and theme by disabling them, even though a lot of users seem to ignore this step. It is only temporary and helps narrow down the issue. Much better than shouting at me on WordPress.org.

Lets assume this does not narrow down the issue for a moment. How would you know if content is being output? The answer is in your browser console.

Lets simulate an error. In the paypal gateway, just before the array is returned I’ll add:

trigger_error( 'Uh oh' );

This triggers the error as expected:

2015-11-12 at 16.29

Now lets try to debug this like someone who does not know where the error is coming from.

In Chrome, go to View > Developer > Javascript Console whilst viewing the checkout.

Now trigger the error again.

After the error is shown, in the console go to the Network tab and click XHR:

2015-11-12 at 16.31

In the list you’re see one which looks like this: ?wc-ajax=checkout. Click on that and go to the response tab:

2015-11-12 at 16.32

Notice in my above example, there is the notice. This invalidates the JSON.

A valid JSON response {starts and ends with a bracket} – if there is an error, white space or content before or after those brackets, that is your issue.

In some cases the error will be obvious and allow you to patch or disable the cause.

Hopefully that helps.

So I spoke at WordCamp Netherlands… — October 6, 2015

So I spoke at WordCamp Netherlands…

Last week I was lucky enough to attend WordCamp Netherlands in Utrecht, followed by a small WC team meetup in Amsterdam. It was great to talk about work, plan for the future, and meet new and old friends.

(Some of) Team WooCommerce in NL

Rather than just attend the WordCamp I was actually a speaker. I presented a talk on user onboarding for plugins, using WooCommerce and WP Job Manager as examples and explaining the benefits and importance of a good first time experience.

Big crowd. Yikes!

Being a bit of a sociophobe and as a first time speaker (!) I was extremely nervous. I’m still not quite sure how I managed to get the courage to do it, but a huge thanks to Barry for the encouragement, advice and support. 

Although I muddled my words somewhat, I think it went reasonably okay. You can watch my presentation below.

I’d love your feedback (both good and bad) if you watched my talk so I can improve in the future, assuming I ever talk again :) Was it helpful? Did everything make sense? Did I waste 30 mins of your life?

Anyhow, thanks to all of those who attended!

User onboarding for WordPress plugins slides #WCNL — September 26, 2015
Interview with WisdmLabs — August 7, 2015
On joining Automattic — July 27, 2015

On joining Automattic

By now you’ve probably heard the news that Automattic (A8c) acquired WooThemes, where I was working as a developer for 3 years. July 1st I officially became an Automattician.


The weeks leading up to the acquisition were surreal; full of questions, a few awkward moments (it was top secret after all) but exciting nevertheless, and I was happy to be invited along with several others to New York to meet fellow Automatticians and be there for that bombshell of an announcement.

If acquisition were inevitable, I’m genuinely relieved that it was Automattic showing the interest. WooThemes and Automattic are very similar culturally and have similar aspirations. I know the team and products are going to be well looked after, and all the people I have met so far from A8c have been really friendly. So far my day to day activities have changed very little and everything feels completely natural.

The only challenge for me personally in this transition was parting ways with a side project/business of mine; WP Job Manager. This was a highly successful (and profitable) project with a user base 30k strong which I enjoyed working on in my spare time. Brian Krogsgard covered the story on poststatus.com in depth back in June and explained;

Automattic has a strict policy that employees cannot have paid side projects, whether client or product work. For Mike to stay at Automattic, he had to figure out what the future of WP Job Manager would be.

A8c expressed interest in acquiring the plugin and we came to an agreement which was a huge relief for me as I wanted to ensure whomever took over would actually look after the plugin and its users.

Anything was an option, including making WPJM free or selling it to a third party, but I’m glad we came to the solution we did. Since WPJM is part of Automattic now there’s no real or perceived conflict to the continuing work on it or revenue from it.

– Matt Mullenweg

Backed by A8c I think the project has a bright future. I’m still working on the dev side and I imagine more hands will be added in the coming months to keep things moving.

Looking ahead, I’m excited to continue and focus my attention on WooCommerce. Up until now we’ve had a tiny team (of ~4 developers) and it’s done fantastically well, but with more resources and people at our disposal who knows what we can achieve. We’ve already had some new people come over on rotation and its great to get fresh eyes on all of the projects and extensions.

Overall, I think that my move to Automattic, and consequential winding down of side projects, is going to have a positive impact on my life in general. I already have more free time, and things will be even better now that I don’t need to deal with tedious accounting and VAT returns for my businesses. I was even able to enjoy a vacation without the worry of supporting my products which I’ve not been able to do for years. It felt great.

And of course I may be able to blog a little more often :)

p.s. Please consider working with us – we’re always looking for talented devs and support staff!

Handling EU VAT on WPJobManager.com with WooCommerce — December 19, 2014

Handling EU VAT on WPJobManager.com with WooCommerce


Ah the EU. Always with their bright ideas. If you haven’t heard about the upcoming changes surrounding EU VAT, first off, where have you been hiding?

To put it simply, essentially they require everyone selling digital products to customers in the EU to charge EU Tax based on the customer location, regardless of where your business is based. You can read more about the changes in the blog post I wrote on WooThemes.com here.

Being based in the UK, and selling plugins on WPJobManager.com, I am affected by these changes and so I’ve been doing a lot of research, speaking to accountants, and preparing my site for the changes.

In this post I’ll explain what I’m doing and hopefully this may give you some ideas/resources if you’re struggling with compliance.

Continue reading


Get every new post delivered to your Inbox.

Join 3,334 other followers