A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Magnus Baneryd
Jan 26, 2010
  6540
(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
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025