Title: Preparing for PHP8.1
Last modified: June 7, 2023

---

# Preparing for PHP8.1

 *  [mattinventive](https://wordpress.org/support/users/mattinventive/)
 * (@mattinventive)
 * [3 years ago](https://wordpress.org/support/topic/preparing-for-php8-1/)
 * Hey I’ve looked through your support form and can see that you’re not currently
   offering full support for PHP8+, however I was wondering when you may have access
   to work on PHP8.1?
 * I’m getting the following depreciation notices:
 *     ```wp-block-code
       -Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/html/wp-includes/functions.php on line 7053
   
       -Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/html/wp-includes/functions.php on line 2165
       ```
   
 * Whilst I realise WordPress CMS is in beta for PHP8.1, it is advised that the 
   only issues with 8.1 are deprecated notices so it should be fine to test ready
   for 8 EoL
 * Many thanks for any help 🙂

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

 *  Plugin Author [AlanP57](https://wordpress.org/support/users/alanp57/)
 * (@alanp57)
 * [3 years ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16800584)
 * I address these issues as they are found. Since these deprecated messages do 
   not include references to any Media Library Folders plugin files, can you specify
   what type of operation was being performed at the time they occurred? Then I 
   might be able to reproduce them and trace them to their source.
 *  Thread Starter [mattinventive](https://wordpress.org/support/users/mattinventive/)
 * (@mattinventive)
 * [3 years ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16800775)
 * I am getting the issue with only the Media Library Folders activated on both 
   Storefront and Twenty Twenty themes.
 * The depreciation message is displayed on the dashboard at any section but not
   on the front-end.
 * The depreciations message do not persist once your plugin is disabled.
 *  Plugin Author [AlanP57](https://wordpress.org/support/users/alanp57/)
 * (@alanp57)
 * [3 years ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16800987)
 * Ok, I try this with PHP 8.1 and then get back to you.
 *  Plugin Author [AlanP57](https://wordpress.org/support/users/alanp57/)
 * (@alanp57)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16836772)
 * In our testing with PHP 8.1, we have not been able to identify the location of
   the lines of code where the issue is occurring. This may change to as better 
   tools for debugging PHP 8.1 become available. But this issue does not prevent
   one from using the plugin with version 8.1 or 8.2 of PHP.
 *  Thread Starter [mattinventive](https://wordpress.org/support/users/mattinventive/)
 * (@mattinventive)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16836792)
 * Thanks Alan for testing I appreciate the response.
 *  [Peter Smits](https://wordpress.org/support/users/psmits1567/)
 * (@psmits1567)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16836795)
 * [@mattinventive](https://wordpress.org/support/users/mattinventive/) when testing
   with 8.1 and 8.2 the result was the same. Even without MLF I get the error when
   going into menu “articles” for instance. So this is caused by WordPress or theme
   used. Going back to version PHP 8.0 resolves the error message. The message do
   not indicate which project causes them. MLF is working fine regardless of the
   errors, nor do I get problems anywhere else.
 *  Thread Starter [mattinventive](https://wordpress.org/support/users/mattinventive/)
 * (@mattinventive)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16836805)
 * Ok [@psmits1567](https://wordpress.org/support/users/psmits1567/), then it has
   to be the version of WordPress used on Pantheon as I’ve already ruled out potential
   conflicts.
 *  [Peter Smits](https://wordpress.org/support/users/psmits1567/)
 * (@psmits1567)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16836850)
 * here is the confirmation that it is a WordPress core problem
 * > [WordPress 5.9 and PHP 8.0-8.1](https://make.wordpress.org/core/2022/01/10/wordpress-5-9-and-php-8-0-8-1/)
 * Maybe this gives a clue what needs to be done to prevent the warnings

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

The topic ‘Preparing for PHP8.1’ is closed to new replies.

 * ![](https://ps.w.org/media-library-plus/assets/icon-128x128.jpg?rev=1814048)
 * [Media Library Folders](https://wordpress.org/plugins/media-library-plus/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/media-library-plus/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/media-library-plus/)
 * [Active Topics](https://wordpress.org/support/plugin/media-library-plus/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/media-library-plus/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/media-library-plus/reviews/)

## Tags

 * [deprecated](https://wordpress.org/support/topic-tag/deprecated/)

 * 8 replies
 * 3 participants
 * Last reply from: [Peter Smits](https://wordpress.org/support/users/psmits1567/)
 * Last activity: [2 years, 11 months ago](https://wordpress.org/support/topic/preparing-for-php8-1/#post-16836850)
 * Status: not resolved