Custom Field search in user meta type Hidden not working after upgrade

Home Forums Product Support Forums Ajax Search Pro for WordPress Support Custom Field search in user meta type Hidden not working after upgrade

This topic contains 3 replies, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 2 years, 10 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #24144
    Pedro Mendoza
    Inelectra_201809
    Participant

    After upgrade wordpress to version 5.2.3, from version 5.0.3 and upgrade ajax search pro to version Versión 4.16.3. the engine search setting Frontend Search Setting \ Custom Fields\ User meta (field) Type Hidden… is not working any more… the result is not filtering.

    We have a develpment site same setting identical search engine setting, but different wordpress version working 100%. Already test , install and uninstall the plugging, export/import definition of the search engine, clear cache, etc… Nothing look to work.

    Please advice how to proceed

    #24158
    Ernest Marcinko
    Ernest Marcinko
    Keymaster

    Hi,

    I can confirm this is a bug in the most recent release. To fix it manually, please try the following:

    1. Make a site back-up, just in case
    2. Open up the wp-content/plugins/ajax-search-pro/includes/functions/functions.php file on your server via FTP/SFTP
    3. Replace it’s contents with this
    4. Save the file

    Refreshing the page and trying again should resolve the issue.

    Best,
    Ernest Marcinko

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


    #24166
    Pedro Mendoza
    Inelectra_201809
    Participant

    I confirm that the indications provided solved the problem.
    Thanks a lot for your help!

    #24170
    Ernest Marcinko
    Ernest Marcinko
    Keymaster
    You cannot access this content. Best,
    Ernest Marcinko

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


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

You must be logged in to reply to this topic.