Title: errors on search widget
Last modified: August 22, 2016

---

# errors on search widget

 *  Resolved [Neil Shimer](https://wordpress.org/support/users/neil-shimer/)
 * (@neil-shimer)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/)
 * Am recieving these type warnings on the search widget:
 * Warning: mysql_fetch_array() expects parameter 1 to be resource, boolean given
   in C:\xampp\htdocs\autodealer\wp-content\plugins\car-demon\includes\car-demon-
   search-fields.php on line 284
 * [https://wordpress.org/plugins/car-demon/](https://wordpress.org/plugins/car-demon/)

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

 *  Thread Starter [Neil Shimer](https://wordpress.org/support/users/neil-shimer/)
 * (@neil-shimer)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/#post-5888884)
 * Also not showing the drop down for condition but condition category exists for
   Used.
 *  Thread Starter [Neil Shimer](https://wordpress.org/support/users/neil-shimer/)
 * (@neil-shimer)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/#post-5888888)
 * These errors are showing in [PHP: 5.5.19] & [PHP: 5.6.3]
    I think it might have
   to do with: mysql_fetch_array — Fetch a result row as an associative array, a
   numeric array, or both Warning
 * This extension is deprecated as of PHP 5.5.0, and will be removed in the future.
 * BTY, this works without errors in my xampplite [PHP: 5.3.1]
 *  Plugin Author [theverylastperson](https://wordpress.org/support/users/theverylastperson/)
 * (@theverylastperson)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/#post-5888901)
 * Hi Neil,
    Thanks for reporting this and for letting me know mysql_fetch_array
   has been deprecated. I’ve also had a report that the transmission field is causing
   some issues. We should have this patched in 1.4.1 and hope to have it released
   on Friday, if not sooner. If you notice anything else not behaving properly let
   me know and we’ll get it addressed as quick as possible. thanks! -j
 *  Plugin Author [theverylastperson](https://wordpress.org/support/users/theverylastperson/)
 * (@theverylastperson)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/#post-5888962)
 * Hi again Neil,
 * I just wanted to let you know the issue with mysql_fetch_array has been resolved
   in the development version, which you can download from here:
    [https://downloads.wordpress.org/plugin/car-demon.zip](https://downloads.wordpress.org/plugin/car-demon.zip)
 * It’s now using $wpdb->get_var instead, like it should be.
 * As for your issue with the condition field, have you assigned any vehicles as‘
   used’? The form is designed to only show the values if there are currently unsold
   vehicles with that type.
 * Let me know if this resolved your issue(s).
 * take care,
    -j
 *  Thread Starter [Neil Shimer](https://wordpress.org/support/users/neil-shimer/)
 * (@neil-shimer)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/#post-5888968)
 * I did have a vehicle assigned as ‘used’ but with this update it fixed both problems!
   You rock!

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

The topic ‘errors on search widget’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/car-demon_748ba6.svg)
 * [Car Demon](https://wordpress.org/plugins/car-demon/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/car-demon/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/car-demon/)
 * [Active Topics](https://wordpress.org/support/plugin/car-demon/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/car-demon/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/car-demon/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Neil Shimer](https://wordpress.org/support/users/neil-shimer/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/errors-on-search-widget/#post-5888968)
 * Status: resolved