WordPress 4.8

WordPress 4.8 expanded the widget experience with dedicated Image, Video, and Audio widgets, and changed the Text widget to offer visual rich-text editing alongside its text mode. It also added a Custom HTML widget for markup that should not be processed by the visual editor. The dashboard gained nearby WordPress event and news information, while the editor improved handling around link boundaries and core included accessibility and developer-facing refinements. These changes built on the older widget model rather than replacing the broader WordPress theme, plugin, and content architecture.

This cycle has reached end of life, so remaining on it leaves the site without upstream fixes for newly discovered core security defects or compatibility problems. Its age also increases the chance that current PHP versions, database environments, browsers, plugins, themes, payment integrations, and external APIs will no longer behave as expected. A site that appears stable can still carry exposure through old dependencies, unpatched administrator accounts, or custom code written against outdated core behavior. WooCommerce is a plugin that runs on WordPress, so a WooCommerce store is a WordPress site and its WordPress version matters to it just as much as its WooCommerce version does. Delaying migration can make the eventual work larger by forcing simultaneous remediation of core, extensions, PHP, custom code, and operational integrations.

Create a complete, tested backup of the database, uploaded media, themes, plugins, configuration, and any server-specific changes, and verify that it can be restored. Inventory active and inactive plugins, themes, custom code, integrations, scheduled tasks, and the server PHP and database versions; remove unused components and identify replacements for abandoned extensions. Clone production into a staging environment, select a currently supported WordPress target and compatible PHP environment, then test the core upgrade together with updated themes and plugins. Exercise login, content editing, media uploads, forms, search, email, caching, APIs, scheduled jobs, and any commerce checkout, payment, tax, shipping, and order-management flows. Resolve deprecated-code warnings and extension conflicts before deployment, document a rollback procedure, schedule a maintenance window, and monitor errors, performance, and key business transactions after the production upgrade.