Hi, We have two 68 C sites using V4.0.9 Designer and a modified default template that have been running for some time now. Recently we have noticed that when a search is performed there is a delay of anywhere from 10 to 30 seconds. We contacted our host provider and they are telling us it is a parsing issue in our code and provided the following link to help with repair: I have searched the unencrypted files and cannot seem to find the specific code referenced in the link. Has anyone experienced this problem? (or is the host provider skirting the issue) Any suggestions would be much appreciated. Thanks.
You would need to have a copy of developer to search all the files. I have looked at an old 4.0.9 installation that I have and do not have the same problem with search. This too unfortunately was designer. Have you tried testing on a completely untouched default template? This will then get rid of the case it is your modifications to the template behind the slowdown. You might also like to consider upgrading as the newer versions not only correct bugs but also provide many security patches.
document.write is javascript, not the mysql database. Do you have any modules? Have you customized the templates at all? What browser are you using, people who recently switched to Firefox 4 have had similar issues with html parser enabled. Often times its a missed closing tag in java or something.
Thank you both for the quick replies. I spoke with a different individual at our host provider and was told that they recently installed some security updates that may be causing an issue... something about a referrer does not exist when a search is performed. ...They are looking into the issue. I'll post an update after receipt of thier response.
One thing, I would be interested in knowing is whether this delay is with ALL browsers or just Firefox. As Larry already pointed out, "document.write()" is javascript. Each browser has it's own version(s) of javascript engine/parser. As pointed out in the developers article for Mozzila (FireFox v4.x), they implemented a new preemptive fetch which is proprietary to that browser. I would be more apt to believe that it is actually a javascript, document.onload(), call with what your describing as that type of call isn't executed until the page actually fully loads including all images even from other sources like banner ads or google adsense. I've run into similar delays even much longer or never finishing even though the entire page shows in the browser windows when a Facebook iframe is used. It's notorious for never getting all the resource items called in their javascript. This also, unfortunately has the ill affect of not allowing any other javascript functions to work as well until it finishes, which includes menus that use javascript.
Yes, the issue existed with all browsers tested (Firefox, IE and Safari). I received a response from our web host today and they discovered that another website was significantly dominating the shared resources. (I've always found it amazing how fast web hosts point to your script as the issue) They moved the site off the server and all is working well... for now. I guess it's time to seriously consider moving our site from the "pains" of a shared web server. Thanks again to all for your suggestions and sorry for the false alarm. Regards, Jim
