• Resolved rogerpearce

    (@rogerpearce)


    Combi multi search works fine on Chrome (and has been working consistently), but a user has just pointed out to me that it fails on Edge. I’ve tested, and it’s true. I’ve updated versions (PD 2.7.6.3, Multi search 2.7.7) but still a problem. Any advice?

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author rolandbarker

    (@rolandbarker)

    Yes, first make sure you’re using the latest version of all the plugins. Second, make sure you are not using any form of content caching on the page with the Participants Database shortcode on it.

    I am unable to test Edge, so if you’re still having a problem, please post a more detailed explanation of exactly how it is failing, thanks.

    Thread Starter rogerpearce

    (@rogerpearce)

    Hi. All plugins are up-to-date (updated again yesterday). I’m not clear about content caching: my site is hosted by a third party and I’m not expert in this. I assume it might be obvious from the page source, but I don’t know what to look for.

    Detailed description of the problem: It’s pretty simple. Enter a search term in the search box. Hit Search. The timer twirls round for a second or two with no result. Page remains the same.

    Plugin Author rolandbarker

    (@rolandbarker)

    OK, this sounds like a problem with the javascript. Since I can’t test this on Edge, you’ll need to investigate.

    Open the page on Edge, then enable the browser developer tools. What you want to look at is the “console” which is where javascript errors will appear.

    Clear the console (important!) then run your test. Immediately check the console for any problems that come in. You can post that here.

    Plugin Author rolandbarker

    (@rolandbarker)

    Oh, another thing you should look at is the “network” panel, this monitors the request that goes out when a search is performed. Clear that before testing also, then look for a “POST” item which is the search request. Take a look at the response to that request.

    Thread Starter rogerpearce

    (@rogerpearce)

    I ran the test with the console open. There appeared to be no javascript problems, but a raft of other issues. I’m not sure if any of them are significant. I ran the test with the network panel open. I can’t see a POST item. I have screenshots of the results, but I’m not sure how/if I can post them here. EDIT: see below.

    • This reply was modified 3 months, 3 weeks ago by rogerpearce.
    Thread Starter rogerpearce

    (@rogerpearce)

    On the console panel:
    issues:
    A ‘cache-control’ header is missing or empty
    A ‘cache-control’ header contains directives which are not recommended: ‘must-revalidate, ‘no-store’
    Response should include ‘x-content-type-options’ header
    Incorrect use of label for=FORM_ELEMENT

    On the network panel:
    under preview and response:
    failed to get session for list instance 1

    The server is running Cloudflare. From the little research I’ve done online, it seems as if that might be the problem.

    Plugin Author rolandbarker

    (@rolandbarker)

    The message you’re seeing in the network panel indicates that caching is interfering with the page functionality. When a search is submitted, a session is used to temporarily store the parameters of the search. That submission is secured with a nonce code so that submissions can’t be spoofed by another party. If the page content is cached, the nonce code will often (but not always) be incorrect.

    This cache can either be a server-based page cache or (less commonly) it can be a browser-based cache. The way to fix this is to suspend caching for this page, page caches are configurable as to which pages they are active on for just this reason. Browser caches can also be configured to not cache a particular page.

    I can’t tell you how to do this, really depends on your specific setup. Often, this can be handled in an accelerator or caching plugin configuration, or in some cases, you will need to contact your hosting provider for help with this.

    Thread Starter rogerpearce

    (@rogerpearce)

    Hi. Many thanks. I’ll contact my hosting provider and see if he can fix it.

    Thread Starter rogerpearce

    (@rogerpearce)

    Hi. For information, now resolved. My hosting provider added a cache bypass rule to the page. Thanks for your help.

Viewing 9 replies - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.