Title: WpdiscuzCache.php error
Last modified: March 3, 2018

---

# WpdiscuzCache.php error

 *  Resolved [hothbricks](https://wordpress.org/support/users/hothbricks/)
 * (@hothbricks)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/wpdiscuzcache-php-error/)
 * I am getting the below error since 5.0.2 :
 * Warning: md5() expects parameter 1 to be string, object given in /path/wp-content/
   plugins/wpdiscuz/utils/class.WpdiscuzCache.php on line 98
 * it appears on the top of the first comment
 * Any idea ?

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

 *  Thread Starter [hothbricks](https://wordpress.org/support/users/hothbricks/)
 * (@hothbricks)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/wpdiscuzcache-php-error/#post-10034089)
 * Seems related to Gravatar cache, if I disable this caching option, then the error
   message disappear….
 *  Plugin Support [gVectors Support](https://wordpress.org/support/users/gvectorssupport/)
 * (@gvectorssupport)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/wpdiscuzcache-php-error/#post-10035021)
 * Hi hothbricks,
 * We’ve already fixed this issue. Please wait for the next update, it’s coming 
   very soon.

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

The topic ‘WpdiscuzCache.php error’ is closed to new replies.

 * ![](https://ps.w.org/wpdiscuz/assets/icon-256x256.png?rev=1076265)
 * [Comments - wpDiscuz](https://wordpress.org/plugins/wpdiscuz/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wpdiscuz/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wpdiscuz/)
 * [Active Topics](https://wordpress.org/support/plugin/wpdiscuz/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wpdiscuz/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wpdiscuz/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [gVectors Support](https://wordpress.org/support/users/gvectorssupport/)
 * Last activity: [8 years, 1 month ago](https://wordpress.org/support/topic/wpdiscuzcache-php-error/#post-10035021)
 * Status: resolved