Product Updates & Version Management

This guide explains how to prepare for WPCoreAI product updates, identify installed versions, follow the appropriate update method, and check your website afterward.

For a product that is not a WordPress plugin or theme, follow its own installation, access, and version-management instructions. WordPress menu paths apply only to WordPress software; licensing, updates, integrations, and support depend on the supplied product and purchase terms.

Update delivery can differ between products and installation packages. Use the existing documentation for your product to confirm its supported update workflow. Do not assume that every WPCoreAI plugin or theme includes an automatic WordPress updater.

Before You Update

Complete these checks before changing an existing installation:

  1. Record the installed product version.
  2. Identify the version you intend to install.
  3. Review any release notes and requirements supplied with that release.
  4. Back up the website’s database and files.
  5. Confirm how you would restore the backup.
  6. Keep a copy of the currently installed release package if available.
  7. Test the update on a staging copy before applying it to a live website where possible.

A previous ZIP is useful, but it does not replace a complete backup. An update may change database settings or stored data as well as product files.

If the product runs scheduled tasks, processes content, or interacts with external services, plan the update around those activities. Follow its documentation for pausing and resuming work where supported.

1. Identify Your Installed Version

WordPress Plugins

Open Plugins → Installed Plugins in your WordPress administration area. Find the plugin and note the version displayed with its details.

If the product also displays a version in its own administration screen, record any difference between the two locations.

WordPress Themes

Open Appearance → Themes and select the relevant theme to view its details and version.

If you use a child theme, record both the child theme and parent theme versions. Confirm which package the proposed update replaces.

Record the Environment

Also note your WordPress and PHP versions. Environment information is usually available under Tools → Site Health → Info.

Expected result: You can identify the installed product, its version, and the environment in which it is running.

2. Confirm the Intended Release

Review the release information available through your purchase access, product page, and documentation:

Confirm that the package belongs to the same product as the installed copy. Check any new requirements, migration instructions, or changes affecting integrations.

A ZIP filename alone is not sufficient to establish the release version. Compare it with the package information and the version reported by WordPress after installation.

Release Candidates and Other Prerelease Packages

Identifiers such as alpha, beta, or rc commonly indicate prerelease software. Do not assume that a prerelease package has the same status as the corresponding final release.

If the product page, documentation, and supplied package show different release identifiers, contact WPCoreAI before replacing a working production installation.

3. Confirm the Supported Update Method

Read the instructions for your product:

Depending on the supplied product package, the supported method may involve an update notice in WordPress or installation of a replacement ZIP.

Where the documented update service requires customer activation, confirm that the installed customer package meets those requirements. Activating a plugin in WordPress and activating a customer license are separate actions.

Check the information associated with your purchase for update entitlements. This guide explains update procedures; it does not change your purchase terms or guarantee a release schedule.

Where a package includes the WPCoreAI license center and updater, use Settings → [Product Name] License → Check for updates to request release information. This checks availability; it does not install the update. Licensed update downloads require an active license and recognized activation. If a recent-check message appears, wait at least one minute before retrying. These controls are available only in packages configured with that integration.

4. Test on Staging

A staging site is a separate copy used to test changes before visitors encounter them.

  1. Create or refresh a staging copy using your hosting provider’s supported process.
  2. Prevent the copy from sending unintended customer emails, taking live payments, or running duplicate automated work.
  3. Confirm any product-specific activation requirements for the staging address.
  4. Apply the intended update using the supported method.
  5. Test the features your website actually uses.

Test the features and integrations enabled on your website with controlled test data. For themes, inspect representative layouts and appearance settings; for plugins, verify the workflows your site uses. Follow your product’s precautions for automated or external actions.

If you cannot create a staging site, choose a suitable maintenance window and have a verified recovery process ready before updating production.

5. Update Through WordPress When Supported

Use this procedure only when your product’s documented workflow provides updates through WordPress.

  1. Sign in with an account permitted to update the relevant software.
  2. Open Dashboard → Updates, or inspect the relevant plugin or theme screen.
  3. Review the available version and release information.
  4. Confirm that your backup is ready and any required preparation is complete.
  5. Run the update for the intended product.
  6. Wait for WordPress to report completion before starting another update.
  7. Check the installed version and test the website.

Avoid submitting the same update repeatedly while it is processing. If the result is unclear, inspect the installed version and any error message before retrying.

Checking for an Expected Update

Where WordPress update delivery is supported, open Dashboard → Updates and use Check again if available.

If no notice appears, confirm the installed version, supported update method, and any documented activation requirements. The absence of a notice does not by itself prove that the installation is current or faulty.

6. Update Using a Replacement ZIP

Use this method when instructed by the product documentation or WPCoreAI support. Obtain the correct installation ZIP through the purchase access available to you.

