BigScoots Essential 75 Updates: What Does the Core Switch Cover?

Read the scope of the switch

The current BigScoots Console guide offers Minor, Enabled and Disabled under WordPress Core Updates. It recommends Minor for minor and security releases while reviewing major releases separately. Its description of Enabled includes development, minor and major updates; do not assume that label simply means ordinary stable plugin maintenance. Confirm the effective policy before changing an existing site.

WordPress itself distinguishes core, plugin, theme and translation updates, with separate core release categories. A core setting therefore cannot be used as evidence that every installed extension has automatic updates enabled.

Four tools that can reduce maintenance effort

| Capability | Practical value | Boundary | |---|---|---| | Core update policy | Choose which core releases run automatically. | The selected category is not a compatibility guarantee. | | Plugin management | View versions and initiate a specific plugin update. | The older WPO procedure is not proof of the current Console layout. | | Manual and daily backups | Prepare a recovery point before a material change. | A backup does not prove restoration was tested. | | Staging environment | Try an update away from the live site. | A successful test does not merge newer production data. |

The Console backup guide describes daily off-server backups, retention of up to 30 days and up to five manual backups. Confirm the correct site and environment and wait for the backup operation to complete; a scheduled daily copy may predate today's orders.

Assign a separate plugin and theme policy

WordPress provides per-plugin and per-theme automatic-update controls. Its documentation notes that hosts or plugins can alter their availability and that scheduled execution depends on WordPress Cron. An enabled control is consequently not evidence that an update actually ran. Review the installed version and failure notifications, and investigate Site Health warnings when scheduling fails.

Our suggested record has an owner, update policy, notification recipient and acceptance check for each important component. Prioritize security fixes rather than leaving everything disabled indefinitely. WooCommerce advises applying security or essential functionality fixes sooner than a routine maintenance cycle.

For a commercial extension, confirm that its update access and compatibility information are available. A managed-hosting subscription should not be assumed to renew every third-party software license or replace the developer responsible for custom code.

Installation success is not business acceptance

For a store, test representative product pages, cart, checkout, shipping, tax and order messages using an appropriate test-payment workflow. Complete required database updates and investigate failed scheduled actions before calling the release finished. These are proposed checks, not results measured by Toolnavia.

Automated visual checks are another distinct capability. WP Engine, for example, explicitly documents visual comparison and rollback in its own Smart Plugin Manager, including false-positive and false-negative limitations. That is comparison context, not a feature imported into Essential 75. Ask BigScoots for written confirmation of any managed testing or rollback scope that determines your purchase.

A homepage that opens cannot establish that a payment callback or member permission still works. For the separate logged-in cache issue, see the [membership-cache guide](/en/hosting/bigscoots-essential75-member-cache-user-isolation).

Prepare recovery without overwriting newer activity

BigScoots warns that Push to Live can replace the live site with its staging copy, including losing content added after the copy was taken. Do not use that action merely because an update test succeeded. Agree a deployment scope that preserves intervening production data.

Our recommended change record includes the old and new versions, backup timestamp, affected functions and recovery owner. If a release fails, preserve the error details and request an application-aware recovery rather than repeatedly applying unrelated changes. An old database restore can discard newer activity, while a code-only reversal may not match a changed database structure.

Recovery should also lead to a plan for fixing the original compatibility issue. Permanently remaining on a vulnerable release is not the intended outcome of a temporary rollback.

Compare the bill with the work it actually removes

On November 6, 2026, Essential 75 is publicly listed at $35 monthly or $350 annually, with one site, 75,000 monthly visits, 10GB storage and 150GB bandwidth. Twelve monthly payments total $420, so the published annual amount is $70 lower before resolving any account-specific charges. This arithmetic is not a final invoice or a measured maintenance saving.

The pricing FAQ calls displayed hosting prices tax-inclusive, whereas terms section 6.6 says applicable taxes are payable in addition. Ask for the final invoice rather than assuming either interpretation is settled. Future pricing can also change under the terms.

Choose Essential 75 when its hosting, support, staging and backup package fits and maintenance responsibilities are clear. Keep an adequate existing service when it already meets those needs. Do not buy a larger plan simply because a core-update toggle was mistaken for end-to-end quality assurance.

Affiliate disclosure: Toolnavia may earn a commission from an eligible BigScoots purchase through the approved direct referral link.