Title: Upgrading to PHP 8.2 &#8211; Errors
Last modified: February 17, 2024

---

# Upgrading to PHP 8.2 – Errors

 *  Resolved [tibbie](https://wordpress.org/support/users/tibbie/)
 * (@tibbie)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/)
 * I have just upgraded to php 8.2 from 8.1 and my sites are going fine. However
   they all get these errors – PHP Warning:  Undefined array key “SERVER_NAME” in/
   home/silkyfl1/zzzzz.com/wp-content/plugins/stopbadbots/stopbadbots.php on line
   112
   PHP Warning:  Undefined array key “REQUEST_METHOD” in /home/silkyfl1/zzzzz.
   com/wp-content/plugins/stopbadbots/stopbadbots.php on line 116
 * Have never seen the error before the upgrade. Can you please advise, thanks

Viewing 10 replies - 1 through 10 (of 10 total)

 *  Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/)
 * (@sminozzi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17432860)
 * Hi Tibbie,
 * It’s not an error; it’s just a warning.
 * Your hosting provider is blocking access to this PHP variables: $_SERVER[‘SERVER_NAME’]
 * and
 * $_SERVER[‘REQUEST_METHOD’]
 * This is a legitimate operation; many plugins and themes will require it. It shouldn’t
   be blocked.
 * Please try contacting them to see if they can enable it.
 * Then, please let me know.
 * Cheers,
   Bill
 *  Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/)
 * (@sminozzi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17433750)
 * Hi Tibbie,
 * We are expanding on the previous answer by providing additional information and
   insights.
 * Your WordPress site should never display PHP warnings on the screen.
 * **Why you should hide PHP warnings:**
    - **They affect your site’s credibility:** Visitors may lose trust in your site
      if they see warnings displayed.
    - **They expose vulnerabilities:** Warnings can reveal potential security issues
      to hackers and other malicious actors.
 * **For a deeper dive into this topic, head over to our blog and read the article
   below (it’s free! and no registration necessary).**
 * [https://wptoolsplugin.com/how-to-handle-php-warnings-on-your-website/](https://wptoolsplugin.com/how-to-handle-php-warnings-on-your-website/)
 * I hope this is helpful.
 * Cheers,
 * Bill
    -  This reply was modified 2 years, 3 months ago by [sminozzi](https://wordpress.org/support/users/sminozzi/).
 *  Thread Starter [tibbie](https://wordpress.org/support/users/tibbie/)
 * (@tibbie)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17433858)
 * Bill, from the server people – After investigating this for you, we created a
   test script that utilizes the variables mentioned by the plugin developer and
   they work fine. We’d suggest contacting the developer again and informing them
   of this.
 * ——————–
 * I never display errors, they came via email, S
 *  Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/)
 * (@sminozzi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17433865)
 * Hi Tibbie,
 * Have you seen this only once or is the warning recurring?
 *  Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/)
 * (@sminozzi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17433891)
 * Hi Tibbie,
 * Anyway, try the new version 9.22. I hope it works fine on your server.
 * Bill
 *  Thread Starter [tibbie](https://wordpress.org/support/users/tibbie/)
 * (@tibbie)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17434036)
 * Bill, the recurring emails come through every 30 minutes, on the hour and half
   hour. 30 minutes is the current server cron job setting.
 * I am currently using Version 9.22 | By [Bill Minozzi](http://stopbadbots.com/)
 * If you have no other thoughts I will simply extend the cron setting so does not
   annoy, thanks S
 *  Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/)
 * (@sminozzi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17434068)
 * Tibbie, in version 9.22, I made a change. First, I checked if the variable exists(
   should always exist).** Then, the line number is changed.** Please check the 
   line number for any warnings. Perhaps your server is delivering old emails. Also,
   verify the date and time of the email.
 *  Thread Starter [tibbie](https://wordpress.org/support/users/tibbie/)
 * (@tibbie)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17434154)
 * Bill,
 * the date and time appear ok. As a matter of interest I added define(‘DISABLE_WP_CRON’,
   true); onto line 86 in wp-config.php which should be pretty safe and now get 
   this message via currently dated email – any use?
 *     ```wp-block-code
       PHP Warning:  Constant DISABLE_WP_CRON already defined in /home/silkyfl1/public_html/wp-config.php on line 86PHP Fatal error:  Uncaught Error: Call to undefined function wp_get_request_method() in /home/silkyfl1/public_html/wp-content/plugins/stopbadbots/stopbadbots.php:128Stack trace:#0 /home/silkyfl1/public_html/wp-settings.php(473): include_once()#1 /home/silkyfl1/public_html/wp-config.php(97): require_once('/home/silkyfl1/...')#2 /home/silkyfl1/public_html/wp-load.php(50): require_once('/home/silkyfl1/...')#3 /home/silkyfl1/public_html/wp-cron.php(46): require_once('/home/silkyfl1/...')#4 {main}  thrown in /home/silkyfl1/public_html/wp-content/plugins/stopbadbots/stopbadbots.php on line 128<!DOCTYPE html><html lang="en-US"><head>        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />        <meta name="viewport" content="width=device-width">                <meta name='robots' content='max-image-preview:large, noindex, follow' />        <title>WordPress &rsaquo; Error</title>        <style type="text/css">                html {                        background: #f1f1f1;                }                body {                        background: #fff;                        border: 1px solid #ccd0d4;                        color: #444;                        font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;                        margin: 2em auto;                        padding: 1em 2em;                        max-width: 700px;                        -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, .04);                        box-shadow: 0 1px 1px rgba(0, 0, 0, .04);                }                h1 {                        border-bottom: 1px solid #dadada;                        clear: both;                        color: #666;                        font-size: 24px;                        margin: 30px 0 0 0;                        padding: 0;                        padding-bottom: 7px;                }                #error-page {                        margin-top: 50px;                }                #error-page p,                #error-page .wp-die-message {                        font-size: 14px;                        line-height: 1.5;                        margin: 25px 0 20px;                }                #error-page code {                        font-family: Consolas, Monaco, monospace;                }                ul li {                        margin-bottom: 10px;                        font-size: 14px ;                }                a {                        color: #0073aa;                }                a:hover,                a:active {                        color: #006799;                }                a:focus {                        color: #124964;                        -webkit-box-shadow:                                0 0 0 1px #5b9dd9,                                0 0 2px 1px rgba(30, 140, 190, 0.8);                        box-shadow:                                0 0 0 1px #5b9dd9,                                0 0 2px 1px rgba(30, 140, 190, 0.8);                        outline: none;                }                .button {                        background: #f3f5f6;                        border: 1px solid #016087;                        color: #016087;                        display: inline-block;                        text-decoration: none;                        font-size: 13px;                        line-height: 2;                        height: 28px;                        margin: 0;                        padding: 0 10px 1px;                        cursor: pointer;                        -webkit-border-radius: 3px;                        -webkit-appearance: none;                        border-radius: 3px;                        white-space: nowrap;                        -webkit-box-sizing: border-box;                        -moz-box-sizing:    border-box;                        box-sizing:         border-box;
   
                               vertical-align: top;                }
   
                       .button.button-large {                        line-height: 2.30769231;                        min-height: 32px;                        padding: 0 12px;                }
   
                       .button:hover,                .button:focus {                        background: #f1f1f1;                }
   
                       .button:focus {                        background: #f3f5f6;                        border-color: #007cba;                        -webkit-box-shadow: 0 0 0 1px #007cba;                        box-shadow: 0 0 0 1px #007cba;                        color: #016087;                        outline: 2px solid transparent;                        outline-offset: 0;                }
   
                       .button:active {                        background: #f3f5f6;                        border-color: #7e8993;                        -webkit-box-shadow: none;                        box-shadow: none;                }
   
                               </style></head><body id="error-page">        <div class="wp-die-message"><p>There has been a critical error on this website.</p><p><a href="https://wordpress.org/documentation/article/faq-troubleshooting/
       ```
   
 *  Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/)
 * (@sminozzi)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17434188)
 * Tibbie, Thank you for the review and update.
 * Please, try the version 9.23
 *  Thread Starter [tibbie](https://wordpress.org/support/users/tibbie/)
 * (@tibbie)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17434284)
 * Bill, looks like has done the job!
 * thank you for your patience.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Upgrading to PHP 8.2 – Errors’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/stopbadbots_f0f0f0.svg)
 * [Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection](https://wordpress.org/plugins/stopbadbots/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/stopbadbots/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/stopbadbots/)
 * [Active Topics](https://wordpress.org/support/plugin/stopbadbots/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/stopbadbots/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/stopbadbots/reviews/)

 * 11 replies
 * 2 participants
 * Last reply from: [tibbie](https://wordpress.org/support/users/tibbie/)
 * Last activity: [2 years, 3 months ago](https://wordpress.org/support/topic/upgrading-to-php-8-2-errors/#post-17434284)
 * Status: resolved