-
MODX Staff
- 10,725 Posts
It appears there is a new problem now with the AjaxSearch javascript -- for some reason, in the default content from branches/0.9.6, the AjaxSearch javascripts are being registered into the content twice, effectively breaking AS somehow without reporting any kind of errors in Fx and IE7 at least. I tries to do something, and in fact the AJAX request appears to be completing properly, but no result or response is ever displayed on the page. Can anyone confirm this problem?
-
MODX Staff
- 12,272 Posts
I don’t think it happens if you’re logged out, but it does if you’re logged into the manager.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 12,272 Posts
Scratch that then ... must’ve been another problem that I was thinking about.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
... caching?
Check the cache for the document, if it’s properly registered in the documentOutput then there might be a problem. Because jscripts registered via regClientStartupScript shouldn’t be injected in to the content until right before the output is sent to the browser.
I will try to look into this, it may be because the mootools call is hard coded into the template and AjaxSearch is adding it also. I’ll try to find time by the end of the week to tackle this.
