Case study · Yorkshire Coast Nature
A legacy PHP upgrade, from PHP 5.6 to 8.1, for a nature tour company
Yorkshire Coast Nature runs birding tours, wildlife safaris and photography workshops, and takes bookings on its own site. I upgraded their bespoke PHP CMS from PHP 5.6 to 8.1, then gave it a new front end. For new builds I use Laravel.
The new site launched in February 2024, on the same CMS I first built in 2012. See the live site (opens in a new tab).
- PHP upgrade
- 5.6 → 8.1
- Tours and workshops
- 41
- CMS first built
- 2012
- New front end live
- Feb 2024
Who they are
Yorkshire Coast Nature is a small, independent nature tourism company. Its guides run birding tours, wildlife safaris and photography workshops across the Yorkshire coast, Wolds and Moors.
What wasn't working
The site ran on PHP 5.6, which stopped getting security updates at the end of 2018. Every booking and payment went through that code. The business needed it on a supported version without breaking how customers book and pay.
What was built
- Platform
Bespoke PHP
- Technologies
- PHP 8.1
- Bespoke CMS
- Online booking with live availability
- PayPal payments
- Gift vouchers
- Responsive front end
I took the site on in February 2022. The first job was upgrading the whole codebase from PHP 5.6 to 8.1, keeping the CMS the team already knew.
Then I worked with a local freelance web designer on a new front end and joined it to the upgraded CMS. Every tour and workshop has its own dates, prices and places left, and customers book and pay online.
Inside the booking system
-
Availability
Every date shows its price and the places left, with a Book button.
-
Booking form
The booking form takes participants, access needs and gift voucher codes.
Upgrade or rebuild?
We looked at moving to WooCommerce. It would have meant a new admin, rebuilt booking rules and moving every tour across.
The client liked their CMS and knew it well. So we kept it and upgraded the code underneath, which kept the admin they use every day.
Keeping bookings running
The hard part was working inside a ten-year-old codebase while the business kept trading. PHP 7 and 8 removed functions and tightened rules that older code relied on.
Bookings and gift vouchers are paid through PayPal, so the upgraded code had to work with PayPal before anything went live. Orders and bookings had to carry on as normal.
What's held up
There isn't much I'd change. The CMS I first built in 2012 is still the one the team uses every day. It's had a PHP upgrade and a new front end, not a rebuild.
Upgrading rather than starting again meant nothing had to be relearned. The tours, workshops and booking process stayed where the team expected them.
The same CMS also runs Wold Ecology, owned by the same people.
The upgraded CMS and new front end went live in February 2024. Yorkshire Coast Nature now lists 27 tours and 14 workshops, each with live places left, and still takes bookings and gift vouchers through PayPal.
Upgrading an old PHP website
01 Should I upgrade my old PHP website or rebuild it?
It depends on whether the system still fits the business. Yorkshire Coast Nature's team liked their CMS, so upgrading the code kept their admin and booking process. A rebuild on WooCommerce would have meant learning a new system.
02 Is it safe to keep running PHP 5.6?
No. PHP 5.6 stopped getting security fixes on 31 December 2018, according to php.net. A site that takes payments on it is running code that no longer gets patched.
03 Can you upgrade PHP without breaking online payments?
Yes, if payments are tested before go-live. Yorkshire Coast Nature takes bookings and gift vouchers through PayPal, so the PayPal integration was the part we checked most closely.
04 Can a 2012 website get a modern design without a rebuild?
Yes. Yorkshire Coast Nature kept its CMS and booking system. A local freelance web designer designed a new front end, and I joined it to the upgraded code in 2024.
Got an old PHP site that needs bringing up to date?
How I build with LaravelLike what you see?
Tell me what your site runs on and what it needs to keep doing. I'll reply by the end of the next working day.