<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NextGen Fusion]]></title><description><![CDATA[NextGen Fusion]]></description><link>https://nextgenfusion.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 13:47:01 GMT</lastBuildDate><atom:link href="https://nextgenfusion.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[WordPress Staging Site: How to Test Changes Safely]]></title><description><![CDATA[A WordPress staging site is a private copy of your live website where you test plugin updates, theme changes and new features before your customers ever…]]></description><link>https://nextgenfusion.hashnode.dev/wordpress-staging-site</link><guid isPermaLink="true">https://nextgenfusion.hashnode.dev/wordpress-staging-site</guid><category><![CDATA[WordPress]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[Devops]]></category><dc:creator><![CDATA[NextGen Fusion]]></dc:creator><pubDate>Wed, 18 Nov 2026 10:45:26 GMT</pubDate><content:encoded><![CDATA[<p>A WordPress staging site is a private copy of your live website where you test plugin updates, theme changes and new features before your customers ever see them. To test changes safely, you copy the live site to a separate address, lock that copy behind a password, switch off anything that talks to real customers (emails, payments, tracking), make and check your change there, and only then repeat it on the live site with a fresh backup in hand.</p>
<p>A site that breaks after a "quick" update on a Friday evening is avoidable pain. This guide walks through the steps we follow on client sites, the settings WordPress itself gives you for this, and the traps that catch store owners, such as duplicate renewal payments from a cloned WooCommerce shop.</p>
<h2>What is a WordPress staging site, and why bother?</h2>
<p>A staging site is a working clone of your live site: same theme, plugins, settings and a recent copy of the database, on a different address such as <code>staging.yourdomain.com</code>. Nobody outside your team should be able to reach it.</p>
<p>The point is simple. On a live site, every mistake is public. A plugin update that clashes with your theme, a PHP version change, a new checkout field or a page builder update can take down a contact form or a checkout without any warning on screen for you. On staging, the same mistake costs you nothing but a few minutes. You find the problem, fix it or roll it back, and your customers never notice.</p>
<p>It matters most if you run WooCommerce, use a lot of plugins, have custom code from a past developer, or have been burned by an update before. If your site is already struggling, start with our guides on <a href="https://www.nextgenfusion.in/blog/slow-wordpress-site/">fixing a slow WordPress site</a> and <a href="https://www.nextgenfusion.in/blog/wordpress-site-hacked/">what to do when a WordPress site is hacked</a>.</p>
<h2>How do you create a staging copy?</h2>
<p>There are three common routes. Which one fits depends on your hosting and how comfortable you are with files and databases.</p>
<p>Ways to create a WordPress staging site</p>
<table>
<thead>
<tr>
<th>Method</th>
<th>How it works</th>
<th>Good for</th>
<th>Watch out for</th>
</tr>
</thead>
<tbody><tr>
<td>Host's one-click staging</td>
<td>Your hosting control panel clones the site to a staging address and can often push changes back</td>
<td>Owners who want the fewest steps</td>
<td>Check what "push to live" overwrites; some tools copy the whole database, including orders</td>
</tr>
<tr>
<td>Staging or migration plugin</td>
<td>A plugin packages the files and database and restores them on a second install or subdomain</td>
<td>Hosts without built-in staging</td>
<td>Large sites can time out; the plugin itself becomes one more thing to keep updated</td>
</tr>
<tr>
<td>Manual copy or local setup</td>
<td>Copy files over SFTP, export and import the database, then update the site URL; or run it on a local machine</td>
<td>Developers and sites with custom code or version control</td>
<td>Easy to miss a step, such as replacing old URLs inside the database</td>
</tr>
</tbody></table>
<p>Whatever route you use, take a full backup of the live site first.</p>
<h2>Step 1: tell WordPress it is a staging site</h2>
<p>Since WordPress 5.5, core has a built-in way to label an install by environment. According to the <a href="https://developer.wordpress.org/reference/functions/wp_get_environment_type/">WordPress developer reference for wp_get_environment_type()</a>, you can set the type with a <code>WP_ENVIRONMENT_TYPE</code> constant (or a server environment variable of the same name), and the allowed values are <code>local</code>, <code>development</code>, <code>staging</code> and <code>production</code>. If nothing is set, WordPress treats the site as <code>production</code>.</p>
<p>On the staging copy, add one line to <code>wp-config.php</code>, above the line that says to stop editing:</p>
<pre><code>define( 'WP_ENVIRONMENT_TYPE', 'staging' );
</code></pre>
<p>This does not change anything visible by itself. What it does is give plugins, themes and your own code a standard way to know where they are running. The same reference asks hosts that offer staging to set this value to <code>staging</code>, and notes that when the type is <code>development</code>, WordPress turns on <code>WP_DEBUG</code> if you have not defined it. A well-built plugin can then, for example, skip sending live emails on a staging copy.</p>
<p>Only those four values are accepted; anything else falls back to <code>production</code>.</p>
<h2>Step 2: keep the staging site out of Google</h2>
<p>An open staging copy is a duplicate of your whole site. You do not want it in search results or customers placing orders on it.</p>
<p>The safest option is a password. Google's page on <a href="https://developers.google.com/search/docs/crawling-indexing/control-what-you-share">controlling what you share with Google Search</a> says that password-protecting content ensures only authorised users can access it, and that this also keeps it out of Google Search, removing it over time if it has already appeared. Many hosting panels let you add HTTP authentication to a subdomain; a login-only maintenance plugin also works.</p>
<p>As a second layer, tick <strong>Settings &gt; Reading &gt; Discourage search engines from indexing this site</strong> on the staging copy. Google also explains that a <code>noindex</code> rule keeps a page out of results, although the page can still be reached by anyone who has the link. That is why noindex alone is not enough for staging: it hides the site from search, not from people.</p>
<p>The classic mistake is the reverse. When you copy staging back to live, or rebuild live from staging, the "discourage search engines" box comes with it. Make unticking it on the live site part of your go-live checklist, every time.</p>
<h2>Step 3: stop staging from talking to real customers</h2>
<p>A cloned site does not know it is a clone. It has the same customer list, the same email settings and the same payment keys. Left alone, it can send real emails and, on a store, try to take real payments.</p>
<ul>
<li><strong>Emails:</strong> install an email-logging or email-blocking plugin on staging, or point your SMTP settings at a test inbox, so order confirmations and password resets do not reach real people.</li>
<li><strong>Payments:</strong> switch every payment gateway to its test or sandbox mode, using test keys, before you place a single order.</li>
<li><strong>Scheduled jobs:</strong> look at backups, newsletter sends, stock syncs and marketplace feeds. A staging copy running the same jobs can overwrite live data in a connected system.</li>
</ul>
<h3>A note for WooCommerce Subscriptions stores</h3>
<p>If you sell subscriptions, there is one built-in safety net worth knowing about. The <a href="https://woocommerce.com/document/subscriptions/subscriptions-handles-staging-sites/">WooCommerce Subscriptions guide to staging sites</a> explains that the extension records the URL where it was first activated, treats that as the live site, and switches to staging mode when the site URL changes. In staging mode it uses manual renewals and disables subscription emails, which prevents duplicate payments from a clone.</p>
<p>The catch is the order of events. The same guide says that if you first activate Subscriptions on a staging site, it will treat that staging site as live. So activate it on the live site first, then create staging from the live database. And do not press the button that enables automatic payments on staging unless you really mean to.</p>
<h2>Step 4: make and test your change properly</h2>
<p>With staging locked down, make one change at a time. Updating twelve plugins in one go and then finding the site broken tells you nothing about which one caused it.</p>
<ol>
<li>Note the current versions of WordPress, PHP, your theme and the plugins you are changing.</li>
<li>Apply the change: an update, a new plugin, a theme edit or a PHP version switch.</li>
<li>Check the pages that make you money, not just the home page: contact and quote forms, product pages, cart, checkout, account login and any booking flow.</li>
<li>Place a test order or send a test enquiry from start to finish, using test payment mode.</li>
<li>Look at the site on a phone, not just a desktop browser.</li>
<li>Check for errors. On staging it is fine to turn on debug logging and read the log after testing.</li>
<li>Run a quick speed test on key pages; our <a href="https://www.nextgenfusion.in/blog/woocommerce-speed-optimisation/">WooCommerce speed optimisation guide</a> lists what to look at on a store.</li>
</ol>
<p>If something breaks, roll it back on staging, find a fix and test again.</p>
<h2>Step 5: push the change to the live site</h2>
<p>This is where most staging accidents happen.</p>
<p>For plugin, theme and core updates, the simplest safe approach is usually to repeat the same tested update on the live site, in the same order, after a fresh backup. You already know it works.</p>
<p>Copying the full staging database over live is risky for any site that changes while you test. On a WooCommerce store, orders, customers and stock levels on live keep changing. Overwrite the live database with a staging copy from two days ago and those orders are gone. If your host's push tool offers a "files only" option or lets you exclude tables, use it for anything other than a brand new site.</p>
<p>Once live, repeat the checks: forms, checkout, login, mobile and the search engine visibility setting.</p>
<h2>Common staging mistakes to avoid</h2>
<ul>
<li><strong>A staging site anyone can open:</strong> no password, and it ends up indexed or used by real customers.</li>
<li><strong>Live payment keys on staging:</strong> a test order becomes a real charge.</li>
<li><strong>Forgetting the copy exists:</strong> an old staging site with outdated plugins is an easy way into your server. Delete staging copies you no longer use, or keep them updated.</li>
<li><strong>Leaving "discourage search engines" ticked on live:</strong> the most common reason a rebuilt site quietly drops out of search.</li>
</ul>
<h2>Frequently asked questions</h2>
<h3>Do small WordPress sites really need a staging site?</h3>
<p>If the site brings in leads or sales, yes, at least for bigger changes such as theme updates, page builder updates or a PHP version switch. For a simple brochure site you might test minor plugin updates directly after a backup, but staging removes the guesswork for anything larger.</p>
<h3>Will a staging site hurt my search rankings?</h3>
<p>Not if it is password-protected. Google says password protection keeps content out of its search results. The real risk is an open staging copy that gets indexed as a duplicate of your site, which is why the password matters more than the noindex setting.</p>
<h3>Can I build a new design on staging and launch it later?</h3>
<p>Yes. On a live store, plan the launch so you copy theme files and settings across while leaving live orders and customer tables untouched.</p>
<h3>How often should I refresh the staging copy?</h3>
<p>Refresh it from live before any significant round of testing. A months-old copy may run different versions from live, so its results tell you little.</p>
<h2>Conclusion</h2>
<p>A staging site is the cheapest insurance a WordPress owner can buy: copy the live site, lock it behind a password, label it with <code>WP_ENVIRONMENT_TYPE</code>, switch off real emails and payments, test one change at a time, and move only the tested change to live. If you would rather not do this yourself, we have handled updates and rebuilds across 100+ projects delivered, and our <a href="https://www.nextgenfusion.in/services/website-maintenance-services/">website maintenance service</a> covers tested updates as standard. Message us on WhatsApp at +91 73482 28167 and you get a fixed written quote within one working day.</p>
<hr />
<p><em>Originally published on the <a href="https://www.nextgenfusion.in/blog/wordpress-staging-site-test-changes/">NextGen Fusion blog</a>.</em></p>
]]></content:encoded></item><item><title><![CDATA[WooCommerce Orders Stuck on Pending Payment: How to Fix]]></title><description><![CDATA[WooCommerce orders stuck on pending payment almost always mean one of two things: the customer never finished paying, or they did pay and the payment…]]></description><link>https://nextgenfusion.hashnode.dev/woocommerce-orders-stuck-pending-payment</link><guid isPermaLink="true">https://nextgenfusion.hashnode.dev/woocommerce-orders-stuck-pending-payment</guid><category><![CDATA[ecommerce]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[woocommerce]]></category><category><![CDATA[WordPress]]></category><dc:creator><![CDATA[NextGen Fusion]]></dc:creator><pubDate>Wed, 18 Nov 2026 10:44:02 GMT</pubDate><content:encoded><![CDATA[<p>WooCommerce orders stuck on pending payment almost always mean one of two things: the customer never finished paying, or they did pay and the payment gateway's confirmation never reached your store. To fix it, check the order notes, match the order against your gateway dashboard, and then repair the webhook or callback that should move paid orders to Processing. Do not ship or ask the customer to pay again until you know which case you are in.</p>
<p>It is a stressful problem because money and stock are both involved, but it is very findable if you work in order. This guide walks through what the status means, how to tell an abandoned order from a paid one, and the fixes that apply to most gateways.</p>
<h2>What does "Pending payment" mean in WooCommerce?</h2>
<p>According to the WooCommerce <a href="https://woocommerce.com/document/managing-orders/order-statuses/">order statuses documentation</a>, Pending payment means the order has been received but no payment has been made, and such orders are generally awaiting customer action. The normal path for a card or UPI payment is Pending payment, then Processing once the gateway confirms the money, then Completed once you have shipped.</p>
<p>The status sits next to a few others that store owners often mix up. Here is how they differ, based on the same documentation:</p>
<p>WooCommerce order statuses that get confused with Pending payment</p>
<table>
<thead>
<tr>
<th>Status</th>
<th>What it means</th>
<th>What you should do</th>
</tr>
</thead>
<tbody><tr>
<td>Pending payment</td>
<td>Order received, no payment made yet</td>
<td>Check whether the customer actually paid before doing anything</td>
</tr>
<tr>
<td>On hold</td>
<td>Awaiting payment confirmation; stock is reduced</td>
<td>Confirm payment by hand (common with bank transfer), then update the status</td>
</tr>
<tr>
<td>Failed</td>
<td>Payment failed or was declined</td>
<td>Read the decline reason in the order notes; stock is returned if it was reduced</td>
</tr>
<tr>
<td>Processing</td>
<td>Payment received and stock reduced</td>
<td>Pack and ship, then mark Completed</td>
</tr>
<tr>
<td>Draft</td>
<td>Temporary checkout record from the block-based checkout</td>
<td>Nothing; WooCommerce cleans up inactive drafts with a daily task</td>
</tr>
</tbody></table>
<p>A single pending order is not a fault; a shopper who closes the payment tab leaves one behind. The problem is pending orders where the customer says they paid, or where your gateway shows money WooCommerce does not.</p>
<h2>Step 1: Did the customer actually pay?</h2>
<p>Start with the money, not the plugin settings. The WooCommerce <a href="https://woocommerce.com/document/managing-orders/troubleshooting-orders/">troubleshooting orders guide</a> gives a clear order of checks for a payment that times out or stays pending:</p>
<ol>
<li>Note the order number, its status, the time of the attempt and any message the customer saw at checkout.</li>
<li>Open the order and read the order notes for a transaction ID, decline reason, timeout or status change.</li>
<li>Log in to your payment gateway dashboard and search for a matching transaction.</li>
</ol>
<p>The guide is firm on one point that saves a lot of trouble: if the customer is unsure whether they were charged, do not let them retry until you have confirmed the first attempt did not create a charge or authorisation.</p>
<p>Either there is no matching transaction (the payment was abandoned or failed early), or there is a successful charge WooCommerce never recorded. The second one is the real bug.</p>
<h2>Step 2: Read the order notes properly</h2>
<p>Gateway plugins write timestamped errors, decline reasons and status updates into the order notes. WooCommerce's guide points out that missing notes are a clue in themselves. If a paid order has no payment notes at all, the gateway most likely failed to talk back to your store, or the payment process was interrupted before it finished.</p>
<p>What we look for in practice:</p>
<ul>
<li><strong>A transaction ID with no status change after it.</strong> The gateway created the payment, but the confirmation step did not land.</li>
<li><strong>A decline or error message.</strong> This is a real failed payment, not a sync problem. Contact the customer with a fresh payment link.</li>
<li><strong>No gateway notes at all.</strong> Treat this as a communication problem between the gateway and your site, and move to the webhook checks below.</li>
</ul>
<p>If your gateway plugin has a debug or logging option, turn it on, place one test order and read the new entries under WooCommerce &gt; Status &gt; Logs. The troubleshooting guide recommends switching verbose logging off again once testing is done.</p>
<h2>Step 3: Fix the webhook or callback</h2>
<p>Most online gateways move an order to Processing by sending your site a message after payment, called a webhook, callback or notification. If it never arrives, or your site rejects it, the order sits on Pending payment while the money sits in your gateway account.</p>
<p>WooCommerce's guide notes that some gateways need webhooks set up by hand while others handle it automatically, and gives Stripe for WooCommerce as an example that needs manual webhook configuration. Whatever gateway you use, check these in its dashboard and plugin settings:</p>
<ul>
<li><strong>The webhook URL points at the live domain.</strong> After a domain change, an HTTP to HTTPS move or a switch from www to non-www, old webhook URLs are a frequent cause.</li>
<li><strong>Live and test keys are not mixed.</strong> A webhook registered only in test mode never hears about real orders.</li>
<li><strong>The gateway shows successful deliveries.</strong> If your gateway keeps a webhook log, error responses there mean your site is receiving the call but refusing it.</li>
<li><strong>Nothing on your server is blocking the request.</strong> Security plugins, firewalls and some caching setups can block or interfere with incoming requests from the gateway. Check them if the gateway log shows errors or timeouts.</li>
</ul>
<p>The guide's advice for a charge that succeeded while the order stayed pending is to follow your gateway's own steps for checking or re-sending the webhook or callback, then reconcile the order before fulfilling it.</p>
<p>If you are still choosing a provider, our guide to <a href="https://www.nextgenfusion.in/blog/woocommerce-payment-gateway-india/">picking a WooCommerce payment gateway in India</a> covers what to compare before you commit.</p>
<h2>Step 4: If you still use PayPal Standard, check IPN</h2>
<p>Older stores sometimes still run PayPal Standard, which WooCommerce now describes as deprecated and hidden by default. It confirms payments through PayPal Instant Payment Notifications (IPN), and WooCommerce's <a href="https://woocommerce.com/document/paypal-standard/">PayPal Standard documentation</a> is direct about the symptom: if you are getting payments but orders stay pending, the IPN is failing.</p>
<p>The checks it lists are:</p>
<ul>
<li>In your PayPal account, set the IPN URL to <code>https://example.com/?wc-api=WC_Gateway_Paypal</code>, with your own domain in place of example.com, and make sure receiving IPN messages is switched on.</li>
<li>Make sure the email address in the WooCommerce PayPal settings is your primary PayPal email. If it does not match the address IPN sends back, the response is rejected.</li>
<li>Check the IPN history page in your PayPal account to see whether messages were sent and what happened to them.</li>
<li>If everything looks right, speak to your host. The documentation notes that some hosts are known to have problems with IPN.</li>
</ul>
<h2>Step 5: Stop paid orders being cancelled while you investigate</h2>
<p>There is a second trap here. WooCommerce's order statuses documentation explains that when the Hold Stock setting is on, WooCommerce automatically cancels eligible Pending payment orders created at checkout once the configured time limit passes, and releases the held stock. If paid orders are stuck as pending, they can be cancelled before you reconcile them.</p>
<p>The PayPal Standard documentation suggests a workaround while you debug: go to WooCommerce &gt; Settings &gt; Products &gt; Inventory and leave the "Hold Stock (minutes)" field empty, so unpaid orders are not cancelled automatically. Remember to put the value back once the fix is confirmed, otherwise abandoned orders will hold stock indefinitely.</p>
<h2>Step 6: Reconcile the orders you already have</h2>
<p>Once the cause is fixed, clear the backlog carefully:</p>
<ol>
<li>Export or list every Pending payment order from the affected period.</li>
<li>Match each one against the gateway dashboard by amount, time and customer email.</li>
<li>For matched orders, re-send the webhook from the gateway if you can. If not, add an order note with the transaction ID and change the status to Processing by hand.</li>
<li>For unmatched orders, leave them pending or cancel them. If stock was held, check it has been released.</li>
<li>Email any customer who was left waiting to confirm their order.</li>
</ol>
<p>Then place a real low-value test order on the live site and watch it move from Pending payment to Processing on its own.</p>
<h2>How do you stop it happening again?</h2>
<p>Stuck orders often start after a change such as a plugin update, a new security plugin, a domain move or a hosting migration. A few habits help:</p>
<ul>
<li>Test payment changes on a staging copy first. Our guide to <a href="https://www.nextgenfusion.in/blog/wordpress-staging-site-test-changes/">setting up a WordPress staging site</a> explains how. WooCommerce also warns that a staging site that is not fully isolated can process live orders by accident, so keep staging on test keys.</li>
<li>Re-check webhook URLs after any change to the domain, SSL or www setting.</li>
<li>Keep checkout fast. WooCommerce's troubleshooting guide notes that slow server responses can lead customers to resubmit the checkout form and create duplicate orders. Our <a href="https://www.nextgenfusion.in/blog/woocommerce-speed-optimisation/">WooCommerce speed guide</a> covers where to start.</li>
</ul>
<p>When we built the WooCommerce store for <a href="https://www.nextgenfusion.in/work/mahhika/">Mahhika, a wedding fashion brand</a>, the checkout supported multiple payment gateways. In that kind of setup, every gateway's confirmation path needs testing before launch.</p>
<h2>Frequently asked questions</h2>
<h3>Why are my WooCommerce orders pending when the customer has paid?</h3>
<p>Usually the gateway took the payment but its confirmation (a webhook, callback or PayPal IPN) did not reach your store or was rejected. Check the order notes, find the transaction in the gateway dashboard, then repair or re-send the webhook. Confirm the payment before you ship.</p>
<h3>Should I change pending orders to Processing by hand?</h3>
<p>Only after you have matched each order to a successful transaction in your gateway dashboard. Add the transaction ID as an order note when you do it. Changing statuses without checking risks shipping orders that were never paid.</p>
<h3>Do pending payment orders cancel themselves?</h3>
<p>Yes, if the Hold Stock setting is on. WooCommerce cancels eligible pending orders created at checkout after the time limit you set and releases their stock. Leave that field empty temporarily if you are investigating paid orders stuck as pending.</p>
<h3>Is a pending order with bank transfer a problem?</h3>
<p>Not necessarily. WooCommerce's guidance says offline methods such as direct bank transfer or cheque need you to confirm the payment yourself before moving the order on. Check your bank statement, then update the status.</p>
<h2>Conclusion</h2>
<p>If your WooCommerce orders are stuck on pending payment, work from the money outwards: confirm the charge in the gateway, read the order notes, fix or re-send the webhook, pause automatic cancellation while you reconcile, and finish with a live test order. If you would rather have someone check it for you, our <a href="https://www.nextgenfusion.in/services/ecommerce-web-development-services/">ecommerce development team</a> has handled payment setups across 100+ projects delivered. Message us on WhatsApp at +91 73482 28167 and you get a fixed written quote within one working day.</p>
<hr />
<p><em>Originally published on the <a href="https://www.nextgenfusion.in/blog/woocommerce-orders-stuck-pending-payment/">NextGen Fusion blog</a>.</em></p>
]]></content:encoded></item><item><title><![CDATA[Shopify Discount Code Not Working? Causes and Fixes]]></title><description><![CDATA[A Shopify discount code that is not working is almost always being blocked by one of its own settings, not by a bug. The usual causes are active dates in…]]></description><link>https://nextgenfusion.hashnode.dev/shopify-discount-code-not-working</link><guid isPermaLink="true">https://nextgenfusion.hashnode.dev/shopify-discount-code-not-working</guid><category><![CDATA[shopify]]></category><category><![CDATA[ecommerce]]></category><category><![CDATA[Web Development]]></category><dc:creator><![CDATA[NextGen Fusion]]></dc:creator><pubDate>Wed, 18 Nov 2026 04:55:05 GMT</pubDate><content:encoded><![CDATA[<p>A Shopify discount code that is not working is almost always being blocked by one of its own settings, not by a bug. The usual causes are active dates in the wrong time zone, a minimum purchase the cart does not meet, an eligibility or market restriction, a used-up usage limit, or a combination rule that lets another discount win. Open the discount in your admin, check those settings in that order, and then test the code in a real checkout before you tell customers it is fixed.</p>
<p>This matters most in a sale week like Diwali, when a broken code turns into abandoned carts and angry messages within minutes. Below is the order I check things in, with the exact Shopify rules behind each step.</p>
<h2>What does the customer actually see?</h2>
<p>Start with the exact message, because it narrows the cause straight away. Ask for a screenshot, or reproduce it in a private window with the same cart.</p>
<ul>
<li><strong>"Discount couldn't be used with your existing discounts"</strong> is a combination problem. Shopify shows this message when a customer enters codes that can't be combined, according to its <a href="https://help.shopify.com/en/manual/discounts/discount-combinations">guide to combining discounts</a>.</li>
<li><strong>"You already have a better combination"</strong> usually appears when a shipping code meets a product or order discount that is already applied.</li>
<li><strong>The code is accepted but the price does not change</strong>, or another discount appears instead. That points to best-discount selection or to products that are not covered by the code.</li>
<li><strong>The code is rejected outright</strong>. Look at dates, eligibility, minimums and usage limits first.</li>
</ul>
<h2>Is the discount active right now, in your store's time zone?</h2>
<p>Shopify's <a href="https://help.shopify.com/en/manual/discounts/discount-types/percentage-fixed-amount">amount off discounts documentation</a> says a discount starts and ends according to the time zone selected in your Shopify admin. If your store is set to a different zone from your customers, a code scheduled for "Dhanteras morning" can go live hours early or late. The same applies to end dates: a sale that should run until midnight in India can stop at the wrong moment if the store clock is set elsewhere.</p>
<p>Check three things on the discount page: the status says Active rather than Scheduled or Expired, the start date and time are in the past, and the end date has not passed. Then check the store time zone under Settings. If you want a code valid for a single day, Shopify's instructions are to select the same calendar day as both start and end date.</p>
<h2>Does the cart meet the minimum requirement?</h2>
<p>Minimums cause more "not working" complaints than anything else, because customers rarely read the small print. The rules are stricter than most owners expect:</p>
<ul>
<li>The minimum purchase amount counts product prices only. Shipping and taxes are not included.</li>
<li>For a product discount, only the selected products or collections count towards the minimum, and they count at their price after any earlier product discounts.</li>
<li>For an order discount, both the total before product discounts and the subtotal after product discounts must meet the minimum.</li>
<li>Purchased gift cards don't count unless you selected the gift card product, and gift cards or store credit used as payment don't affect the minimum.</li>
</ul>
<p>So a customer with a cart full of items, of which only some sit in the discounted collection, may never reach the threshold even though the cart total looks high enough. If that keeps happening, say on the banner and product page exactly which items count. On our <a href="https://www.nextgenfusion.in/work/vashtaraheaven/">Vashtara Heaven Shopify kidswear store</a>, the free-shipping threshold is shown as a site-wide banner rather than surfacing as a checkout surprise, which is the same principle.</p>
<h2>Is the customer eligible, and is the code used up?</h2>
<p>In the Eligibility section a discount can be open to all customers, to specific customers, to customer segments, or to specific markets. A code limited to a segment will fail for a shopper who is not logged in as a member of it, and a code limited to one market will fail for a shopper browsing another market.</p>
<p>Next, look at Maximum discount uses. A total usage limit stops the code once that number of uses is reached across all customers. "Limit to one per customer" tracks the customer's email address or phone number, so a repeat buyer using the same email will be refused even with a fresh browser.</p>
<p>Finally, check value and scope. Shopify notes that discounts with a zero value might not work correctly at checkout and suggests at least 1% or the smallest currency unit. Also confirm the Applies to section: a code set to Specific collections will not touch products outside them.</p>
<h2>Is another discount winning the combination?</h2>
<p>Discounts don't combine automatically. Each one has a Combinations section where you tick which classes it may combine with: product, order or shipping discounts. Two discounts only stack when the setting on each of them allows it. When they can't combine, Shopify applies whichever discount is best for the customer, so your code may look "ignored" when an automatic discount simply gives a bigger saving.</p>
<p>Shopify applies discounts in a fixed order: product discounts first, then order discounts on the reduced subtotal, then shipping discounts last. Here is what can and can't stack, based on Shopify's combination table:</p>
<p>Which Shopify discount classes can combine</p>
<table>
<thead>
<tr>
<th>Combination</th>
<th>Supported?</th>
<th>What to check</th>
</tr>
</thead>
<tbody><tr>
<td>Product discount + product discount on different items</td>
<td>Yes, all plans</td>
<td>Both discounts allow product combinations</td>
</tr>
<tr>
<td>Product or order discount + free shipping</td>
<td>Yes, all plans</td>
<td>Both discounts allow the other's class</td>
</tr>
<tr>
<td>Product discount + order discount</td>
<td>Yes, eligible stores</td>
<td>No checkout.liquid customisations, Checkout Extensibility in use</td>
</tr>
<tr>
<td>Order discount + order discount</td>
<td>Yes, eligible stores</td>
<td>Same eligibility as above</td>
</tr>
<tr>
<td>Two product discounts on the same item</td>
<td>Shopify Plus only</td>
<td>Reciprocal tags on both discounts</td>
</tr>
<tr>
<td>Shipping discount + shipping discount</td>
<td>No</td>
<td>Only one shipping discount per order</td>
</tr>
</tbody></table>
<p>There are also hard limits: a store can have at most 25 active automatic discounts, including app-based ones, and a customer can use at most 5 product or order codes plus 1 shipping code on the same order. If you run lots of overlapping sale offers, you can hit these during a festival week without noticing.</p>
<h3>Buy X get Y and shipping codes</h3>
<p>On every plan except Shopify Plus, products in a Buy X get Y offer can't receive further product discounts. If a customer enters a code that touches those products, Shopify applies the best overall value instead. Keep BOGO offers and code offers on different collections, or use an order discount instead.</p>
<p>Shipping codes have their own quirk. When a shipping discount can't combine with a product or order discount already in the cart, the product or order discount takes priority, because the discounted cart value is used to work out shipping rates. Shopify's fix is to allow both discounts to combine.</p>
<h2>Is the order coming through a channel that supports it?</h2>
<p>Discount combinations only work on orders through the Online Store, the Storefront API and Shopify POS. They are not available on checkouts on Facebook, Instagram, Google or other external checkout platforms. If a customer says the code worked on your website but not when buying through a social shop, that is the reason, not a fault in the code.</p>
<p>Headless storefronts are another case. If your shop runs on a custom front end, the developer has to pass the code to the cart through the Storefront API, so test it there separately rather than assuming the theme behaviour carries over. We covered when that set-up makes sense in our guide to <a href="https://www.nextgenfusion.in/blog/headless-shopify-when-to-go-headless/">going headless with Shopify</a>.</p>
<h2>Could an app, Script or checkout customisation be blocking it?</h2>
<p>When every setting looks right, look at what else touches checkout. Shopify's troubleshooting steps are:</p>
<ol>
<li>Check for an active automatic discount that applies to the same products and conflicts with the code.</li>
<li>If you use Shopify Scripts, review active scripts under Settings, then Checkout, for conditions that reject codes.</li>
<li>Temporarily remove discount or checkout apps one at a time to see if the problem stops, then reinstall them.</li>
<li>For app-created discounts, ask the app developer whether the app supports discount combinations, because that is on their side.</li>
</ol>
<h2>How to test discount codes before a sale goes live</h2>
<p>Shopify suggests testing combinations by going through checkout, entering your codes and checking the totals, then closing the page before paying. I run this short routine for every sale code, ideally the day before launch:</p>
<ol>
<li>Cart with only eligible products: the code applies and the total is what you expect.</li>
<li>Cart with an excluded product added: only the eligible items are discounted.</li>
<li>Cart just under and just over the minimum: the code fails and then works.</li>
<li>The code together with any automatic discount and any free shipping offer: the right combination wins.</li>
<li>A logged-out customer, a customer outside the segment, and a different market address if you sell internationally.</li>
<li>The code on mobile, and once more after the start time passes.</li>
</ol>
<p>If you are also changing themes or apps during the sale week, do it on a copy first. The same logic is in our post on <a href="https://www.nextgenfusion.in/blog/shopify-cart-abandonment/">reducing Shopify cart abandonment</a>, since a code that fails at checkout is one of the fastest ways to lose a cart.</p>
<h2>Frequently asked questions</h2>
<h3>Why does my Shopify discount code say it can't be combined?</h3>
<p>That message appears when the discounts in the cart are not set to combine with each other's class. Open each discount and tick the matching classes in its Combinations section. Also check whether an automatic discount is already applying to the same products.</p>
<h3>Why did a different discount replace my code?</h3>
<p>When two discounts can't combine, Shopify automatically applies the one that gives the customer the best saving. If two product discounts have the same value on the same items, it may pick either one. This is expected, so allow combinations if you want both to apply.</p>
<h3>Can customers use a discount code on Instagram or Facebook checkout?</h3>
<p>Discount combinations are not available for checkouts on Facebook, Instagram, Google or other external platforms. For sale offers that rely on stacking, send shoppers to your own online store, where combinations are supported.</p>
<h2>Conclusion</h2>
<p>When a Shopify discount code is not working, check it in this order: active dates and store time zone, minimum requirements, eligibility and usage limits, value and scope, combination settings, sales channel, and finally apps or Scripts. Test each sale code in a real checkout before launch, and keep your offers simple enough that customers understand which items qualify. If you want a second pair of eyes on your store before a sale, or help with <a href="https://www.nextgenfusion.in/services/shopify-development-services/">Shopify development</a>, message us on WhatsApp at +91 73482 28167 and you get a fixed written quote within one working day.</p>
<hr />
<p><em>Originally published on <a href="https://www.nextgenfusion.in/blog/shopify-discount-code-not-working/">NextGen Fusion</a>.</em></p>
]]></content:encoded></item><item><title><![CDATA[WooCommerce Emails Not Sending? How to Find and Fix It]]></title><description><![CDATA[When WooCommerce emails are not sending, the cause is usually one of three things: the order never reached a status that triggers an email, the email type…]]></description><link>https://nextgenfusion.hashnode.dev/woocommerce-emails-not-sending</link><guid isPermaLink="true">https://nextgenfusion.hashnode.dev/woocommerce-emails-not-sending</guid><category><![CDATA[Web Development]]></category><category><![CDATA[email]]></category><category><![CDATA[woocommerce]]></category><category><![CDATA[WordPress]]></category><dc:creator><![CDATA[NextGen Fusion]]></dc:creator><pubDate>Wed, 18 Nov 2026 04:49:15 GMT</pubDate><content:encoded><![CDATA[<p>When WooCommerce emails are not sending, the cause is usually one of three things: the order never reached a status that triggers an email, the email type is switched off, or WooCommerce did send it but your server's mail setup failed or the message was filtered as spam. WooCommerce now logs every transactional email attempt, so you can tell which of the three it is in a few minutes instead of guessing. Check the order status first, then the email settings, then the <code>transactional-emails</code> log, and only then move on to SMTP and domain authentication.</p>
<p>Customers who get no confirmation tend to message the store or order twice, and owners miss new orders. Below is the order I work through on client stores, with the WooCommerce and Gmail rules behind each step.</p>
<h2>Is the problem "not sent" or "not received"?</h2>
<p>"Not sent" means WooCommerce never handed the email to your site's mail system, or the handover failed. "Not received" means it left your site but was rejected or filtered as spam on the way.</p>
<p>WooCommerce's own <a href="https://woocommerce.com/document/email-faq/">email troubleshooting guide</a> points out that the plugin sends mail through <code>wp_mail()</code>, the core WordPress mail function. So in many cases WooCommerce created the email correctly, and the real fault sits with the hosting mail function or a later step. The guide also says that, often, email issues are deliverability issues: the server sends the message, but it is not received.</p>
<h2>Step 1: Check the order status before anything else</h2>
<p>WooCommerce only sends the new order and processing emails when an order moves into the right status. According to the WooCommerce guide, if an order is still in <strong>Pending payment</strong>, no email is triggered. That is the most common "emails not sending" report I see, and it is not an email problem at all.</p>
<ul>
<li><strong>The payment was not completed.</strong> The customer abandoned the external payment page or the card was declined. No email is expected here.</li>
<li><strong>The payment was completed but the order is still pending.</strong> The payment gateway is not updating your site. WooCommerce says to treat this as a gateway issue and work through the gateway's own documentation. Our guide to <a href="https://www.nextgenfusion.in/blog/woocommerce-orders-stuck-pending-payment/">WooCommerce orders stuck on pending payment</a> covers webhooks, callbacks and the order notes to read.</li>
<li><strong>An error stopped the status change.</strong> A conflict with a theme, custom code or another plugin can throw an error before the status changes. WooCommerce suggests checking its logs for fatal errors and testing with other plugins disabled and a default theme active.</li>
</ul>
<p>If your paid orders show <strong>Processing</strong> and the emails still do not arrive, move on to Step 2.</p>
<h2>Step 2: Confirm the email is switched on</h2>
<p>Every WooCommerce email has its own on/off switch. Go to <strong>WooCommerce &gt; Settings &gt; Emails</strong>, open the email in question (for example "Processing order" for customers or "New order" for the shop owner), and make sure <strong>Enable this email notification</strong> is ticked. For the admin "New order" email, also check that the recipient field holds an address someone actually reads.</p>
<p>These switches get changed more often than owners think, for example by an email customiser plugin or someone testing on the live store. If the email is enabled and still not going out, WooCommerce says a conflict is the likely cause.</p>
<h2>Step 3: Read the transactional email log</h2>
<p>This is the step that saves the most time. WooCommerce automatically logs each transactional email attempt. To read it:</p>
<ol>
<li>Place a test order or trigger the email you want to check.</li>
<li>Go to <strong>WooCommerce &gt; Status &gt; Logs</strong>.</li>
<li>Open or filter the log source named <code>transactional-emails</code>.</li>
<li>Find the entry for that email type and order.</li>
</ol>
<p>Each entry records one of four outcomes. Here is what each one means and where to go next, based on the WooCommerce guide:</p>
<p>WooCommerce transactional email log outcomes</p>
<table>
<thead>
<tr>
<th>Log outcome</th>
<th>Log level</th>
<th>What it means</th>
<th>Next step</th>
</tr>
</thead>
<tbody><tr>
<td>Sent</td>
<td>INFO</td>
<td>WooCommerce handed the email to the mail system successfully</td>
<td>Treat it as a delivery problem (Steps 5 and 6)</td>
</tr>
<tr>
<td>Failed</td>
<td>WARNING</td>
<td>The site's mail-sending process returned an error, usually with a reason</td>
<td>Fix the hosting or mail setup (Step 4)</td>
</tr>
<tr>
<td>Disabled</td>
<td>NOTICE</td>
<td>The email type is turned off in the email settings</td>
<td>Enable it (Step 2)</td>
</tr>
<tr>
<td>Skipped</td>
<td>NOTICE</td>
<td>A required condition was missing, such as no recipient</td>
<td>Add the missing detail, such as the recipient</td>
</tr>
</tbody></table>
<p>For order emails, sent and failed attempts are also added as private order notes, so you can see them on the order screen itself. Disabled and skipped emails appear only in the log. If you expected an entry and there is none at all, WooCommerce says to look for fatal errors and conflicts.</p>
<p>If entries are missing, check <strong>WooCommerce &gt; Status &gt; Logs &gt; Settings</strong> is not hiding INFO or NOTICE levels. Also, the log covers WooCommerce transactional emails only. WordPress password reset emails and other admin emails might not appear there, so for those you need your SMTP provider's logs or a mail logging plugin.</p>
<h2>Step 4: Fix a "Failed" result with proper SMTP</h2>
<p>A failed entry usually includes the reason reported by WordPress or the mail service, which tells you whether the hosting mail setup is at fault.</p>
<p>The fix WooCommerce recommends is to use a dedicated SMTP provider to send the email for you, which it describes as more reliable than your own server's mail function. In practice that means three jobs:</p>
<ul>
<li><strong>Pick a transactional email service</strong> and create an account for your domain. Check its official pricing page yourself, as plans change.</li>
<li><strong>Connect WordPress to it</strong> with one SMTP or mailer plugin (never two at once), using the provider's API key or SMTP details.</li>
<li><strong>Verify your domain with the provider</strong>, which normally means adding the DNS records it gives you. That step matters for Step 6.</li>
</ul>
<p>Make this change on a copy of the site first if you can. A <a href="https://www.nextgenfusion.in/blog/wordpress-staging-site-test-changes/">WordPress staging site</a> lets you test the mailer without risking live orders, but remember to stop the staging copy from emailing real customers.</p>
<h2>Step 5: Use a From address on your own domain</h2>
<p>If the log says "Sent" and customers still see nothing, look at the sender first. In <strong>WooCommerce &gt; Settings &gt; Emails</strong>, the From address should use your website's domain, such as <a href="mailto:orders@yourstore.com">orders@yourstore.com</a>. The WooCommerce guide warns that a public address like @gmail.com or @yahoo.com is likely to land in spam or be blocked, because the declared sender (Gmail's or Yahoo's servers) does not match the actual sender (your server).</p>
<p>Gmail's <a href="https://support.google.com/a/answer/81126">email sender guidelines</a> go further. Google says not to impersonate Gmail From: headers and notes that Gmail will begin using a DMARC quarantine enforcement policy, which could affect delivery for anyone who does. Google also recommends one consistent From: address per message type, so keep one fixed address for order emails and a separate one for newsletters, and keep promotions out of receipts.</p>
<h2>Step 6: Set up SPF, DKIM and DMARC for the sending domain</h2>
<p>This is where most "sent but not received" cases end. Gmail's sender guidelines say that starting 1 February 2024, all senders who send to personal Gmail accounts must set up SPF or DKIM, have valid forward and reverse DNS for their sending domains or IPs, use a TLS connection, keep the spam rate reported in Postmaster Tools below 0.3%, and format messages to the RFC 5322 standard. Senders of more than 5,000 messages a day to Gmail accounts must set up SPF, DKIM and DMARC, with the From: domain aligned with the SPF or DKIM domain.</p>
<p>Most shops are nowhere near that volume, but Google recommends all three anyway:</p>
<ul>
<li><strong>SPF</strong> is a DNS record listing who may send mail for your domain. Google's guidance is that it should include all your senders. If you add an SMTP provider but forget to add it to SPF, its messages are more likely to be marked as spam. Keep one SPF record per domain and add each sender to it.</li>
<li><strong>DKIM</strong> signs each message so the receiving server can confirm your domain sent it. Google requires a key of 1024 bits or longer for personal Gmail accounts and recommends 2048 bits where your provider supports it.</li>
<li><strong>DMARC</strong> tells receiving servers what to do with mail that fails SPF or DKIM. Google says the enforcement policy can be set to none, and recommends DMARC reports so you can see who is sending as your domain.</li>
</ul>
<p>Google also notes that messages failing these checks might be marked as spam or rejected with a 5.7.26 error, so if a customer forwards you a bounce containing that code, authentication is the place to look. Your SMTP provider's domain verification screen shows which records are missing.</p>
<h2>Step 7: Test it like a customer</h2>
<p>Once the log, From address and DNS records are in order, run one clean test before you call it fixed:</p>
<ol>
<li>Place a real low-risk order, or a test-mode order if your gateway supports it, using a personal Gmail address and one other mailbox provider.</li>
<li>Confirm the order reaches Processing and the order notes show the email as sent.</li>
<li>Open the received email, view the original message or headers, and check that SPF, DKIM and DMARC all show a pass.</li>
<li>Check the admin "New order" email arrived at the shop's own address.</li>
</ol>
<p>Repeat this after any change to hosting, DNS, payment gateway or email plugins. A store that was fine last month can break quietly after a domain or SSL change, which is why it belongs in a regular <a href="https://www.nextgenfusion.in/services/website-maintenance-services/">website maintenance</a> routine rather than being fixed only when a customer complains.</p>
<h2>Frequently asked questions</h2>
<h3>Why are WooCommerce emails going to spam?</h3>
<p>Usually because the sender cannot be verified: a From address on a free mailbox such as Gmail, missing SPF or DKIM records, or a shared server with a poor reputation. Use your own domain, a dedicated SMTP provider, and SPF, DKIM and DMARC.</p>
<h3>Why does the customer get no email but I get the new order email?</h3>
<p>The customer "Processing order" email is enabled separately from the admin "New order" email, so check both. If both are on and the log shows "Sent", the problem is delivery or spam filtering, usually fixed by authentication.</p>
<h3>Where can I see whether WooCommerce sent an email?</h3>
<p>Go to WooCommerce &gt; Status &gt; Logs and open the <code>transactional-emails</code> source. For order emails, sent and failed attempts also appear as private notes on the order. If entries are missing, check the log settings are not hiding INFO or NOTICE levels.</p>
<h3>Do I need an SMTP plugin for WooCommerce?</h3>
<p>It is not required, but WooCommerce recommends a dedicated SMTP provider because it is more reliable than your own server's mail function. On shared hosting in particular, it is the most dependable fix for failed or missing emails.</p>
<h2>Conclusion</h2>
<p>When WooCommerce emails are not sending, work from the order outwards: confirm the order reached Processing, confirm the email is enabled, read the <code>transactional-emails</code> log, then fix SMTP, the From address and SPF, DKIM and DMARC in that order. Most stores are back to reliable order emails once mail goes through a dedicated provider on an authenticated domain. We have delivered 100+ projects and handle this setup as part of our build and maintenance work. If you would rather we check your store, message us on WhatsApp at +91 73482 28167 and you get a fixed written quote within one working day.</p>
<hr />
<p><em>Originally published on <a href="https://www.nextgenfusion.in/blog/woocommerce-emails-not-sending/">NextGen Fusion</a>.</em></p>
]]></content:encoded></item><item><title><![CDATA[How to Update PHP Version in WordPress Without Breaking It]]></title><description><![CDATA[To update the PHP version in WordPress safely, first check which PHP version your site runs and which version your WordPress core, theme and plugins…]]></description><link>https://nextgenfusion.hashnode.dev/how-to-update-php-version-in-wordpress-without-breaking-it</link><guid isPermaLink="true">https://nextgenfusion.hashnode.dev/how-to-update-php-version-in-wordpress-without-breaking-it</guid><category><![CDATA[PHP]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[WordPress]]></category><dc:creator><![CDATA[NextGen Fusion]]></dc:creator><pubDate>Tue, 17 Nov 2026 10:52:08 GMT</pubDate><content:encoded><![CDATA[<p>To update the PHP version in WordPress safely, first check which PHP version your site runs and which version your WordPress core, theme and plugins support, then make the switch on a staging copy, test the pages that earn you money, and only then change the live site from your hosting panel. WordPress currently recommends PHP 8.3 or greater, and PHP 8.2 stops receiving security fixes on 31 December 2026, so many sites need this change in the next few weeks.</p>
<p>The PHP switch itself is one dropdown in most hosting panels and takes seconds. The risk sits in old plugins and custom theme code that break on a newer version. Below is the routine I follow on client sites, with the official WordPress and PHP pages behind each date and version.</p>
<h2>Why the PHP version matters for a WordPress site</h2>
<p>PHP is the language WordPress runs on, and your host decides which version your site uses. Every PHP release branch has a fixed life. According to the official <a href="https://www.php.net/supported-versions.php">PHP supported versions page</a>, each branch gets two years of active support (bug and security fixes), then two more years of fixes for critical security issues only. After those four years, the branch reaches end of life and gets no fixes at all.</p>
<p>The <a href="https://wordpress.org/about/requirements/">WordPress requirements page</a> recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS support. It also says WordPress still works on PHP 7.4 and later in legacy environments, but warns that those older versions have reached end of life and may expose your site to security vulnerabilities. In plain terms: an old PHP version does not stop your site loading, but it leaves known holes unpatched.</p>
<h2>Which PHP versions are supported right now?</h2>
<p>These are the dates from php.net as of November 2026. If your site shows a version that is not in this table, such as 8.1, 8.0 or anything in the 7.x range, it is already past end of life.</p>
<table>
<thead>
<tr>
<th>PHP branch</th>
<th>Active support until</th>
<th>Security fixes until</th>
<th>What it means for you</th>
</tr>
</thead>
<tbody><tr>
<td>8.2</td>
<td>31 Dec 2024</td>
<td>31 Dec 2026</td>
<td>Plan the move now; no fixes from 2027</td>
</tr>
<tr>
<td>8.3</td>
<td>31 Dec 2025</td>
<td>31 Dec 2027</td>
<td>Meets the WordPress recommendation; security fixes only</td>
</tr>
<tr>
<td>8.4</td>
<td>31 Dec 2026</td>
<td>31 Dec 2028</td>
<td>A sensible target if your plugins support it</td>
</tr>
<tr>
<td>8.5</td>
<td>31 Dec 2027</td>
<td>31 Dec 2029</td>
<td>Newest; check plugin support carefully first</td>
</tr>
</tbody></table>
<h2>Step 1: Find the PHP version your site runs today</h2>
<p>In your WordPress dashboard, go to <strong>Tools &gt; Site Health &gt; Info</strong> and open the <strong>Server</strong> section. It lists the PHP version along with other server details.</p>
<p>You can also see the version in your hosting control panel, usually in a section named something like PHP configuration or PHP version manager. Note down the exact current version before you change anything, so you know what to roll back to.</p>
<h2>Step 2: Check that your WordPress core supports the new version</h2>
<p>WordPress publishes a <a href="https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/">PHP compatibility table</a> for each WordPress release. A few rows that matter in practice:</p>
<ul>
<li><p>WordPress 6.9, 7.0 and 7.1 are listed as compatible with PHP 8.5, 8.4, 8.3, 8.2, 8.1, 8.0 and 7.4.</p>
</li>
<li><p>WordPress 6.7 and 6.8 go up to PHP 8.4, and WordPress 6.6 goes up to PHP 8.3.</p>
</li>
<li><p>WordPress 6.3 and older are not listed as compatible with PHP 8.3 or newer.</p>
</li>
<li><p>WordPress 7.0 dropped support for PHP 7.2 and 7.3.</p>
</li>
</ul>
<p>So if your site is still on an old WordPress release, update WordPress core first (on staging), then change PHP. Doing both in one jump on the live site makes it hard to tell which change broke what.</p>
<h2>Step 3: Check your theme, plugins and custom code</h2>
<p>The same WordPress handbook page makes a point worth repeating: WordPress is rarely used without a theme or plugins. Core being compatible tells you nothing about a plugin that has not been updated in three years, or a custom theme written for PHP 7.</p>
<ul>
<li><p><strong>Update everything first.</strong> Update all plugins and the theme to their latest versions on staging before touching PHP. Recent releases are the most likely to include compatibility fixes.</p>
</li>
<li><p><strong>Look for abandoned plugins.</strong> On each plugin's page in the WordPress plugin directory, check when it was last updated and which WordPress version it was tested up to. A plugin with no updates for years is the most likely thing to fail.</p>
</li>
<li><p><strong>Ask about paid plugins.</strong> Premium plugins and page builders publish their own requirements. Check the vendor's documentation or changelog for the PHP version you are moving to.</p>
</li>
<li><p><strong>Review custom code.</strong> Code in a child theme's <code>functions.php</code> or a custom plugin is where older PHP habits hide. A developer should read it against PHP's migration guides for each version you skip.</p>
</li>
</ul>
<h2>Step 4: Test the new PHP version on a staging copy</h2>
<p>Make a full staging copy of the site and switch only the staging copy to the new PHP version. If you have not set one up before, our guide to <a href="https://www.nextgenfusion.in/blog/wordpress-staging-site-test-changes/">setting up a WordPress staging site</a> covers the options and how to stop staging sending real emails or taking payments.</p>
<p>Then click through the site the way a customer would. On a business or shop site, test at least these:</p>
<ul>
<li><p>The home page, a service or product page, and a blog post.</p>
</li>
<li><p>Every contact and enquiry form, including the confirmation message.</p>
</li>
<li><p>Add to cart, cart, checkout and the order confirmation page, using test payment mode.</p>
</li>
<li><p>Logging in, the dashboard, and editing and saving a page.</p>
</li>
<li><p>Any booking, membership, search or filter feature your business relies on.</p>
</li>
</ul>
<p>Turn on WordPress debug logging on staging while you test, and read the log afterwards. Warnings and deprecation notices there point you to the plugin or file that needs attention before you go live, even if the page looked fine.</p>
<h2>Step 5: Switch PHP on the live site and keep a way back</h2>
<p>Once staging passes, take a fresh backup of the live files and database. Pick a quiet hour for your traffic, change the PHP version in the hosting panel, and clear any server or plugin cache so visitors get pages built on the new version.</p>
<p>Run the same short test list on the live site straight away. If something breaks, switch the PHP version back to the one you noted in Step 1. Changing back takes seconds and buys you time to fix the plugin on staging without losing orders or enquiries.</p>
<h2>What to do if the site breaks after a PHP update</h2>
<h3>White screen or "There has been a critical error"</h3>
<p>This usually means a plugin or theme uses code the new PHP version no longer accepts. Switch PHP back first so the site is up, then find the culprit on staging by reading the error log or deactivating plugins one at a time.</p>
<h3>One feature stopped working</h3>
<p>If the site loads but a form, slider or checkout step fails, the plugin behind that feature is the first suspect. Check for an update, contact the plugin author, or replace it with a maintained alternative.</p>
<h3>A plugin has no compatible version</h3>
<p>Do not stay on an end-of-life PHP version for one plugin. Replace the plugin, or have a developer patch or rebuild that feature. An outdated PHP version and an abandoned plugin are both risks, and our <a href="https://www.nextgenfusion.in/blog/website-security-checklist/">website security checklist</a> covers why unpatched software is one of the first things to fix.</p>
<h2>Frequently asked questions</h2>
<h3>Which PHP version should my WordPress site use?</h3>
<p>WordPress recommends PHP 8.3 or greater. For most sites on a current WordPress release, PHP 8.3 or 8.4 is a practical choice, as long as your theme and plugins support it. Check the plugin requirements before choosing 8.5.</p>
<h3>Will updating PHP make my site faster?</h3>
<p>It can help, but it is not a guaranteed fix for a slow site. Slow WordPress sites usually have bigger causes such as heavy themes, too many plugins or no caching. Our guide on <a href="https://www.nextgenfusion.in/blog/slow-wordpress-site/">fixing a slow WordPress site</a> covers those first.</p>
<h3>Can updating PHP delete my content?</h3>
<p>No. Changing the PHP version does not touch your database or uploads. The risk is that pages or features stop working until incompatible code is fixed, which is why you test on staging and keep the old version ready to switch back.</p>
<h3>What happens if I stay on PHP 8.2 after December 2026?</h3>
<p>According to php.net, PHP 8.2 security support ends on 31 December 2026. Your site will keep loading, but any security issue found in PHP 8.2 after that date will not be fixed by the PHP project.</p>
<p>Updating the PHP version in WordPress is a short job when you do it in order: note the current version, confirm core, theme and plugin support, test on staging, then switch the live site with the old version ready as a fallback. If your site is on PHP 8.2 or older, plan the move before 31 December 2026.</p>
<hr />
<p><em>Originally published on the <a href="https://www.nextgenfusion.in/blog/update-php-version-wordpress/">NextGen Fusion blog</a>. I'm Ritesh Kumar Giri, founder of NextGen Fusion, a web and software development studio.</em></p>
]]></content:encoded></item></channel></rss>