New Build Breaks ConfirmTemplates

[Christopher Bishop]

The new build breaks the confirmtemplates (custom) and just throws errors now, also all of a sudden i cannot page on a grid past page 2, if i roll back to previous build it works fine. (grid is basic using needdatasource with paging) nothing fancy.

            <ConfirmTemplate>
                 <div style="height:10px;"></div>
                 <div style="float:left; padding-right:20px;">
                    <img src="../im/sw.png" alt="" title="" />
                 </div>
                 <div class="windowpopup radconfirm">
                   <div class="DFont"> {1} </div>
                   <div style="height:20px;"></div>
                   <div>
                     <div style="float:left; padding-right:18px;"></div>
                     <div style="float:left;width:100px;">
                         <a class="DFont" onclick="$find('{0}').callBack(true);" href="javascript:void(0);" >
                           <div class="CButtons DFont" style="cursor:pointer; width:90px; text-align:center;">
                             <div id="okBtn" class="DFont" style="width:90px; text-align:center;">Yes, Delete</div>
                           </div>
                         </a>
                     </div>
                     <div style="float:left;width:70px;">
                         <a class="DFont" onclick="$find('{0}').callBack(false);" href="javascript:void(0);">
                           <div class="CButtons DFont" style="cursor:pointer; width:60px; text-align:center;">
                             <div class="DFont" style="width:60px; text-align:center;">Cancel</div>
                           </div>
                         </a>
                    </div>
                    <div style="clear:both;"></div>
                   </div>
                 </div>
                 <div style="height:10px;"></div>
            </ConfirmTemplate>

[Fiko]

Hello Christopher Bishop,

I prepared a test demo based on your code and I was able to reproduce the problem. The issue occurs because the new version of the RadWindow control does not have callBack() function. You can avoid this problem by using the close() function instead callBack() one in the predefined Dialog Templates. In your case the confirm template should look like this :

<ConfirmTemplate>
    <div style="height: 10px;">
    </div>
    <div style="float: left; padding-right: 20px;">
        <img src="../im/sw.png" alt="" title="" />
    </div>
    <div class="windowpopup radconfirm">
        <div class="DFont">
            {1}
        </div>
        <div style="height: 20px;">
        </div>
        <div>
            <div style="float: left; padding-right: 18px;">
            </div>
            <div style="float: left; width: 100px;">
                <a class="DFont" onclick="$find('{0}').close(true);" href="javascript:void(0);">
                    <div class="CButtons DFont" style="cursor: pointer; width: 90px; text-align: center;">
                        <div id="okBtn" class="DFont" style="width: 90px; text-align: center;">
                            Yes, Delete</div>
                    </div>
                </a>
            </div>
            <div style="float: left; width: 70px;">
                <a class="DFont" onclick="$find('{0}').close(false);" href="javascript:void(0);">
                    <div class="CButtons DFont" style="cursor: pointer; width: 60px; text-align: center;">
                        <div class="DFont" style="width: 60px; text-align: center;">
                            Cancel</div>
                    </div>
                </a>
            </div>
            <div style="clear: both;">
            </div>
        </div>
    </div>
    <div style="height: 10px;">
    </div>
</ConfirmTemplate>

I hope this helps.

Regards,
Fiko
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

[Christopher Bishop]

Fiko,
Perfect solution works like a charm :)

Something else you guys should check out is the scriptmanager if used with radgrid (paging) it is flaky at best normally you can get to page 2 and then it is a crap shoot from there, replace with asp:scriptmanager and all is well. Which kind of sucks because i really like  the idea of  the scriptmanager...

Also feature suggestion: on the stylemanager it would be nice if you did the same thing that the script manager does ie: point it to the file instead of assembly.

[Veselin Vasilev]

Hi Christopher Bishop,

I took this example:
http://demos.telerik.com/aspnet-ajax/Grid/Examples/GeneralFeatures/Paging/DefaultCS.aspx

and replaced the ScriptManager with RadScriptManager. The page worked just fine.
Can you please tell us how to reproduce the problem?

Thanks

All the best,
Veselin Vasilev
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

[Christopher Bishop]

Veselin,

I will produce a example for you more than likely will not be until tommorow but I basicly did the same thing, i think the only difference here might be the fact that i am saving the viewstate in session but I will play around with a few samples and see if i can pin point the actual problem.

 

Thanks

Chris

 

[Veselin Vasilev]

Hi Christopher Bishop,

Take your time and let us know the results when you are ready.

Regards,
Veselin Vasilev
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

[Christopher Bishop]

Ok after some debugging and some straight tests (which i will compile and send up this weekend) here is what I have found.

The telerik scriptmanager and grid paging stuff is working like it should except when in these situtations (all of which have work arounds)

1: If you are saving the viewstate to a session and you have httpZip enabled on the server with large pages (100+) it causes the session to reset and the grid gets confused (on the paging not the actual grid).

2: If you are using advanced httpModules like me and stripping white space from css and js none of the controls will load in FireFox without a refresh of the current page it just hangs the first time you hit the page then if you hit reload a couple of times it goes through and works fine (works fine in all other browsers though).

3: There seems to be a weird random bug when using the telerik compression if you are already using gzip / iis compression that will cause a "full postback" not "ajax postback" on a page, haven't been able to really track this one down fully as it only happens in IIS 6 but works perfect in Win2008 and IIS7.

4: if using radscriptmanager in combination with the RadUpload randomly you will get page not found errors after and during upload, replacing radscriptmanager with asp:scriptmanager solves the problem. (this could be related to 1)

I have some more but I need to setup a test server in order to build some examples for better testing.

Like I say there are "easy" work arounds that are not a real hassle to implement (depending on how you build your pages of course) and somethings are effect by 3rd party compression tools etc. which are becoming "less" of a issue because with things like radscriptmanager and radcompression you can really get rid of a lot of the 3rd party tools for handling those kinds of things.