Plugin Update Support for WordPress and More

Why updates feel risky, and why skipping them is worse

Most site owners have been burned once: they clicked "Update all" and the site went white, or the page builder layout fell apart. So the updates pile up. The problem is that plugin updates very often contain security fixes, and once a vulnerability is published, bots start scanning for unpatched sites within days.

The answer is not to stop updating, but to update properly: with a backup, in the right order, and with someone checking the result.

How dijitul support runs updates

1. Backup. A full files and database backup, stored off the server.
2. Read the notes. For major version jumps (WooCommerce, Elementor, Divi, ACF, Gravity Forms and the like) we check the changelog for breaking changes and known issues.
3. Update in order. Usually WordPress core, then the theme, then plugins, with dependent add-ons updated after their parent plugin.
4. Run database updates that WooCommerce and others ask for.
5. Check. Homepage, key landing pages, contact forms, search, login and, for shops, a product page and the basket.
6. Clear caches so visitors see the updated site.

For high-risk sites we run updates on a staging copy first and only push to live once it checks out.

When an update breaks something

When an update does cause a problem, we fix it rather than just reverting and leaving you exposed. Common causes we deal with:

• Plugin conflicts. Two plugins loading different versions of the same library, or both hooking into the same part of the checkout.
• PHP compatibility. A new plugin version needs a newer PHP than your server runs. See PHP version upgrade.
• Theme template overrides. WooCommerce reports outdated template copies in your theme that need updating.
• Cached CSS and JavaScript. The page builder needs its CSS regenerated, or the caching plugin is serving old files.

If the site is down right now, see broken website repair.

Premium plugins, licences and abandoned code

Premium plugins only update while their licence is active. We list every paid plugin, its licence status and renewal date, so you are not unknowingly running an out-of-date copy. We also flag plugins that have been closed on WordPress.org or have not had an update in a long time, and suggest maintained alternatives. Nulled (pirated) plugins are removed and replaced, because they are a common source of malware.

Although most of our update work is WordPress, we also handle extension updates on Joomla, Drupal and other platforms.

What you get after each update run

Updating should not be invisible. After each run you can see what changed: which plugins moved from which version to which, anything we held back and why, and anything that needs your decision, such as a premium licence to renew or a plugin we recommend replacing. If we held an update back, for example a major page builder release with open bug reports, we note it and come back to it once the first fixes are out.

We also keep an eye on the knock-on effects that are easy to miss: a contact form that still displays but no longer sends (see website forms not working), a payment gateway plugin that needs new API settings, or a caching plugin that needs its rules rebuilt after a WooCommerce update.

Pricing

Updates applied and checked are included in every support plan. Essential is £25 a month + VAT and includes updates, daily backups, uptime monitoring and security monitoring. Business at £50 a month + VAT adds an hour of fixes and changes each month and priority support, which covers most update-related conflicts. A one-off catch-up on a site that has not been updated in years is £45 an hour + VAT, with a 30-minute minimum and then 15-minute blocks. We look first and tell you roughly how long the catch-up should take before we start. Get in touch.

What it costs

Support plans from £25 a month + VAT, or £45 an hour + VAT for one-off fixes. Pick a plan if you want it looked after every month, or pay by the hour for a one-off job.

Related