Settings js command should use deep copy version of extend

+1 I just ran into a bug were settings were disappearing.

Also worth pointing out that this is what D7's setting command does:

  /**
   * Command to set the settings that will be used for other commands in this response.
   */
  settings: function (ajax, response, status) {
    if (response.merge) {
      $.extend(true, Drupal.settings, response.settings);
    }
    else {
      ajax.settings = response.settings;
    }
  },

i've reviewed the patch above and added an update to the preprocess function on the server-side to the same effect. this issue is blocking the dependency of ctools for the 2.x branch of ajax_load. this is against the latest dev

ooook, after working on this issue more, and looking over the d7 stuff again, the merge flag is really handy, this patch includes a merge arg and also implements a $return arg for the ctools_ajax_render function because I prefer the argument order and I need it as well, If you would like the $return arg patch separate, just let me know.

and once more changing the 'else if' to 'elseif'....

+1 this just killed me on a custom module. Any chance we can get his committed?

Thank you. I've been waiting a good minute for this to be rtbc, I'd really like to see this change made as it would allow me to work further on the "live" updates system I've imagined possible for some time.

I ended up just overriding the js function with my own with the same name. I'm not particularly sure if this is 100% safe to do or best practices (I would love to hear about it if it isn't) but since ctools ajax ended up in core in D7 I think most of the changes to D6 version are bug fixes rather than feature requests. I just wanted to throw the idea out there because it works quite well for me and doesn't require hacking ctools or waiting for this to be committed.

...coming from #1060340-10: Port AJAX load module to drupal 7.

This issue has be open for ages, the patch is small and robust, what do we have to do to get some attention on this matter???

Not sure why, but #6 was causing issues for me when using jCarousel in a modal. Specifically, this line in ajax-responder.js:

$.extend(data.merge, Drupal.settings, data.argument);

It was causing my jCarousel javascript to not be executed. I tried it with the original patch in the issue, and I do not have a problem if it looks like this:

$.extend(true, Drupal.settings, data.argument);

I'm short on time at the moment so I'm just reporting it. No suggested fix for now but I'm happy to provide extra information if needed.


Update: It works properly for me if we do something like the D7 version, such as:

  Drupal.CTools.AJAX.commands.settings = function(data) {
    if (data.merge) {
       $.extend(true, Drupal.settings, data.argument);
    }
    else {
      $.extend(Drupal.settings, data.argument);
    }
  };

reroll with additions from #13

I'm just in the process of testing #14. I appreciate that from a backward-compatibility perspective adding a parameter to ctools_ajax_render is the safe choice, but is there any case where doing a deep merge is going to break functionality? As far as I can see, there's very little risk aside from a slight performance hit client-side?