So what went wrong?
It’s no secret that I’m a fan of using AJAX, if used wisely of course. In the backends I program AJAX is used in an excessive (read: ubtrosive (yes indeed!)) way as it improves the backend/cms a lot. Reason I’m relying heavily on AJAX (+ JSON responses, parsed through JSON.js) for the backend is that we can safely state that the single user who uses the backend (or the little group of users) has an XHR capable browser (it’s one of the requirements set before the backend is even made), it speeds up things (little data instead of a full page is sent back), it’s just “darn handy”, etc. (maybe a backend demo movie would be in place?)
A successful AJAX request as seen with firebug
And that’s where it all went wrong: after the update of prototype.js none of the AJAX calls even got made/executed (thank you Firebug for instantly letting me see what went wrong!). Jip, the website “Just Breaks” (TM)
Finding the problem
Remember remember, the fifth of November
Smoothing out the fix
As I already was using the
X-JSON header as it’s supposed to be done (scroll down last paragraph), but without the addition of the json parameter to the
onSuccess callback (I used a
evalJSON() in one function in which I injected a JSON string as a parameter.
1 million dollars!
Hope it was helpful and saves you the hassle 😉