Welcome Guest Search | Active Topics | Sign In | Register

Reference Error: eo_Callback is not defined Options
Joan Darling
Posted: Friday, November 18, 2016 3:01:06 PM
Rank: Advanced Member
Groups: Member

Joined: 3/9/2010
Posts: 119
I'm getting the error "Reference Error: eo_Callback is not defined" from the client side when trying to execute a callback using the eo.callback control within a javascript function (see below). This error started about a month ago and so far is only affecting three customers. Each customer is using a different OS and the error is occurring in many different browsers so it's not OS or browser specific. Do you have any information that may help me to solve this problem? I've tried many different ways to try to reproduce it but no luck so far.

Code: HTML/ASPX
<eo:callback ID="cbScopeChange" runat="server" ClientSideAfterExecute="cbScopeChange_ClientSideAfterExecute">
</eo:callback>

<eo:callback ID="cbRoleChange" runat="server" ClientSideAfterExecute="cbRoleChange_ClientSideAfterExecute">
</eo:callback>
    
<eo:callback ID="cbAltRoleChange" runat="server" ClientSideAfterExecute="cbAltRoleChange_ClientSideAfterExecute">
</eo:callback>


Code: JavaScript
function ddlSelectedIndexChange(ddl) {
    try {
        if (ddl.id.indexOf("ddlRole") > -1) {
            eo_Callback("cbRoleChange", ddl[ddl.selectedIndex].value);
        } else if (ddl.id.indexOf("ddlAltRole") > -1) {
            eo_Callback("cbAltRoleChange", ddl[ddl.selectedIndex].value);
        } else if (ddl.id.indexOf("ddlScope") > -1) {
            eo_Callback("cbScopeChange", ddl.selectedIndex);
            resetToolbar();
        } else if (ddl.id.indexOf("ddlWebPeriod") > -1) {
            eo_Callback("cbDateChange", ddl[ddl.selectedIndex].value);
        }
    } catch (err) {
        alert("ddlSelectedIndexChange - " + err);
    }
}
eo_support
Posted: Sunday, November 20, 2016 12:04:53 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,229
Hi,

We can't think of anything specific that can cause this. It has to be related to the environment. For example, some users can have certain browser plugs/network security software that incorrectly blocks out our JavaScript file then you will have this error. If you have access to the user's system, you can use the browser's debugger to find out whether the script files are loaded correctly, and if not loaded, you maybe able to use a traffic analyzer to find out why.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.