MX Site Search Forum :: MX Search works and then stops
This thread was displayed: 0 times
Starting with 17th May 2007, Adobe Systems will stop offering support for any version of the discontinued InterAKT products. As a result, we will not answer to new support incidents starting with May 17th, 2007. Pending support incidents will still be followed in order to be closed. The product forums will remain open and be transformed in user-to-user forums. The general forums will be made read-only and not allow new posts or comments.
For more information about the affected products visit: www.interaktonline.com/Support/
Robert Farrell
04-03-2007 19:41:24 GMT +2
|
Hello - I hope mx search is still being support! I have a seach form that works for a few mintues and then tops working for about an hour and then starts working again what is causing this? thanks Robert
|
|
|
Brad Lawryk  04-03-2007 19:57:13 GMT +2
|
Hi Robert,
The solution to your problem is very simple actually.
In your MX Site Search settings there is a setting for 'Cache Refresh Delay'. This is currently set for 60 minutes by default. Why its 60 I don't know.
I always change that to '2'.
Hope that helps ya! ;-)
Brad
|
|
|
Robert Farrell
04-03-2007 20:54:37 GMT +2
|
Hey Brad thanks I changed it to 2 and it NOW works what is this for? Why is 2 better than 80 thanks Robert
|
|
|
Brad Lawryk 04-03-2007 21:22:39 GMT +2
|
Hi Robert,
I am no expert on coding - just using the extensions. So perhaps someone from InterAKT can actually explain in technical terms whhat it does and how it works. But in a nutshell from what I understand is that when a search is performed it creates a cache table of information from your site. WIth the default setting of 60 minutes a new cache will be created on the next search after the 60 minutes is up.
Any info added to the site before that cache will not show up in the search. This isn't a problem for sites that do not change content constantly and helps cut down on server resources and load time. However a site that constantly updates or is underdevelopment and has many changes in a matter of minutes the changes will not be implimented in the search until a new cache table is created.
So for all intensive purposes you can actually set that setting to '0' and a new cache table will be generated with every search. Its actually recommended to do this during development, but I find two minutes to be sufficient.
Hope that helps explain things a bit anyways.
Brad
|
|
|
Guenter Schenk 04-03-2007 23:56:31 GMT +2
|
Hey Brad,
such a great & elaborate explanation coming from a self-constituted no-coder -- now that puts me coder to shame, hands down, lol ;-)
Günter
|
|
|
Brad Lawryk 04-04-2007 00:29:16 GMT +2
|
Haha, I just hope I was half right on the explanation at least. I am just a mere 'Code Jedi in Training' compared to the great Darth Guenter. ;-)
Brad
|
|
|
Guenter Schenk 04-04-2007 00:54:09 GMT +2
|
lol, yes of course, but this time you´re better than me, because as coder I´d just have replied "because it´s just 1 digit" to the question "Why is 2 better than 80" ;-)
Günter
|
|
|
Robert Farrell
04-05-2007 00:15:48 GMT +2
|
Hey Brad complete break down NOW I cant get ANY of my forms to work they were ALl working fine and now they dont any suggestions? thanks Robert
|
|
|
benjamin wende
03-24-2008 15:30:35 GMT +2
|
|
|
|
