Re: ExportWebPart javascript bug in ASP.NET AJAX Futures 2007

alessandro — Tue, 05 May 2009 08:40:56 GMT

hi, I just had to deal with this myself. The function seems to have been disabled in the core script files. You may try re-enabling it again until a permanent fix is available. Add the following script block in your page (preferably the masterpage)

<script type="text/javascript">
function pageLoad()
{
    if (__wpm != null)
    {
        if (!__wpm.ExportWebPart)
            __wpm.ExportWebPart = WebPartManager_ExportWebPart2;
    }
}
function WebPartManager_ExportWebPart2(exportUrl, warn, confirmOnly) {
    if (warn == true && __wpmExportWarning.length > 0 && this.personalizationScopeShared != true) {
        if (confirm(__wpmExportWarning) == false) {
            return false;
        }
    }
    if (confirmOnly == false) {
        window.location = exportUrl;
    }
    return true;
}
</script>

Also note that I have taken the liberty to change the original function name from
WebPartManager_ExportWebPart to WebPartManager_ExportWebPart2 ; this is done on purpose in case ms decided to fix this in a future release, you won't go into conflict and it should just work whether you remember to remove the above workaround or not.

Have a good day,

ExportWebPart javascript bug in ASP.NET AJAX Futures 2007

smasher9 — Mon, 12 Jan 2009 03:41:53 GMT

Hi,

I use ASP.NET AJAX Futures 2007 for Drag Drop support in FireFox. But in IE the Export web part feature stops working now.

I found that, the WebPartManager javascript object in ASP.NET AJAX Futures JS library doesn't have the ExportWebPart method which is called to export web part. (The original ASP.Net WebPartManager javascript object has this method).

Is there any solution for this problem? Will it be fixed in the next version of ASP.NET AJAX Futures?

Thanks.

ASP.NET Futures

Re: ExportWebPart javascript bug in ASP.NET AJAX Futures 2007

ExportWebPart javascript bug in ASP.NET AJAX Futures 2007