Magnus Baneryd
Jan 26, 2010
  6684
(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
Optimizely CMS 13 and the Alloy demo site

The Alloy demo site now runs on Optimizely CMS 13. Here’s a quick guide to getting it up and running locally.

Tomas Hensrud Gulla | Apr 10, 2026 |

A day in the life of an Optimizely OMVP: Getting Up to Speed with Optimizely CMS 13 — A Free Learning Path

If you're working with Optimizely and haven't started exploring CMS 13 yet, now's the time. I've put together a dedicated CMS 13 course within the...

Graham Carr | Apr 10, 2026

A day in the life of an Optimizely OMVP: Optimizely CMS 13 Is Here: The Features, The Add-Ons, and What's Coming Next

CMS 13 went GA on 31st March 2026, and after months of previews, webinars, and internal engineering sessions, it's finally real. I've been deep in...

Graham Carr | Apr 10, 2026

How to get the Page Tree back in Optimizely CMS

Lost the page tree in Optimizely CMS? Here's why it happens and the non-obvious fix to get it back.

Henning Sjørbotten | Apr 10, 2026 |