This website uses cookies to personalize your experience. By using this website you agree to our cookie policy.

MySQL Error in Logs

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #17746
    amishdirectamishdirect
    Participant

    Hi there!

    We are receiving the following error in our logs:

    2018/05/04 14:52:30 [error] 1247#1247: *655901 FastCGI sent in stderr: “PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘) OR () OR ())

    ‘ at line 47 for query SELECT

    wp_posts.post_title as title,
    wp_posts.post_title as post_title,
    wp_posts.ID as id,
    1 as blogid,
    wp_posts.post_date as date,
    wp_posts.post_date as post_date,
    ” as content,
    wp_posts.post_excerpt as excerpt,
    wp_posts.post_type as post_type,
    ‘pagepost’ as content_type,
    ‘post_page_cpt’ as g_content_type,
    (SELECT
    wp_users.display_name as author
    FROM wp_users
    WHERE wp_users.ID = wp_posts.post_author
    ) as author,
    w” while reading response header from upstream, client: 172.31.54.168, server: amishdirectfurniture.com, request: “POST /wp-content/plugins/ajax-search-pro/ajax_search.php HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php7.0-fpm.sock:”, host: “amishdirectfurniture.com”

    We recently added the this plugin to our website since the native theme one (Flatsome) was running slow on our site. The logic we are using is the “AND with exact word match” so I am trying to figure out what the error is in regards to with the “OR ()” logic.

    Any idea on what could be causing this issue? The support credentials I gave are for our live site. I am currently just trying to trouble shoot before making any changes. Any help would be great! Thanks!

    #17748
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Hi,

    This looks like the main search query, although it is not the full query, so I can’t tell what exactly is missing there. I’m guessing either a missing/corrupted file or something inconsistent in the search options database.

    Can you add temporary FTP access so I can try debugging it?

    Alternatively you can try to fully reset the plugin:
    Please only do this, if you are fine with loosing all the search plugin configuration, and any possible modficiations!
    – Under the Maintenance submenu, clicking the red “Wipe all plugin data..” button: https://i.imgur.com/KJyXZp3.png
    – Then re-downloading the plugin fron codecanyon and installing it again.

    #17752
    amishdirectamishdirect
    Participant

    I’ll back up our settings on our test site and then re-import them first. We use AWS so I don’t like handing out our keys to often. If I see that fixes the problem I will let you know. I know I had this plugin on our site a while ago so maybe wiping the old data might help.

    Thanks!

    #17760
    Ernest MarcinkoErnest Marcinko
    Keymaster

    You cannot access this content.

    #17769
    amishdirectamishdirect
    Participant

    You cannot access this content.

    #17771
    amishdirectamishdirect
    Participant

    You cannot access this content.

    #17787
    Ernest MarcinkoErnest Marcinko
    Keymaster

    You cannot access this content.

    #17792
    amishdirectamishdirect
    Participant

    You cannot access this content.

    #17804
    Ernest MarcinkoErnest Marcinko
    Keymaster

    Thank you very much for all the details.

    I have found the problem, it was a yet unknown bug with the recent version. It happened on single term searches, that is why the error was rarely seen in the logs.

    I have replaced the faulty line in the main search query file for a temporary fix. For reference, the wp-content\plugins\ajax-search-pro\includes\classes\search\class-asp-search-cpt.php file was modified, you can keep a copy of it, if you use it on multiple sites.

    I will of course fix this issue permanently within the upcoming release. The error should not re-appear now, hopefully.

    #17813
    amishdirectamishdirect
    Participant

    That’s awesome! Glad you were able to found out the problem. I am still seeing multiple errors in the log but I’m not sure if that was from you. I’ll check again tomorrow to confirm whether or not I am still seeing the error.

    #17815
    Ernest MarcinkoErnest Marcinko
    Keymaster

    You are welcome!

    I have seen other erros as well in the log, but those were not related to this plugin. Let me know if you find anything.

    #17822
    amishdirectamishdirect
    Participant

    Sorry, should have made myself clearer. I still saw the SQL error but there was multiple of them and they were back to back unlike the previous ones I saw. That’s why I thought they were most likely from you debugging. I just checked out the error log today and did not see the error. I’m going to go ahead and marked this as solve then. I’ll keep an eye out for the new update. Thanks again for all the help!!

    #17824
    Ernest MarcinkoErnest Marcinko
    Keymaster

    You cannot access this content.

Viewing 13 posts - 1 through 13 (of 13 total)
  • The topic ‘MySQL Error in Logs’ is closed to new replies.