Scripts stopped working after a WordPress update
A WordPress core update swapped the bundled jQuery and old plugin code was calling methods that were removed years ago, such as .live or .size.
Code brought up to modern jQuery
Working with jQuery?
Most jQuery code that reaches us was written years ago, by someone who has long since moved on, and now it is wedged between a modern browser and a WordPress update that keeps breaking it. We work out which version is actually running, what is calling it, and what can safely change.
What it is
jQuery is a JavaScript library that was created by John Resig in 2006 to make cross-browser JavaScript tolerable. It wrapped DOM traversal, events, Ajax and animation behind a short, forgiving syntax at a time when every browser disagreed on the details.
It became ubiquitous through the late 2000s and the early 2010s, and it is still bundled by default with WordPress. The latest major line is 3.x, with 3.7.1 as a recent release, and jQuery Migrate exists to help old code run on newer versions. Modern browsers now cover most of what it was built to paper over, and a lot of its API is built into the standard DOM through querySelector, fetch and classList.
The honest version
No technology is all upside. This is where jQuery earns its place and where it tends to cause trouble.
Sound familiar?
The jQuery problems that bring people to us, and what you have once each one is fixed.
A WordPress core update swapped the bundled jQuery and old plugin code was calling methods that were removed years ago, such as .live or .size.
Code brought up to modern jQuery
An old theme or CDN link pins the site to a jQuery version with published XSS issues, and every visitor loads that script.
Pinned to a patched release
Theme, plugin and a third-party widget each load their own copy of jQuery, and they quietly overwrite each other until something breaks.
One version, loaded once
A new theme shipped the slim build, which drops Ajax and effects, and existing plugin code expects the full build to be there.
Right build loaded for the site
jQuery and jQuery UI are loaded on every page, including ones that never use them, dragging Core Web Vitals down.
Only loaded where it is actually used
The console fills with deprecation warnings every page load, which means the next upgrade will remove something the site still depends on.
Deprecations resolved, Migrate retired
A jQuery plugin that has not seen a release in years is now the reason the site cannot move forward on anything else.
Replaced with something maintained
Years of accumulated jQuery across a site that would be smaller, faster and easier to hire for as vanilla JavaScript or a modern framework.
Modernised in stages, nothing broken
What we do
Call us for one failing plugin, or hand us the whole legacy front end.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Not always, and not in a hurry. If the theme and the plugins depend on it, removing it breaks the site. The useful first step is usually to make sure only one modern version loads, that it is a patched release, and that jQuery UI is only pulled in where it is actually used.
Yes. We run jQuery Migrate against the existing code to list every deprecated call, fix those in place, and then retire Migrate. The upgrade is tested on a copy of the site before anything changes on the live one.
Routinely. We work out which jQuery is really loading, which plugins are in play, and which code is still in use. From there you get a plain list of what is safe to keep, what should be patched, and what is worth replacing.
Usually yes. WordPress periodically bumps the bundled jQuery, most recently from 1.12 to 3.5 in WordPress 5.6, and plugins written against the older API often call methods that no longer exist. We patch the plugin or swap it for a maintained equivalent.
Yes, and we do it in stages. The site keeps working while the jQuery layer is peeled back page by page, so there is no big-bang rewrite and no window where the site is down.
Estimates are free. Describe what is breaking or what you want to modernise and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: