Title: Depreciated Code Errors
Last modified: May 2, 2024

---

# Depreciated Code Errors

 *  Resolved [mfghost](https://wordpress.org/support/users/mfghost/)
 * (@mfghost)
 * [2 years ago](https://wordpress.org/support/topic/depreciated-code-errors/)
 * In the back end of my website, in the SlimStats Overview, there’s two depreciated
   code errors, one in “Recent Search Terms” that says:
 *     ```wp-block-code
       Deprecated: parse_url(): Passing null to parameter #1 ($url) of type string is deprecated in /plugins/wp-slimstat/admin/view/wp-slimstat-reports.php on line 1115
       ```
   
 * and the the other in “Top Referring Domains” that says:
 *     ```wp-block-code
       Notice: Function wpdb::prepare was called incorrectly. The query does not contain the correct number of placeholders (2) for the number of arguments passed (1). Please see Debugging in WordPress for more information. (This message was added in version 4.8.3.) in /wp-includes/functions.php on line 6078
       ```
   
 * Has anyone else came across these and found a fix? I also can’t access the SlimStat
   plugin folder. I can access all the other except for SlimStat.
    -  This topic was modified 2 years ago by [mfghost](https://wordpress.org/support/users/mfghost/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fdepreciated-code-errors%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [Mostafa Soufi](https://wordpress.org/support/users/mostafas1990/)
 * (@mostafas1990)
 * [2 years ago](https://wordpress.org/support/topic/depreciated-code-errors/#post-17729501)
 * Hello,
 * Thank you for bringing this issue to our attention. It appears to be a compatibility
   problem with PHP v8.0, which I have now addressed. You can view the fix here:
 * [https://github.com/wp-slimstat/wp-slimstat/commit/23c8788e9e2543dc58600ea41cd0b8b7f07de884](https://github.com/wp-slimstat/wp-slimstat/commit/23c8788e9e2543dc58600ea41cd0b8b7f07de884)
 * Regarding the second issue, it seems to be more complex. Could you please use
   the Query Monitor plugin to trace it? This tool will help us pinpoint the exact
   line in the code where the issue occurs.
 * Thank you for your cooperation.
 *  Thread Starter [mfghost](https://wordpress.org/support/users/mfghost/)
 * (@mfghost)
 * [2 years ago](https://wordpress.org/support/topic/depreciated-code-errors/#post-17729584)
 * [@mostafas1990](https://wordpress.org/support/users/mostafas1990/) When I go 
   into my file directory I go to wp-content>plugins>wp-slimstat and I can’t go 
   any farther. It says “the server can’t be reached”.
 * I’ll run the plugin for the 2nd error.
 *  Plugin Author [Mostafa Soufi](https://wordpress.org/support/users/mostafas1990/)
 * (@mostafas1990)
 * [2 years ago](https://wordpress.org/support/topic/depreciated-code-errors/#post-17730539)
 * Weird indeed, I suggest reaching out to your server host support to investigate
   this matter, as it seems unrelated to the plugin or WordPress.
 * Best

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

The topic ‘Depreciated Code Errors’ is closed to new replies.

 * ![](https://ps.w.org/wp-slimstat/assets/icon.svg?rev=2832242)
 * [SlimStat Analytics](https://wordpress.org/plugins/wp-slimstat/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-slimstat/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-slimstat/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-slimstat/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-slimstat/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-slimstat/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Mostafa Soufi](https://wordpress.org/support/users/mostafas1990/)
 * Last activity: [2 years ago](https://wordpress.org/support/topic/depreciated-code-errors/#post-17730539)
 * Status: resolved