Plugins and themes we see in support work

Names, not scores

Builders and sliders (Avada, WPBakery, Elementor) add weight and constraint. Forms (Gravity Forms, and the older Contact Form 7 installs we still find) fail in mail more often than in markup. ACF is usually innocent and occasionally the thing a broken field group is hanging from. WP Rocket and similar optimization plugins will happily cache a broken form. Yoast is a metadata tool that people blame for outages it did not cause. Wordfence will lock you out for reasons that are, occasionally, correct.

Hosts we have seen in the same era of work include everyday shared brands and managed WordPress platforms. Payment and CRM names that show up beside storefronts include PayPal, Stripe, Salesforce, HubSpot, and Avalara. We will say we have worked with them. We will not invent a count.

How conflicts actually present

We have replaced a custom interactive map that died after application updates because the plugin had no compatible follow-on version. The honest deliverable was a static image and editing instructions, not another year of a dead feature. We have restored forms that disappeared because the plugin directory was empty and the host would not allow the reinstall until limits and permissions were fixed — on both language versions.

Maintenance cycles that skip forms are how quote engines die on a Tuesday. Coordinated core, theme, and plugin updates sometimes cannot be taken independently; we have deployed that set and still had a licensing leftover to chase. That leftover is a note, not a failed site.

Mail plugins are not optional infrastructure

Gravity Forms can store a lead and still fail to send it. That is a mail-account problem more often than a forms-plugin problem. WP Rocket can cache the broken form after you “fixed” it. Wordfence can block the IP you are testing from. Yoast will not take your site down, but people will still disable it first because it is visible. Disable one thing at a time, on a copy, with a snapshot.

If you run a builder, accept that some layout bugs are constraints, not conflicts. We have had mobile menus and compressed tables that the builder would not let us fix without a different structure. That is an engineering conversation, not a “install a plugin to fix the plugin” conversation.

How to keep them from breaking

Update on a copy. Keep a snapshot. Change one risky plugin at a time on revenue sites. After the cycle, submit a form, log in, and place a test order if you take money. If a custom plugin cannot follow, replace the feature rather than freeze the rest of the stack for it. If you want that rhythm done for you, that is what care plans are for.

Site-down steps remain on the why websites go down article and the emergency repair page. A proper project document, if you are buying a rebuild instead of a repair, is the proposal checklist.

What an update day should look like

Pick a window. Take a snapshot you can restore. Write down the versions you are on. Update core, then themes, then plugins — or follow the order the site has already proven, if it has one. Load the homepage, an interior page, wp-admin, a form, and checkout. If a custom plugin fatals and has no compatible update, decide the replacement in that window, not “later.” Later is how a dead map sits on the homepage for six months.

Licensing leftovers after a successful deploy are normal. Record them. Do not pretend the cycle failed because a paid plugin wants a key. Do not pretend the cycle succeeded if the quote form is dead.

If you do not want to own that window, that is a care plan: WordPress care at a published $90 CAD/hour cadence, with the same testing list every time. Emergency work when someone skipped the window is still emergency repair.

A note on nulled and abandoned plugins

An abandoned plugin is a calendar problem. A nulled plugin is an incident. We will say which one we think we are looking at. We will not keep a nulled security plugin in the stack and call the site hardened. If a builder add-on has no current vendor, treat it like the custom map: replace the feature or accept that the next PHP bump may take it down.

Must-use plugins and drop-ins hide in places the Plugins screen does not list. If a “we deactivated everything” site is still fatal, look at mu-plugins, object-cache drop-ins, and host-injected files. That is also where leftover malware likes to live, which is when this article stops being a plugin article and becomes a cleanup.

Page builders earn their keep until they do not. The constraint is real: some layouts cannot be fixed inside the builder without a different structure. Naming Avada, WPBakery, or Elementor here is not a recommendation and not an insult. It is a statement that we have had to work inside them, around them, and sometimes after them.

If you want a second pair of eyes on a stack before the next PHP deadline, send the plugin list. If the site is already down, skip the list and send the URL. Those are different pages on this site for a reason.

The rest of the stack we will name

Alongside those WordPress products, our team has supported Sitefinity and Magento installations — upgrades, hosting moves, checkout and tax integrations, CRM sync. We mention that because it is true, not because we want every reader to buy an enterprise CMS. If you run one of those platforms and it still earns money, we will say whether repair, export, or a planned migration is the honest next step. We will not publish a ticket count from the years before Metro Vancouver IT.

WooCommerce and Shopify storefronts fail in familiar ways: checkout, payment apps, shipping rules, and the mail that proves an order happened. PayPal and Stripe are not interchangeable with “the form sent.” Avalara-style tax is not interchangeable with a single inclusive rate. Salesforce and HubSpot mappings should not clobber product names on every sync. If any of that is your week, start at API integration support or ecommerce development.

If you are buying a build rather than a repair, read the proposal checklist before you sign a document that has a mood board and a price but no exclusions.