It's better if you can "monkey patch" if possible - load an external script that patches Prototype with your fix after it's been loaded. Not that a Prototype upgrade will never cause your patch to break, but in many cases, it won't, and in the case of a big upgrade you'll probably end up having to tweak your patch anyway.
-Fred On Wed, Jun 25, 2008 at 12:26 PM, Paul <[EMAIL PROTECTED]> wrote: > > LOL ... we actually run into the same problem as we reported before > (see > http://prototype.lighthouseapp.com/projects/8886/tickets/12-ns_error_not_available-during-ajax-requests > , > which is fixed for 1.6.0.3). However, we accidentally upgraded > prototype which removed our patch. No one realized we are running into > the same exact issue since we assumed we already had the patch :). -- Science answers questions; philosophy questions answers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
