This Error 4.23.3 update: This request has failed. Please check your connection.

Home Forums Bug reporting, Questions & Suggestions Ajax Search Pro for WordPress This Error 4.23.3 update: This request has failed. Please check your connection.

This topic contains 5 replies, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 1 month, 1 week ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #40549
    marcel
    marcel
    Participant

    After updating to version 4.23.3 we now get an error : This request has failed. Please check your connection.

    Analysis shows we now get a php memory error, where we already have 2024mb allocated.

    Can you please resolve this as we have an issue on our live site now

    TY,
    Marcel

    #40551
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi Marcel,

    These errors usually indicate something on the server side, it is very unlikely to be a memory related issue. You can check this documentation for possible causes and resolutions to them.

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #40569
    marcel
    marcel
    Participant

    Hello Ernest, thank you for the quick reply.
    Firstly apologies it is regarding update from 4.23.3 to 4.24.2, so not a problem with 4.23.3

    We have looked into this but we have not found a solution.
    Also we have another wordpress staging environment running on the same server with the old plugin version that does not result in an error. The network analysis also returns a 500 server error, but only for the updated plugin version. It times out after about 6-7 seconds.

    I have notice the picklist on the frontend has a different html structure now after the update. the hidden label is missing.
    Please see the attached screenshots.

    Thank you for your support,
    Marcel

    Attachments:
    You must be logged in to view attached files.
    #40582
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi,

    The label change is intended, it will not impact the server side whatsoever, it is definitely unrelated to the issue.

    Try reinstalling the plugin first via the plugin manager, to make sure this is not a file corruption issue. Then, if the problem persists, then you will have to check the php error logs to see what triggers the 500 error. Error messages starting with 5xx are originating from the server side, so only the PHP error logs will help revealing the issue.

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


    #40628
    marcel
    marcel
    Participant

    Hello Ernest,

    After following the suggested instructions, including deleting and reinstalling the plugin we have finally managed to trace the issue to the wp-content/cache/asp directory, which is strange as we dont have any caching activated within the plugin.

    We don’t have a proper fix yet, but have found a workaround in renaming the asp cache directory. At least the filter is working again, but does trigger php warning messages; eg: file_put_contents(/wp-content/cache/asp/search1.css): Failed to open stream: No such file or directory.

    Can you investigate if this is indeed a bug or how we may properly resolve this error.
    Thank you for your support,
    Marcel

    #40629
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi,

    That folder is simply used to store the stylsheets and the script files generated. Make sure that the folder ( wp-content/cache/asp/ ) has not been deleted or the ownership and the permissions have not been altered.
    The error message reports, that PHP can not write that to that folder for some reason.

    Best,
    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)


Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.