Replacing a Plugin

  1. Open Plugins → Add New Plugin → Upload Plugin.
  2. Select the correct replacement plugin ZIP.
  3. Start installation.
  4. If WordPress recognizes an existing installation and offers a replacement comparison, check the product identity and version information carefully.
  5. Confirm replacement only when the details match your intended update.
  6. Wait for completion, then confirm the plugin’s version and activation state.

Some WordPress versions label the menu entry Add New. If the installer does not recognize the existing product as expected, stop and check the package rather than forcing the installation.

Replacing a Theme

  1. Open Appearance → Themes → Add New Theme → Upload Theme.
  2. Select the correct replacement theme ZIP.
  3. Start installation.
  4. If WordPress offers to replace an installed theme, review its identity and version information.
  5. Confirm the intended replacement.
  6. Check the installed version, active theme, and affected pages.

Some WordPress versions label the button Add New.

Do not rename the internal product folder to force an update. Avoid deleting the installed product first unless its documented procedure explicitly requires it. Plugin deletion can trigger an uninstall process that removes stored data.

7. Verify the Update

An installation success message is the starting point for verification. After the update:

  • Confirm that WordPress reports the intended product version.
  • Check that the expected plugin or theme remains active.
  • Inspect the product’s administration screens and saved settings.
  • Test the features used by your website.
  • Open representative public pages on desktop and mobile.
  • Test any relevant forms, purchase flows, or integrations affected by the change.
  • Check for new error messages.
  • Resume any paused work only after the relevant checks pass.

If an appearance change is not visible, clear the relevant page cache through your caching plugin, hosting service, or CDN, then test again. Cache clearing does not resolve a failed installation or an underlying application error.

Expected result: The intended version is installed, the website remains accessible, and the features you rely on work as expected.

Protect Customizations During Updates

Replacing product files can overwrite edits made directly inside the plugin or theme folder.

Before updating, identify any direct file changes and keep a record of them. For theme customizations, use supported settings or a properly configured child theme where appropriate.

A child theme does not guarantee that every customization remains compatible with a changed parent theme. Test custom templates, CSS, and functions after the update.

If you are unsure how an existing customization was implemented, ask its developer to review it before replacing the product files.

Automatic Updates

WordPress may offer automatic-update controls for installed plugins and themes. The presence of a control does not establish that a product’s update service is configured or that every future release will install successfully.

Before enabling automatic updates, confirm the supported delivery method, maintain recoverable backups, and consider how you will detect and respond to a failed update.

For websites where changes require review, use a managed update process with staging checks and post-update verification.

Downgrades and Recovery

Installing an older ZIP is not always a complete rollback. A newer release may have changed database structures, saved settings, or other stored data.

If an update causes a problem:

  1. Record the error and the versions involved.
  2. Check whether the public website and administration area remain accessible.
  3. Stop unrelated changes and preserve relevant diagnostic information.
  4. Contact WPCoreAI or your hosting provider for assistance, depending on the failure.
  5. If recovery requires a restore, use a known working backup of the relevant files and database.

For an active store or publishing website, account for orders, submissions, and content created after the backup. Ask your hosting provider to help plan a restore that avoids unnecessary data loss.

Do not repeatedly switch between releases without understanding their data compatibility. Retest the website after recovery.

Common Update Problems

The Update Package Cannot Be Downloaded

Record the exact message. Confirm the supported package-access method and any documented customer activation requirements.

If the error indicates a network connection problem, ask your hosting provider to inspect outbound access. Do not disable HTTPS certificate verification as a workaround.

The Update Reports a Permission or Storage Error

Ask your hosting provider to check available storage, temporary-directory access, file ownership, and permissions. Do not apply unrestricted writable permissions as a general fix.

The Version Did Not Change

Reload the relevant plugin or theme details and compare the reported version with the intended release. Confirm which ZIP was installed and whether WordPress reported completion.

If the result remains inconsistent, contact WPCoreAI before attempting another replacement.

The Website Breaks After Updating

Prioritize restoring access. If WordPress administration is available, you may be able to deactivate the affected plugin or return to the previously working theme as appropriate.

If administration is unavailable, contact your hosting provider for recovery assistance and inspection of the relevant PHP error log.

Keep a Simple Update Record

For each production update, record:

  • The product name.
  • The previous version and installed version.
  • The update date.
  • The update method.
  • The backup or recovery point used.
  • The checks completed and any issues found.

This record makes later troubleshooting easier and helps distinguish an update-related problem from an unrelated change.

Contact WPCoreAI About an Update

Use the Contact page if a release, package, or supported update method is unclear.

Include the product name, installed version, intended version, WordPress and PHP versions where known, update method, and exact error message. For purchase-access questions, include your order number if available.

Do not include passwords, payment details, license keys, API credentials, or private download URLs in the contact form.