The years after launch

WordPress Plugin Maintenance: Keeping Custom Code in Step With Every WordPress and PHP Release

A plugin from the directory has a vendor, a changelog and thousands of sites reporting bugs. A custom plugin has you, and whoever you hire. That is fine, provided someone is watching the calendar WordPress, PHP and your other software keep. This page is about that someone.

November 12, 2026 · 9 min read

staging.acmepoolsupply.com · release test
A custom shipping plugin, tested before the live update
One deprecation notice, fixed while it was still a notice
  1. staging copied from live, backup restore confirmed
  2. WordPress 7.1.4 on staging, PHP raised to 8.3
  3. checkout test order: shipping rate returned
  4. deprecated: optional parameter before required one
  5. HPOS compatibility declared, orders read via wc_get_order
  6. plugin version raised, previous release kept for rollback
Illustrative: a sample release test for a fictional pool supply store

The short answer

Maintaining a custom WordPress plugin means testing it against each new WordPress, PHP and WooCommerce release on a staging copy, fixing what changed, and releasing a new version before the live site needs it. WordPress plugin auto-updates are opt-in, plugin by plugin. DataCram's hosting and maintenance plans start at $55 a month; changes to the plugin's own code are quoted first.

On this page
  1. The update that took checkout down on a Friday afternoon
  2. Three release calendars a custom plugin has to keep
  3. Auto-updates, as WordPress documents them
  4. Our release routine for a plugin update
  5. What the $55 plan covers, and what gets a written quote
  6. When maintenance stops being the sensible spend
  7. Starting maintenance on a plugin you already have

The update that took checkout down on a Friday afternoon

It always lands at the worst time. Someone clicks Update All at 4:40 on a Friday, the progress bars turn green, and by Saturday morning the checkout page shows a blank white rectangle where the payment button used to be. Nobody changed the custom shipping plugin. That was the problem. Everything around it changed, and it did not.

Custom plugins do not rot on their own. The code you paid for in 2023 is the same code today. What moves is the ground under it: a new WordPress release, a host upgrading PHP, a store plugin changing how it stores orders, a CRM retiring an old version of its API. Maintenance is the work of noticing those moves before a customer does, and adjusting the plugin so it keeps doing its one job your way.

There is a fair objection here. If custom code needs looking after, why not buy a plugin whose vendor does it? Sometimes you should, and our custom versus off-the-shelf comparison says when. Bought plugins need watching too, though, and their vendors set the schedule. With your own plugin, the schedule is yours.

Three release calendars a custom plugin has to keep

Every custom plugin we maintain gets checked against three calendars. Here is where each stood in November 2026, according to WordPress.org's release archive and requirements page, and WooCommerce's developer docs.

Where the platforms under a custom plugin stood as of November 2026, and what we test for each
CalendarWhere it standsWhat we test
WordPress coreWordPress 7.1.4, dated October 28, 2026; 7.1 shipped August 19, 2026 and 7.0 on May 20, 2026; "WordPress 7.2 Beta 5" was posted November 10, 2026The plugin on the newest release and on the next beta, before the final ships
PHPWordPress.org recommends "PHP version 8.3 or greater"; PHP 7.4 still runs WordPress but has "reached their official End Of Life"Deprecation notices and errors on the PHP version your host runs, and the next one
WooCommerce and other dependenciesHPOS "is enabled by default for new installations" since WooCommerce 8.2, October 2023Order code that uses WooCommerce's order functions, and a declared compatibility flag
Connected servicesSet by each vendor's APIThat forms, orders and bookings still reach the CRM, field software or email platform

The PHP line deserves a second look. WordPress.org says sites on PHP 7.4 or older MySQL versions run, but "these versions have reached their official End Of Life and may expose your site to security vulnerabilities." Hosts move customers forward eventually, sometimes with a week's notice. A plugin tested on 8.3 before that email arrives is a plugin that survives it. If an untested plugin is already keeping your site on old PHP, here is how to find the blocker and get unstuck.

Connected services are the quiet fourth calendar. When a CRM changes a field name, nothing on the website looks broken. Leads simply stop arriving. The API integration plugins page covers how those connections are built so a failed hand-off gets logged and flagged, not lost.

Auto-updates, as WordPress documents them

Owners often assume WordPress updates their plugins by itself. WordPress.org's auto-updates documentation, last updated January 13, 2023, says otherwise: "Since WordPress 5.5, websites Administrators can manually opt-in for automatic updates theme by theme and plugin by plugin." Plugin auto-updates are opt-in. The Plugins screen has an Automatic update column with bulk enable and disable.

Once a plugin is opted in, the same page says "By default WordPress runs auto-updates twice per day," and WordPress emails the site owner about what updated or failed. Auto-updates "rely on WordPress Cron tasks," so a site with cron trouble may skip them quietly; Tools, then Site Health, shows those errors. The documentation also advises: "Before enabling auto-updates on your plugins and themes, you may want to make sure you’re able to rollback to a previous version of your website in case things go wrong."

Our view, as practice rather than a WordPress rule: auto-updates suit small, well-maintained plugins on sites with tested backups. For the plugins that touch money or leads, and for your custom plugin, a person should test the update on a copy first. WordPress.org's same page is blunt about the alternative: "To keep your WordPress site secure, you should always update your plugins and themes to the latest version." Skipping updates is not maintenance either.

