PHP Error Log File 7 gigs with Connections Query Error

  • Resolved donkiely

    (@donkiely)


    2 years, 4 months ago

    I just discovered that we have a 7 gig php_errorlog file on our web server in which the entire contents consist of an error thrown by Connections code. Each line is rather lengthy, but this is the gist:

    WordPress database error Can't find FULLTEXT index matching the column list for query SELECT [prefix]_connections_address.entry_id, ....

    More of the query is below, if it is of use.

    Why is there no FULLTEXT index? Is that something that we can recreate so that these queries succeed? And why is Connections throwing so many of these errors?

    Thanks!

    More of the query:

    [04-Jul-2022 00:50:39 UTC] WordPress database error Can't find FULLTEXT index matching the column list for query SELECT [prefix]_connections_address.entry_id, MATCH (line_1, line_2, line_3, line_4, district, county, city, state, zipcode, country) AGAINST ('+Guitar') AS score FROM [prefix]_connections_address WHERE MATCH (line_1, line_2, line_3, line_4, district, county, city, state, zipcode, country) AGAINST ('+Guitar' IN BOOLEAN MODE) ORDER BY score made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/[theme]/page.php'), the_content, apply_filters('the_content'), WP_Hook->apply_filters, do_shortcode, preg_replace_callback, do_shortcode_tag, _Builder_Element->_render, _Builder_Section->render, do_shortcode, preg_replace_callback, do_shortcode_tag, _Builder_Element->_render, _Builder_Row->render, do_shortcode, preg_replace_callback, do_shortcode_tag, _Builder_Element->_render, _Builder_Column->render, do_shortcode, preg_replace_callback, do_shortcode_tag, _Builder_Element->_render, do_shortcode, preg_replace_callback, do_shortcode_tag, cnShortcode::view, cnShortcode_Connections::shortcode, cnRetrieve->entries,

    The cnRetrieve->entries term then repeats a few dozen times.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Steven

    (@shazahm1hotmailcom)

    Sorry to hear you are having trouble!

    RE: Why is there no FULLTEXT index?

    The FULLTEXT indexes are created when installing Connections (if supported by the web host). This error can occur if something other than Connections alters or removes the FULLTEXT indexes.

    RE: Is that something that we can recreate so that these queries succeed?

    Please navigate to the Connections Settings admin page and click the Search tab. Disabled the FULLTEXT search option and save the save, then change. Clear/delete the PHP error log. Enable the FULLTEXT search option. Navigate to the Connections Directory homepage on your site. Enter a search term in the keyword search field and hit the enter key. Open the PHP error log file; one might not exist if it was deleted (the server creates it on demand). If the log file does not exist or does not contain the error, then the database properly supports FULLTEXT queries, and you do not need to take further action. If the error persists, please navigate to the Connections Settings admin page and disable the FULLTEXT search option.

    RE: And why is Connections throwing so many of these errors?

    The WordPress database will log the error if something other than Connections alters or removes its FULLTEXT search indexes. WordPress will log the error each time a keyword search is performed on the directory. So, if your directory is popular on your site, the log file can fill quite quickly.

    I hope this helps; please let me know.

    Thread Starter donkiely

    (@donkiely)

    Thanks! That resolved the problem. I really appreciate your help.

    Don

    Plugin Author Steven

    (@shazahm1hotmailcom)

    Good to hear. Again, apologies for the trouble. Have a great day!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP Error Log File 7 gigs with Connections Query Error’ is closed to new replies.