Magnus Baneryd
Jan 26, 2010
  5432
(1 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
Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog

New Optimizely certifications - register for beta testing before November 1st

In January 2023, Optimizely is making updates to the current versions of our certification exams to make sure that each exam covers the necessary...

Jamilia Buzurukova | Sep 28, 2022

Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog