Title: Deprecated found
Last modified: September 18, 2023

---

# Deprecated found

 *  [cfm168](https://wordpress.org/support/users/cfm168/)
 * (@cfm168)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/deprecated-found-3/)
 * Hello,
 * I have WP v6.3.1, WooCommerce v8.1.1. Can someone help how to fix the following
   deprecated issue:
 * Sep 18, 07:54:45
 * Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array
   |string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.
   php on line 2182
 * Sep 18, 07:54:45
 * Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string
   is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on
   line 7127
 * ———————————————————
 * Thanks in advance!
    -  This topic was modified 2 years, 7 months ago by [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/).

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

 *  [Alan Fuller](https://wordpress.org/support/users/alanfuller/)
 * (@alanfuller)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/deprecated-found-3/#post-17060500)
 * You don’t need to fix deprecated notices as a user. They are notice to developers
   that in future version the function may not work as expected.
   If these are displaying
   on a production site then you have the wrong settings and you should turn notices
   and warnings display off.See [https://fullworksplugins.com/docs/plugins-general/troubleshooting-plugins-general/php-notices-and-warnings/](https://fullworksplugins.com/docs/plugins-general/troubleshooting-plugins-general/php-notices-and-warnings/)
 *  Thread Starter [cfm168](https://wordpress.org/support/users/cfm168/)
 * (@cfm168)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/deprecated-found-3/#post-17061153)
 * [@alanfuller](https://wordpress.org/support/users/alanfuller/) – Thank you Sir.
 * How can I tell which plugin(s) cause the deprecated so I can contact the developer.
   I have more than 15 plugins in my site.
 *  [Alan Fuller](https://wordpress.org/support/users/alanfuller/)
 * (@alanfuller)
 * [2 years, 7 months ago](https://wordpress.org/support/topic/deprecated-found-3/#post-17061555)
 * No need to @ me or any one ( check you don’t break the guidelines: Do not abuse
   the `@<name>` mentions, they are not a tool to get faster responses. )
   1. Set
   you site to debug mode, dbug log true, debug display false. The logs should show
   stack traces, looking at the stack trace may identify which plugin is calling
   the core functions with ‘null’ [https://wordpress.org/documentation/article/debugging-in-wordpress/](https://wordpress.org/documentation/article/debugging-in-wordpress/)
   or2. Use a process of elimination, set theme to 2023 / disable all plugins, and
   enable 1 by one, you can do this without impacting users by using [https://wordpress.org/plugins/health-check/](https://wordpress.org/plugins/health-check/)
   or3. Get your developer to use a step debugger like xdebug and set break points
   when the core functions receive ‘null’ and then step up the stack

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

The topic ‘Deprecated found’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 3 replies
 * 2 participants
 * Last reply from: [Alan Fuller](https://wordpress.org/support/users/alanfuller/)
 * Last activity: [2 years, 7 months ago](https://wordpress.org/support/topic/deprecated-found-3/#post-17061555)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics