WordPress 4.7

WordPress 4.7 expanded the Customizer with starter content for new sites, visible custom CSS editing, video header support, and improved theme setup options. It introduced the Twenty Seventeen default theme, added PDF thumbnail previews in the media library, and let users select an administration-interface language independently of the site language. The cycle also exposed core content through REST API endpoints, enabling applications to read and manage posts, pages, comments, users, taxonomies, and media through the API when permissions allow it. WooCommerce is a plugin that runs on WordPress, so a WooCommerce store is a WordPress site and its WordPress version matters just as much as its WooCommerce version.

WordPress 4.7 has reached end of life, so it should not be treated as a maintained security baseline. Remaining on it leaves the site dependent on an old core codebase, with no expectation of vendor fixes for newly discovered issues affecting that line. The practical risk grows as current plugins, themes, hosting PHP versions, browsers, and external integrations move beyond the APIs and behavior available in this release. Teams may be unable to apply current plugin or WooCommerce updates without first updating WordPress, while retaining old extensions can create separate security and compatibility exposure. Older custom themes and plugins may also rely on assumptions that are no longer valid in current WordPress, making an eventual upgrade more expensive if it is deferred.

Create a complete, tested backup of the files, database, uploads, configuration, and any off-site integration settings, and verify that restoration works. Build a staging copy that matches production, then inventory the active theme, child theme, plugins, must-use plugins, custom code, scheduled tasks, REST API consumers, payment or shipping integrations, and hosting PHP and database versions. Identify replacements or updates for abandoned extensions before changing core. Upgrade WordPress on staging toward a currently supported release, using interim upgrades where the hosting stack or extensions require them, and update compatible plugins and themes in a controlled order. Test authentication and roles, editorial workflows, forms, media handling, permalinks, caching, email, search, API integrations, and all store journeys if WooCommerce is used, including checkout, payments, tax, shipping, order emails, refunds, and webhooks. Resolve deprecations in custom code, obtain stakeholder sign-off, schedule a production change with a rollback plan, and continue applying core, theme, plugin, and server updates through a regular maintenance process.