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

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...

Zero to Hero - A real life RCA of exact issue in Sitecore Managed Cloud environment

Hello All, The purpose of today's post is to share a real life burning and escalated scenario which was new to me and how did I approach it and how big the escalations were and what was the outcome Sitecore's goodwill was at stack not because Sitecore is not capable of handling it but just because our environment was Sitecore Managed Cloud, and any issue that comes if its infra, back end code, front end code will be first pointed as Sitecore issue and that is where our consultancy and experience will play a role to prove that it is not Sitecore issue.  Issue we faced Out of the blue our site started giving "504 Gateway Time-out", and it was reported that almost everyone is getting this error, but when we used to browse the site, everything looked good and never 504. 504 Gateway Time-out error tells that, That the request went to Content Delivery servers of Sitecore from gateway, but gateway did not get response in time from those CDs and hence it gave time out error. ...