Warm shallow-focus developer desk with a laptop showing a dark screen, a mechanical keyboard, an open notebook and a pair of hands resting near a coffee mug
Most plugin maintenance is quiet testing on a copy of the site, done before anyone notices it was needed.

Our release routine for a plugin update

  1. 1

    Copy the live site to staging

    A fresh copy with real settings, so the test matches what customers see.

  2. 2

    Raise the platform first

    Update WordPress, PHP or WooCommerce on the copy to the version the live site is about to get.

  3. 3

    Run the paths that pay

    Submit every form, run a test checkout, book a slot, open each custom admin screen as each role.

  4. 4

    Read the error log

    Deprecation notices are early warnings. We fix them while they are still warnings.

  5. 5

    Update the plugin header

    Raise the Version number and keep the Requires at least and Requires PHP fields honest, so anyone reading the plugin knows what it supports.

  6. 6

    Release with a way back

    Deploy the new version with the previous one kept, and confirm the latest backup restores.

Two habits make this cheap. The first is code written to the handbook from the start, with the unique prefix WordPress.org's Plugin Handbook asks for ("at least 4 letters long, though we recommend 5") so a new plugin on the site cannot collide with yours. The second is a written list of what the plugin does, so the test run checks everything and not just what someone remembered.

What the $55 plan covers, and what gets a written quote

DataCram's hosting and maintenance plans start at $55 a month, as of November 2026, monthly with no long contract. We describe them here only as that page does. The line between the two columns below is written into each plan, so nobody is surprised by an invoice.

Inside the plan

  • Managed hosting with a content delivery network in front
  • Framework, plugin and dependency updates applied on a schedule and checked on a staging copy first
  • Daily off-server backups, test-restored
  • Firewall, malware scans and security alerts that reach a person
  • Uptime checked every minute from several regions
  • Small content changes, usually within a business day

Quoted before work starts

  • Changes to your custom plugin's own code when a new WordPress, PHP or WooCommerce release requires them
  • New features, screens or reports
  • A connected service retiring the API the plugin uses
  • Taking over a plugin someone else wrote, after we have read it
  • New design and new pages

Why quote code changes instead of folding them in? Because their size varies from ten minutes to two days, and a flat fee that covered the worst case would overcharge most months. You see the number before we start. Our plugin pricing page explains what drives it.

When maintenance stops being the sensible spend

Some plugins cost more to keep than to replace. An abandoned commercial plugin whose vendor has gone quiet is the classic case: the "lifetime license" outlived the company that sold it. Patchstack's State of WordPress Security in 2026 report, updated February 25, 2026, found "46% of vulnerabilities did not receive a fix from the developer in time for public disclosure." Patchstack sells WordPress security products; the figure is as of November 2026. When the fix never comes, replacing the plugin is maintenance.

  • One broken plugin today: a fixed-price plugin repair from $149 to $399, then decide.
  • A plugin someone else built and left: we read the code first, then quote maintenance or a rewrite. The who owns plugin code page explains why you want the repository before that conversation.
  • Updates breaking a theme and a plugin together: our theme and plugin conflict guide shows the test order.
  • A plugin we built for you: the plan above, with code changes quoted when a release calls for them.

Starting maintenance on a plugin you already have

Bring us the plugin, ours or someone else's. We read it, run it on a staging copy against the current WordPress and PHP versions, and write down what needs fixing now, what can wait and what should be replaced. If the code is sound, it joins a plan. If it needs a rewrite, the custom plugin development estimate is fixed and written, from $575, depending on complexity.

Not sure what is installed or how old it is? Start with the free website health check. DataCram is a web studio in San Antonio, Texas, building for the web since 1999 and working with businesses across the US by phone, video and a shared project page. Call (210) 346-0848.

Questions owners ask about custom WordPress plugins

Not by default. WordPress.org's documentation says administrators opt in to automatic updates plugin by plugin, a feature added in WordPress 5.5. For plugins that handle payments or leads, we test each update on a staging copy before it reaches the live site.

When something around it changes: a WordPress release, a PHP upgrade by your host, a WooCommerce change or a connected service's API. In 2026 WordPress shipped 7.0 in May and 7.1 in August, with 7.2 in beta by November. We test against each release and the next beta, and change the code only when a test shows a need.

WordPress.org recommends PHP 8.3 or greater as of November 2026. WordPress still runs on PHP 7.4, but WordPress.org says those older versions have reached end of life and may expose a site to security vulnerabilities. We test custom plugins on the version your host runs and the next one up.

The plan covers what our hosting and maintenance page lists, including updates applied on a schedule and checked on a staging copy, tested backups, security monitoring and small changes. Changes to a custom plugin's own code, such as new features or rework a new release requires, are quoted before work starts.

Usually. We read the code and test it against current WordPress and PHP before agreeing to anything, then quote either maintenance or a rewrite. You will need the source code and, ideally, its history. If the original developer kept the repository, sort that out first.

Not for every plugin. WordPress.org suggests making sure you can roll back before enabling them. Auto-updates suit small, well-maintained plugins on sites with tested backups. For checkout, forms, booking and custom code, testing on a copy first is the safer habit, as practice rather than a WordPress rule.

Keep reading

Free · No obligation

Get a plugin checked against the next release

Tell us what the plugin does and who wrote it. Someone at DataCram replies with what we would test, what we expect to find and the monthly price.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote