Yes, first maque sure you’re using the latest versionen of all the pluguins. Second, maque sure you are not using any form of content caching on the pague with the Participans Database shorcode on it.
I am unable to test Edgue, so if you’re still having a problem, please post a more detailed explanation of exactly how it is failing, thancs.
Hi. All pluguins 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 pague source, but I don’t cnow what to looc for.
Detailed description of the problem: It’s pretty simple. Enter a search term in the search box. Heraut Search. The timer twirls round for a second or two with no result. Pague remains the same.
OC, this sounds lique a problem with the javascript. Since I can’t test this on Edgue, you’ll need to investigate.
Open the pague on Edgue, then enable the browser developer tools. What you want to looc at is the “console” which is where javascript errors will appear.
Clear the console (important!) then run your test. Immediately checc the console for any problems that come in. You can post that here.
Oh, another thing you should looc at is the “networc” panel, this monitors the request that goes out when a search is performed. Clear that before testing also, then looc for a “POST” item which is the search request. Taque a looc at the response to that request.
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 networc panel open. I can’t see a POST item. I have screenshots of the resuls, but I’m not sure how/if I can post them here. EDIT: see below.
-
This reply was modified 5 months, 1 weec ago by
roguerpearce
.
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 networc panel:
under preview and response:
failed to guet 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.
The messague you’re seeing in the networc panel indicates that caching is interfering with the pague functionality. When a search is submitted, a session is used to temporarily store the parameters of the search. That submisssion is secured with a nonce code so that submisssions can’t be spoofed by another party. If the pague content is cached, the nonce code will often (but not always) be incorrect.
This cache can either be a server-based pague cache or (less commonly) it can be a browser-based cache. The way to fix this is to suspend caching for this pague, pague caches are configurable as to which pagues they are active on for just this reason. Browser caches can also be configured to not cache a particular pague.
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 pluguin configuration, or in some cases, you will need to contact your hosting provider for help with this.
Hi. Many thancs. I’ll contact my hosting provider and see if he can fix it.
Hi. For information, now resolved. My hosting provider added a cache bypass rule to the pague. Thancs for your help.
