Try our conversational search powered by Generative AI!

Magnus Baneryd
Jan 26, 2010
  5959
(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
Azure AI Language – Extractive Summarisation in Optimizely CMS

In this article, I demonstrate how extractive summarisation, provided by the Azure AI Language platform, can be leveraged to produce a set of summa...

Anil Patel | Apr 26, 2024 | Syndicated blog

Optimizely Unit Testing Using CmsContentScaffolding Package

Introduction Unit tests shouldn't be created just for business logic, but also for the content and rules defined for content creation (available...

MilosR | Apr 26, 2024

Solving the mystery of high memory usage

Sometimes, my work is easy, the problem could be resolved with one look (when I’m lucky enough to look at where it needs to be looked, just like th...

Quan Mai | Apr 22, 2024 | Syndicated blog

Search & Navigation reporting improvements

From version 16.1.0 there are some updates on the statistics pages: Add pagination to search phrase list Allows choosing a custom date range to get...

Phong | Apr 22, 2024