World is now on Opti ID! Learn more

Magnus Baneryd
Jan 26, 2010
  5156
(0 votes)

“Breaking” change in the Gadget Ajax framework between the CMS 6 RC1 and the RTM

I am sad to announce that we had to do a behavioral change in the gadget Ajax framework.

Previously when you did an Ajax call (using the gadget framework, gadgetInstance.ajax({..})) we loaded the default view of the gadget (gadget.loadView()) when the call returned. This has now changed so that we do not call gadget.loadView() when the Ajax call returns.

So if you were relying on that the default view was loaded when you did an Ajax post using gadgetInstance.ajax you now have to attach a default success handler and call loadView yourself.

gadgetInstance.ajax({
    type: "POST",
    url: gadgetInstance.getActionPath({ action: "Save" }),
    data: data,
    success: function(e){
        gadgetInstance.loadView();
    }
});
Jan 26, 2010

Comments

Please login to comment.
Latest blogs
Test blog updated

abv123

Dung Nguyen Epi | Jan 7, 2026

Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |