Build in search cache problem

  • Resolved braehler

    (@braehler)


    5 years, 4 months ago

    Hey there,
    since the latest update we are having an issue with the build in search. If you search fo city A you get the results for city A. But when you do a second search, for City B, you get the results of city A. A third search for City C will get the results of City B and so on
    Any thoughts on this?

Viewing 8 replies - 16 through 23 (of 23 total)
  • Thread Starter braehler

    (@braehler)

    Hi @richardmtl
    I reached out to them and this is their response
    “This is actually an issue still pending a complete fix by WP Job Manager. This issue was not fully fixed in their latest release. The development team is actually aware of this and this is something still under further review. I believe this is something that would entail modifying the “ajax-filters.min.js” file and short-circuiting the function that reads the sessionStorage cache. In the meantime, you may use version 1.32.3 of the plugin.”

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Hi,

    Yup, https://github.com/Automattic/WP-Job-Manager/pull/1893 still has to be reviewed and accepted, sorry!

    Thread Starter braehler

    (@braehler)

    @richardmtl
    This is realy urgent. We and all the other customers need this fix. This is goind on for month now

    Thread Starter braehler

    (@braehler)

    @richardmtl

    I′ve tried some changes/ overriding the ajax-filters..min.js from the current version with the filter of version 1.32.3.
    Seems to work on our staging enviroment, but we have to do some more testing in the behavior. But on a first sight all seems to be good, and the cahing problem is solved for now.
    Still need to compare both filters line for line, but I think this could be a workaround until you′ve solved the current filter problem

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Great, @braehler ! Mind sharing your changes? Maybe it’d be useful for the developers..

    Thread Starter braehler

    (@braehler)

    Hey @richardmtl
    I just took the old ajax-filters..min.js from Version 1.32.3 and replaced the current version of 1.34.0
    I did not change anything in the code.
    I′m quite sure this is solved with this workaround, everything seems to work the way it should be.
    So the error which is leading to this must be somewhere in the filter within the changes which came up starting from version 1.33.0
    But I had no time to compare both filters, I do not work on the weekends, to see what the difference between verison 1.32.3 and Version 1.34.0 is. Still need to do that, but the filter is not well formatted ?? everything is in one line and that makes it a little bit hard to read through.
    Can I find them on github in a prettier formatted version?

    Plugin Contributor Richard Archambault

    (@richardmtl)

    You can find the History for that file here:

    https://github.com/Automattic/WP-Job-Manager/commits/6dddd269fbcb0f0e370d963bb1a0a4bdc4db3a83/assets/js/ajax-filters.js

    Thread Starter braehler

    (@braehler)

    @richardmtl
    thanks, I′ll have a look at that

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Build in search cache problem’ is closed to new replies.