How to update Plumbit plugins

Plumbit plugins do not all receive updates from the same owner. Check the plugin source first, then update one component at a time with a backup and a staging check for major changes.

Before you update#

Back up the site files and database, and confirm that the restore path is available.
Test major updates on staging before changing a production site.
Record the current Plumbit, Plumbit Extensions, WordPress, PHP, and plugin versions.
Read the Plumbit release notes and confirm the current requirements in Plumbit requirements.
Keep the previous working packages or a complete backup available for rollback.
Avoid updates during active checkout, order, or important form-submission periods.

Identify the plugin's update source#

Theme and plugin updates are separate operations. Use the exact status, package source, and update owner shown in this Plumbit matrix.

Plugin	Plumbit status	Package source	Update owner
Plumbit Extensions	Required	Pre-Packaged	Plumbit-supplied TGMPA workflow at Appearance > Install Plugins when a compatible package is provided.
Elementor	Required	WordPress.org	Plugins > Installed Plugins or Dashboard > Updates.
One Click Demo Import	Required	Pre-Packaged	Plumbit-supplied TGMPA workflow at Appearance > Install Plugins.
Meta Box	Required	WordPress.org	Plugins > Installed Plugins or Dashboard > Updates.
Contact Form 7	Recommended	WordPress.org	Plugins > Installed Plugins or Dashboard > Updates.
WooCommerce	Recommended	WordPress.org	Plugins > Installed Plugins or Dashboard > Updates.
Envato Market	Recommended	Pre-Packaged	Plumbit-supplied TGMPA package at Appearance > Install Plugins; its Envato account connection remains Envato-owned.

Update Plumbit Extensions#

Plumbit Extensions is a separate plugin with its own directory and plugin files. Plumbit registers it as required and supplies a package at Appearance > Install Plugins when the theme release includes one. The installer can show Required, Update, Activate, Requires Update, or Required Update not Available depending on the installed and supplied versions.

Check the Plumbit version, the installed extension version, and the available package before updating. A theme update does not automatically update Plumbit Extensions unless the visible update workflow explicitly offers the compatible package. Do not delete the plugin first. Update or replace it through the supplied workflow, keep it active when the site depends on its Services, Projects, Team, and Stronghold widgets, then test those records and widgets.

Plugin settings and database content are stored separately from the plugin files in normal WordPress operation, but a backup and staging test are still required. A plugin update replaces files inside that plugin's directory, so direct edits to Plumbit Extensions can be overwritten.

Update WordPress.org plugins#

Open Plugins > Installed Plugins or Dashboard > Updates for Elementor, Meta Box, Contact Form 7, and WooCommerce. These plugins use the WordPress.org update channel and are not updated by replacing the Plumbit theme. Complete any plugin-owned prompt before testing the site.

An update action can replace plugin files while leaving database records in place, but compatibility code, defaults, or a plugin-owned database migration can still change visible behavior. Use a backup and staging checkpoint before a major update.

Update pre-packaged plugins#

Plumbit supplies Pre-Packaged packages for Plumbit Extensions, One Click Demo Import, and Envato Market. In TGMPA, Plumbit Extensions and One Click Demo Import are Required, while Envato Market is Recommended. Use Appearance > Install Plugins when a compatible package is offered, and do not download a replacement from an unofficial archive.

One Click Demo Import is an importer plugin. Updating it does not import demo content. Envato Market has its own account and service workflow; do not send account tokens or purchase codes in a support request. Plumbit does not include a separately licensed third-party premium plugin in this package.

Check Elementor and WooCommerce#

After an Elementor update, open representative Elementor pages and templates. If Elementor-owned styles are stale, use Elementor's own CSS regeneration tool; do not manually delete generated CSS files. Check headers, footers, page headers, Services, Projects, and Team widgets when Plumbit Extensions changes.

After a WooCommerce update, review the compatibility notes and back up before accepting a WooCommerce database-update prompt. WooCommerce owns that prompt. Test Shop, product pages, Cart, Checkout, My Account, product forms, and a representative order path. If WooCommerce reports an outdated template, identify whether the warning belongs to Plumbit or a child-theme override before copying anything.

Check Contact Form 7 and Meta Box#

Contact Form 7 plugin files update separately from form records and Mail settings. After an update, submit a test form and check the visible result, validation, spam integration, and mail handoff. A frontend success message does not guarantee inbox delivery. Use Contact Form 7 troubleshooting when delivery or form behavior is the issue.

Meta Box supplies the custom-field framework used by Plumbit settings and content screens. After a major Meta Box update, check the relevant page options, Service, Project, Team, and product fields without assuming that a missing screen means the stored value was deleted.

What plugin updates preserve#

Item	Normal update behavior
Plugin files	Files in the plugin directory are replaced by the new package.
Direct plugin edits	Direct edits can be overwritten during replacement.
Plugin settings and content	Normally stored separately from plugin files, but backup and staging remain necessary.
Elementor content and templates	Stored separately from plugin files; test layouts after a major update.
Contact forms	Form records and Mail settings remain separate from plugin files; test delivery.
WooCommerce products and orders	Database records normally remain; complete WooCommerce's own update prompt when required.
Meta Box values	Field values are separate from plugin files; check their owning screens after a major change.

After updating#

Confirm Plumbit Extensions and required plugins are active and show the expected versions.
Open representative Elementor pages, Header and Footer templates, and Page Headers.
Check Services, Projects, Team, the blog, Search, Archives, and the 404 page.
Test Shop, a product, Cart, Checkout, and My Account after WooCommerce changes.
Submit a Contact Form 7 test and verify the expected mail handoff.
Check menus, widgets, sidebars, mobile layouts, the browser console, and the PHP error log.

Expected result#

Each Plumbit-related plugin is updated through its correct source, required components remain active and compatible, and the workflows owned by the updated plugin pass their post-update checks.

Common problems#

Plumbit Extensions update is unavailable

Check the Plumbit version, supplied package, TGMPA notice, installed version, and package integrity. A required update may not be available until a compatible Plumbit package is supplied.

The required-plugin notice remains

Compare installed and required versions, confirm activation, review the available package, and check for a theme and plugin version mismatch. Do not delete the plugin as the first response.

A plugin update fails

Record the source, package, permissions, disk space, timeout, memory, network response, and compatibility message. Restore the pre-update working state when necessary rather than deleting files or database records.

Elementor layout changes after an update

Check the plugin compatibility, Elementor-owned CSS, templates, and representative responsive views. Regenerate CSS only through Elementor when its own output is stale.

WooCommerce displays a database update

Back up first, then follow the WooCommerce-owned prompt and test Shop, Cart, Checkout, My Account, and products.

A direct plugin customization disappeared

Plugin-file replacement can overwrite direct edits. Reapply the change through a supported extension point or maintained custom plugin after reviewing the new version.

Get help safely#

Provide the Plumbit version, Plumbit Extensions version, plugin name and versions, previous version, update source, exact error, WordPress and PHP versions, staging result, backup availability, recent customization, and a PHP error excerpt with secrets removed. Do not send WordPress or hosting passwords, database credentials, Envato tokens, purchase codes, or full private backups.

See Installing Plumbit plugins, Updating Plumbit safely, and Getting support for the adjacent workflows.