[{"data":1,"prerenderedAt":195},["ShallowReactive",2],{"seo-verification":3,"blog-php-8-1-minimum-prepare-clients-online-stores-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-php-8-1-minimum-prepare-clients-online-stores-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":28,"featuredImage":30,"bgImage":31,"posterImage":32,"relatedSolution":30,"intro":33,"sections":34,"ctaTitle":133,"ctaBody":134,"ctaButton":135,"ctaUrl":136,"relatedPosts":137},560,"php-8-1-minimum-prepare-clients-online-stores",{"fr":12,"en":10,"ar":13,"es":14},"php-8-1-minimum-preparer-boutiques-en-ligne-clients","php-8-1-الحد-الأدنى-تجهيز-متاجر-العملاء-الإلكترونية","php-8-1-minimo-preparar-tiendas-en-linea-clientes","PHP 8.1 minimum: prepare your clients' online stores","WooCommerce proposes PHP 8.1 as its minimum. Check each client store's PHP version, test on a copy and migrate without breaking payment.",9,0,false,"2026-11-01T00:00:00+00:00","2026-11-01T14:14:31+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},4,"Development","developpement","bg-warning\u002F10 text-warning","dev",[29],{"id":23,"name":24,"slug":25,"color":26,"icon":27},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fphp-8-1-minimum-preparer-boutiques-en-ligne-clients-poster.svg","A WooCommerce proposal published on 8 September 2026 considers raising the minimum PHP version to 8.1. Nothing is settled, but stores left on PHP 7.4 or 8.0 would stop receiving WooCommerce updates, with no alert. For an agency running dozens of stores, the question is simple: which versions run where, and in what order should you migrate? This guide gives the method, from listing versions to the checkpoints specific to payment, with a clear split of responsibilities between agency, client and host.",[35,39,42,52,55,80,112,115,119,122,130],{"type":36,"title":37,"body":38},"h2","WooCommerce may require PHP 8.1: what is actually proposed","On 8 September 2026, the WooCommerce engineering team published a proposal on its developer blog: raise the minimum PHP version to 8.1, starting with WooCommerce 11.5, then targeted for January 2027. A comment dated 29 September mentions a shift to WooCommerce 11.6. This is a proposal open for discussion, not a published decision: the target version, the timing and even the principle could still change. No firm cut-over date has been announced, and this article does not invent one.\n\nWhy care when nothing is settled? Because WooCommerce documentation currently says the plugin works with PHP 7.4 and above, and recommends PHP 8.3 or higher. The gap between that minimum and that recommendation is wide, and many client stores live in that gap. The proposal has at least one merit: it forces a question an agency should be asking anyway, namely which PHP version runs on each store, and who decides to change it.",{"type":36,"title":40,"body":41},"What would happen to a store left on PHP 7.4 or 8.0","According to the post, WordPress would by default stop offering the WooCommerce update to stores that do not meet the new requirement. Those stores would stay on their current version and keep receiving corrective releases for that branch. The post also states that PHP would not be changed on the owner's behalf, and that existing installations would not be deactivated.\n\nThe risk for an agency is therefore not a sudden outage but silence: a store that quietly stops receiving new versions, until the day a client asks for a feature or an extension itself demands a recent version. Nothing turns red and nobody is warned. Hence the value of taking stock beforehand rather than discovering it under pressure from a client request.",{"type":43,"title":44,"items":45},"ul","Why prepare now, even if the change is postponed or dropped",[46,47,48,49,50,51],"**PHP 7.4 is already unsupported** — WooCommerce documentation points out that PHP 7.4 reached end of life in November 2022, and PHP 8.0 has also left security support. Staying on them is a risk independent of WooCommerce.","**The official recommendation is above the minimum** — WooCommerce recommends PHP 8.3 or higher. Aiming only at 8.1 means preparing one more migration in the near term.","**A sample is not your portfolio** — the post puts stores tracked on PHP 7.4 at roughly 7 % and on PHP 8.0 at roughly 2 %, but that tracking is opt-in: an order of magnitude, not a census. Sites inherited from a previous provider are often further behind than average.","**Extensions often decide before WooCommerce does** — the post says so itself: raising the minimum does not guarantee that every extension, theme or snippet will work. Testing on a copy remains essential.","**A schedule you choose beats a schedule you suffer** — spreading migrations store by store, outside peak selling periods, costs less than a string of emergencies.","**The client sees the agency, not the platform** — if a store is stuck on its branch, they will come to you. Better to have announced it.",{"type":36,"title":53,"body":54},"First step: know the PHP version of every store","The general method for inventorying a fleet is described in \u003Ca href=\"\u002Fen\u002Fblog\u002Fphp-version-inventory-for-client-sites-an-agency-method\">the article on inventorying PHP versions\u003C\u002Fa>; it is not repeated here. For a WooCommerce store, three facts are enough at first: the PHP version, the WooCommerce version and the state of the extensions.\n\nThe most reliable source is the WooCommerce > Status page, \"Server environment\" section, \"PHP version\" row: this is the one WooCommerce documentation points to for checking the minimum. Over SSH, `wp --info` shows the PHP version used by WP-CLI, and `wp eval 'echo PHP_VERSION;'` the one WordPress actually runs. Be careful: on the command line the PHP binary can differ from the web server's, so when they disagree, the Status page is authoritative. In cPanel, the version is set per domain, as explained in \u003Ca href=\"\u002Fen\u002Fblog\u002Fchange-php-version-site-cpanel\">the guide to changing a site's PHP version\u003C\u002Fa>.\n\nRecord the result in a table: store, PHP version, WooCommerce version, blocking extensions, status, planned switch date. Handle stores on PHP 7.4 and 8.0 first, then the others.",{"type":56,"title":57,"steps":58},"steps","Migrating a store to a newer PHP version without breaking payment",[59,62,65,68,71,74,77],{"title":60,"body":61},"Back up and note the starting point","Back up the files and the database, then check that the backup restores. Note the domain's current PHP version: it is your way back.",{"title":63,"body":64},"List the extensions and the theme","`wp plugin list --fields=name,status,version,update` gives the inventory. For each extension and for the theme, note the PHP compatibility declared by the vendor (\"Requires PHP\" field or release notes). Update first whatever can be updated under the current PHP version.",{"title":66,"body":67},"Create a test copy","Same WooCommerce version, same extensions, copied database. Put the payment gateway in test or sandbox mode, and cut outgoing emails to real customers.",{"title":69,"body":70},"Change the PHP version on the copy","Aim for the version WooCommerce recommends if every extension supports it, otherwise the highest they accept. On the copy only, enable `define( 'WP_DEBUG_LOG', true );` to read errors without showing them to visitors.",{"title":72,"body":73},"Replay the checkout flow","Go through the checkpoints in the table below, from cart to confirmation, including a refund. Fix or replace any failing extension before going further.",{"title":75,"body":76},"Switch production","Pick a quiet slot, warn the client, change the domain's PHP version, clear caches (page, object, opcode), then reread WooCommerce > Status to confirm the effective version.",{"title":78,"body":79},"Monitor and keep the way back","Over the following days, watch the error log, incoming orders, emails and scheduled actions. Keep the previous version at hand until the store has gone through a full cycle of orders.",{"type":81,"title":82,"headers":83,"rows":87},"comparison","Checkpoints specific to a store",[84,85,86],"Checkpoint","What can break","How to verify",[88,92,96,100,104,108],[89,90,91],"Payment gateways","Module incompatible with the new version: payment declined or blank page at validation","Test order in the gateway sandbox, from cart to confirmation",[93,94,95],"Webhooks","Payment notifications not received or rejected, orders stuck \"on hold\" or pending","Delivery log on the gateway side, then the status of the test order",[97,98,99],"Scheduled tasks","Recurring actions failing: reminders, synchronisations, subscriptions","WooCommerce > Status > Scheduled Actions, list of failures; `wp cron event list`",[101,102,103],"Order emails","Customer confirmation or store notification missing or malformed","Test order, then receipt of both messages",[105,106,107],"Extensions touching orders","Custom feature that reads or edits orders and crashes","Create, edit and refund a test order; reread each extension's declared compatibility",[109,110,111],"Full checkout","Fatal error on a rarely tested step (promo code, shipping, customer account)","Full run with a promo code, two shipping methods and a new account",{"type":36,"title":113,"body":114},"Who owns what: agency, client, hosting","The agency keeps the client relationship and the schedule: it announces the maintenance window, decides which extensions to replace and signs off on the restart. Hosting provides the infrastructure: available PHP versions, choosing the version site by site, isolated cPanel accounts so that a switch on one store does not touch the others. On ServOrbit, the PHP version is chosen per domain; assisted migration and administration can be added as options, they are not included by default.\n\nA simple rule avoids misunderstandings: write down, before touching anything, who answers for what. The client's paid extensions, the custom theme, hosting, the payment gateway: each has an owner, and the PHP migration does not erase those boundaries.",{"type":116,"title":117,"body":118},"tip","Recommended order","Rehearse the procedure on a low-stakes store in the portfolio, then handle those on PHP 7.4 and 8.0, then the busiest ones, never during a peak selling period. Time each migration: that time is the basis of an honest quote for the next ones.",{"type":36,"title":120,"body":121},"Troubleshooting: what breaks most often after the change","After a switch, the same symptoms come back from one store to the next. Here are the five most frequent, with the first move for each.",{"type":43,"title":123,"items":124},"The five symptoms to know",[125,126,127,128,129],"**\"There has been a critical error on this website\"** — the WordPress message when an extension or the theme triggers a fatal error under the new version. Fix: put the previous PHP version back in cPanel, then read the copy's error log to identify the extension, and update or replace it.","**Orders stuck \"pending payment\"** — the gateway notification no longer arrives or is rejected. Fix: roll back, then check the webhook log on the gateway side and the module's declared PHP compatibility.","**Blank screen at checkout** — often a payment or shipping extension. Fix: roll back, then deactivate extensions one by one on the copy until the culprit is found.","**Order emails missing** — the sending test was not replayed after the switch. Fix: test order, read the mail log, check the sending extension.","**Failing scheduled actions** — recurring tasks that were silently crashing under the old version come to light, or the reverse. Fix: open the list of failed actions, read the message, update the extension involved.",{"type":36,"title":131,"body":132},"And if the change is postponed or dropped?","The plan remains useful. PHP 7.4 and 8.0 are already out of security support, the official recommendation is higher than 8.1, and the inventory you just built also serves for the next deadline, for example \u003Ca href=\"\u002Fen\u002Fblog\u002Fphp-82-end-of-life-planning-your-migration\">the migration checklist for a PHP branch reaching end of life\u003C\u002Fa> or the \u003Ca href=\"\u002Fen\u002Fblog\u002Fend-of-life-calendar-2027-hosting-agencies\">hosting end-of-life calendar\u003C\u002Fa>.\n\nWatch the WooCommerce developer blog and its documentation: that is where the decision, if it is made, will be published with its version and date. Until then, better to hold an up-to-date list and a rehearsed procedure than to discover the topic the day a store stops updating.","Every client store and its PHP version, under your control","Your clients' domains, hosting and cPanel accounts gathered in one space, with the PHP version chosen site by site and a view on renewals. The client relationship and the schedule stay with you.","Discover the agency space","\u002Fsolutions\u002Fagences",[138,155,175],{"id":139,"slug":140,"slugs":141,"title":145,"excerpt":146,"readTime":147,"views":148,"isPinned":19,"publishedAt":149,"updatedAt":150,"category":151,"categories":152,"featuredImage":30,"bgImage":31,"posterImage":154,"relatedSolution":30},206,"php-82-end-of-life-planning-your-migration",{"fr":142,"en":140,"ar":143,"es":144},"php-82-fin-de-vie-checklist-migration","نهاية-دعم-php-82-دليل-الترحيل","php-82-fin-de-vida-planificar-la-migracion","PHP 8.2 end of life: your migration checklist","PHP 8.2 reaches EOL on December 31, 2026. Inventory your stack, compare PHP versions, and follow a step-by-step migration checklist to PHP 8.3 or 8.4.",11,7,"2026-08-01T00:00:00+00:00","2026-09-07T11:26:10+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},[153],{"id":23,"name":24,"slug":25,"color":26,"icon":27},"\u002Fblog\u002Fcovers\u002Fphp-82-fin-de-vie-checklist-migration-poster.svg",{"id":156,"slug":157,"slugs":158,"title":162,"excerpt":163,"readTime":147,"views":18,"isPinned":19,"publishedAt":164,"updatedAt":165,"category":166,"categories":172,"featuredImage":30,"bgImage":31,"posterImage":174,"relatedSolution":30},508,"php-version-inventory-for-client-sites-an-agency-method",{"fr":159,"en":157,"ar":160,"es":161},"inventaire-versions-php-parc-sites-clients-agence","جرد-إصدارات-php-لمواقع-العملاء-منهج-للوكالات","inventario-de-versiones-php-de-sitios-cliente-metodo-de-agencia","PHP version inventory for client sites: an agency method","Build a register of the PHP version served by every client site across several hosts: access tiers, batch scripts, priority batches, client message, dated proof.","2026-10-27T00:00:00+00:00","2026-10-27T23:58:39+00:00",{"id":167,"name":168,"slug":169,"color":170,"icon":171},8,"Security & Monitoring","securite-monitoring","bg-rose-500\u002F10 text-rose-400","security",[173],{"id":167,"name":168,"slug":169,"color":170,"icon":171},"\u002Fblog\u002Fcovers\u002Finventaire-versions-php-parc-sites-clients-agence-poster.svg",{"id":176,"slug":177,"slugs":178,"title":182,"excerpt":183,"readTime":184,"views":18,"isPinned":19,"publishedAt":185,"updatedAt":186,"category":187,"categories":192,"featuredImage":30,"bgImage":31,"posterImage":194,"relatedSolution":30},503,"change-php-version-site-cpanel",{"fr":179,"en":177,"ar":180,"es":181},"changer-version-php-site-cpanel","تغيير-إصدار-php-للموقع-في-cpanel","cambiar-version-php-sitio-cpanel","Change your site's PHP version in cPanel","Choose your site's PHP version in cPanel: open the site page, the Settings tab, then pick the version you want from the list.",3,"2026-10-23T00:00:00+00:00","2026-10-24T03:34:36+00:00",{"id":188,"name":189,"slug":190,"color":191,"icon":190},12,"Guides","guides","bg-emerald-500\u002F10 text-emerald-400",[193],{"id":188,"name":189,"slug":190,"color":191,"icon":190},"\u002Fblog\u002Fcovers\u002Fchanger-version-php-site-cpanel-poster.svg",1793543003876]