Skip to main content

telerik multiple window bug

Many of you (just like me) might have came across the multiple telerik window bug which is just as annoying as it can get

Scenario : In my case i had two telerik window which were opening from the same grid,one was inbuilt window for editing the record (GridEditMode.PopUp) and the other one was opening from one hyperlink inside the same grid

Here i had used the same model for both the partial controls which were loading inside window,so the control's generated html contained id same as property name of strongly model

So now when i was opening first window it came loaded with all controls and my partial control,now i opened second window as well,everything worked fine till now.

Now if you people might have observed that when you close the telerik window,It does not clear the content which you rendered inside it,so window was closed but the html inside remained as it is.

Now problem occurs now if i try to open the default edit pop up window for telerik grid it tries to render the html and now we have used the same model here so it gets same "Id" for the controls inside (as out previous window which we closed already has same content in it),and hence it does not know what to do and fires an error

So we always wonder,It was working when i first opened it but now when i opened it for the second time,It does not work and we run out of ideas what to do

Below is the solution for the same,It might help you solve the issue for your telerik multiple window

Solution : Just clear the content of the window in OnClose event like following,Write a client side event for window which calls below function

function OnClose()
{
   // MyWindow is id of my window
   $('#MyWindow').html('');
}

This is simple but it avoids many issues and saves time

Cheers !!!

Comments

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

Sitecore Stream - Platform DxP Evolution

Hi Team, I am absolutely Sitecore Stream enthusiast, and if you also keep following what is new in it and explore it features, This blog post is for you Since it was announced in symposium 2024 and probably the first platform DxP version package was released in FEB-2025 and we are now in Sep end and there have been significant roll outs and we are into 6th release of the platform DxP package. The purpose of this blog post is to summarize all improvements which came along with different releases for all of you and community, If you have not explored all of the packages. NOTE : Remember Stream is "AI capabilities throughout the composable stack, be it Content Hub, XMC, CDP, Personalized but this blog post is only for platform DxP package for on-prem XP/XM. If you see the image above, i have tried to show the package rollout on the timeline as an when they were released and watchout for next package rollout, For other useful features :)  Important improvements 1) Less configurations ...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!