Built Mighty

Seymour Duncan, ongoing WooCommerce development

As a developer at Built Mighty, I help look after the Seymour Duncan online store: tracing a silent pre-order payment fault to its cause, keeping the site up under heavy traffic, and cutting its numbered releases.

Seymour Duncan home page

What went wrong

A store that sells guitar pickups and pedals lets fans reserve new gear before it ships. For those pre-orders the store places a hold on the buyer’s card at checkout, and charges it when the product is released. After a major version update to the store’s payment plugin, that hold quietly stopped happening. Checkout looked normal, no error appeared, and even the plugin’s built-in status screen reported no problems. The fault ran for about two weeks and came to light only when someone examined a single large pre-order by hand.

The pre-order fix

  • I tracked the fault down to one particular change inside that plugin update, and found a second, separate fault in the same release. I fixed both.
  • I identified the 13 pre-orders that had no card hold, so the business could resolve them.
  • I wrote automatic checks that confirm the pre-order payment hooks are still connected after any update, because a green status page proved not to be enough.

Also on this project

  • When the site was timing out, I found that one abusive visitor was using about 38% of its daily processing capacity. I blocked it at the hosting layer and the site recovered.
  • I fixed a marketing-integration plugin fault that had been crashing about 2,000 times a day. Separately, I added crawler protections against aggressive bots.
  • I traced repeated server errors to two pages that held the server’s limited workers for the full length of heavy jobs, and confirmed it against the live server logs.
  • I cut 51 numbered releases of the store’s code on GitHub.

The result

A later large pre-order was held, then released and charged as it should be, and the payment reached the company’s order system. Pre-order payments now have checks that alert the team when a plugin update breaks them. The abusive traffic was blocked, the crashing integration was fixed, and the store keeps getting regular updates, each one traceable to a tagged version of the code.

Tools I used, in plain words

WordPress and WooCommerce

The site platform and its shop plugin.

PHP

The programming language behind both, used for the fixes and the automated checks.

Git and GitHub releases

Numbered versions of the site code, so changes can be traced and rolled back.

Server logs and hosting tools

The records and controls that show what a live site is doing and let me block bad traffic.

Automated checks

Scripts that confirm the important parts of the payment flow are still connected after updates.

Gallery

Screenshots

Select an image to enlarge it.

Other work

More projects

All projects

Have a site that needs fixing, moving or building, or a role to fill? Tell me what’s going on.

Get in touch