Magento on PHP 8.2 has a deadline

If your Magento 2.4.6 store still runs on PHP 8.2, put 31 December 2026 on the release calendar. That is when upstream PHP security support ends. Your checkout may work fine the following morning. The work to find a supported combination of Magento, PHP and your extensions belongs before that date.

Author
Intercube
Published
Reading time
4 min read

01

The PHP deadline applies to the server

The PHP project’s support schedule ends upstream security updates for PHP 8.2 on 31 December 2026. Adobe’s lifecycle policy flags the date for Adobe Commerce 2.4.6 stores that use PHP 8.2. A Commerce support extension covers the application under Adobe’s terms. The runtime has its own support timetable.

Ask your provider which PHP version actually handles storefront requests, scheduled jobs and queue consumers. Then ask what patch coverage applies after December. If your provider offers extended PHP maintenance, get the version, scope and end date in writing before using it to schedule a later upgrade.

02

Choose the Magento release and PHP together

Start with your exact Magento edition and patch level. Adobe lists PHP 8.1 and 8.2 for the on-premises Commerce 2.4.6-p15 release. That gives a merchant on that combination a concrete reason to look at a newer application release. Check Adobe’s requirements for your edition and target, then review Composer constraints and support from the vendors of the modules you rely on.

Check what the upgrade changes elsewhere. A supported PHP version still needs compatible search and database versions, and your payments and fulfilment extensions need to work against the new application. Once you know those dependencies, you can choose whether to upgrade in place or prepare the new stack with your next host.

03

Place an order before you book the cutover

Give your Magento developers a staging environment on the target stack. Put a product in the basket, check out with a test payment and watch the order reach the system that handles fulfilment. If your catalogue comes from an ERP or a feed, change one test product and confirm that the update is reflected in search.

Use the rehearsal to decide when the real store can switch. A database change can require a maintenance window. Agree when the store stops accepting orders, how you reconcile recent orders, and when to fall back if a critical step fails.

04

Rehearse the upgrade on Intercube

If your current host cannot give your developers an environment on the target stack, we can prepare one as part of a move to Intercube managed Magento hosting. Our engineers configure the runtime and services. Your Magento team can bring its modules and run the checkout, indexing and fulfilment tests before the shop moves.

Migration to Intercube managed hosting is included at no additional cost. We agree the data transfer and cutover with your team during onboarding, so you can use the rehearsal to make a decision before you set a production date.

What to settle before the deadline

  • The actual PHP version in production and for background jobs.
  • The exact Magento edition and patch level.
  • A target stack the Magento release supports.
  • A rehearsal that follows an order through fulfilment.
  • A trading window and fallback plan your team agrees to.

PHP and Adobe documentation

Plan your Magento upgrade and move

Tell us which Magento and PHP versions you run. We can help scope the target environment and a rehearsal with your developer.

Discuss your Magento migration