Title: Fatal error: Uncaught Error
Last modified: January 29, 2018

---

# Fatal error: Uncaught Error

 *  Resolved [Malae](https://wordpress.org/support/users/malae/)
 * (@malae)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-error-9/)
 * Hi Mikko,
 * After update to ver. 4.0.4 on site running PHP 7.0 I had the following message:
   `
   Fatal error: Uncaught Error: Call to undefined function mysql_connect()` I could
   not find the mysql_connect() function in any plugin files, but found instances
   of `mysql_` including the following: `relevanssi_index_mysql_columns` `relevanssi_mysql_columns`
   and `relevanssi_form_mysql_columns` in several files. If possible, reverting 
   to PHP 5.6 is a temporary workaround to fix the the site after crashing.
    -  This topic was modified 8 years, 4 months ago by [Malae](https://wordpress.org/support/users/malae/).
    -  This topic was modified 8 years, 4 months ago by [Malae](https://wordpress.org/support/users/malae/).

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

 *  Plugin Author [Mikko Saari](https://wordpress.org/support/users/msaari/)
 * (@msaari)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-error-9/#post-9916018)
 * Relevanssi does not use `mysql_connect` anywhere, Relevanssi does all database
   interactions through the $wpdb interface. Is it possible the function call is
   in a different plugin?
 *  Thread Starter [Malae](https://wordpress.org/support/users/malae/)
 * (@malae)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-error-9/#post-9916352)
 * Hello Mikko,
 * My apologies and thank you for your quick reply. When I didn’t find `mysql_connect`
   in the plugin files, I should have realised that the error was not from your 
   plugin, even though it indirectly triggered it. I thought the anomalous error
   message was cause by a glitch related to the use of `mysql_` functions, but it
   was late and didn’t have time to check further.
 * Today I dug deeper into the issue and finally found the cause. I had tested the
   plugin on a development site on a WAMP localhost server where PHP had been updated
   recently from PHP 5.6 to 7.0. Although all the extensions were installed and 
   I had had no other fatal errors, I had omitted to update the `extension_dir=`
   in the php.ini file. Thus the error was caused by WAMP not being able to find
   the required file for PHP 7.0.

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

The topic ‘Fatal error: Uncaught Error’ is closed to new replies.

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

## Tags

 * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/)
 * [uncaught error](https://wordpress.org/support/topic-tag/uncaught-error/)

 * 2 replies
 * 2 participants
 * Last reply from: [Malae](https://wordpress.org/support/users/malae/)
 * Last activity: [8 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-error-9/#post-9916352)
 * Status: resolved