Title: Uncaught TypeError
Last modified: July 15, 2024

---

# Uncaught TypeError

 *  [camador](https://wordpress.org/support/users/camador/)
 * (@camador)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/uncaught-typeerror-92/)
 * After updating to latest version of Flexmls IDX plugin my WordPress site crashes,
   this is the exact line where the error is thrown
 * Uncaught TypeError: Cannot access offset of type string on string in wp-content/
   plugins/flexmls-idx/components/search-results.php:325

Viewing 1 replies (of 1 total)

 *  [Matt_flexmlsIDX](https://wordpress.org/support/users/matt_flexmlsidx/)
 * (@matt_flexmlsidx)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/uncaught-typeerror-92/#post-17891300)
 * Hi [@camador](https://wordpress.org/support/users/camador/) 
   I can look into 
   this. Would you be able to email us some more details about your WordPress site?(
   email: idxsupport at flexmls dot com)Please provide the activation key you’re
   using for the site (under _Flexmls IDX>Flexmls IDX_ WP admin page) and the information
   under the Support tab in the plugin so we can see which version of the plugin,
   PHP and cURL are being used.Thank you

Viewing 1 replies (of 1 total)

The topic ‘Uncaught TypeError’ is closed to new replies.

 * ![](https://ps.w.org/flexmls-idx/assets/icon.svg?rev=2617426)
 * [Flexmls® IDX Plugin](https://wordpress.org/plugins/flexmls-idx/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/flexmls-idx/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/flexmls-idx/)
 * [Active Topics](https://wordpress.org/support/plugin/flexmls-idx/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/flexmls-idx/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/flexmls-idx/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Matt_flexmlsIDX](https://wordpress.org/support/users/matt_flexmlsidx/)
 * Last activity: [1 year, 10 months ago](https://wordpress.org/support/topic/uncaught-typeerror-92/#post-17891300)
 * Status: not resolved