this._contextMenuFunctionality.dispose is not a function

[Roman]

Hello,

I've updated to latest version of UI for ASP.NET AJAX R3 2016 and I get now following javascript error...

TypeError: this._contextMenuFunctionality.dispose is not a function

 /Telerik.Web.UI.WebResource.axd?....:29491:33 dispose()
 /Telerik.Web.UI.WebResource.axd?....:6:68785 disposeElement()
 /Telerik.Web.UI.WebResource.axd?....:15:35395 _updatePanel()
 /Telerik.Web.UI.WebResource.axd?....:15:32430 _scriptIncludesLoadComplete()
 /Telerik.Web.UI.WebResource.axd?....:6:204 .()
 /Telerik.Web.UI.WebResource.axd?....:6:307
 /Telerik.Web.UI.WebResource.axd?....:15:4881 _loadScriptsInternal()
 /Telerik.Web.UI.WebResource.axd?....:15:5671 _scriptLoadedHandler()
 /Telerik.Web.UI.WebResource.axd?....:6:307 ._completedCallback()
 /Telerik.Web.UI.WebResource.axd?....:6:94288 _scriptLoadHandler()

I'm using a TreeView and some context menus in a Update Panel and this error occures when I'm clicking a tree node.

These are the client side events of RadTreeView I'm using:

OnClientContextMenuItemClicking="onContextMenuItemClick"
OnClientContextMenuShowing="onClientContextMenuShowing"
OnClientDoubleClick="onClientDoubleClickHandler"
OnClientNodeClicking="clientNodeClickingHandler"
OnClientNodeExpanding="toggleHandler"
OnClientNodeCollapsing="toggleHandler"
OnClientNodeExpanded="onNodeExpandedCollapsed"
OnClientNodeCollapsed="onNodeExpandedCollapsed"

Hope this helps,

Best regards

Roman Haussener

[Marin Bratanov]

Hi Roman,

UPDATE: R3 2016 SP2 (2016.3.1027) is released on 27 Oct 2016 and it contains a fix for this issue. 

This is a known regression in the RadEditor control. You can find more details and workarounds here: https://feedback.telerik.com/Project/108/Feedback/Details/203960. You can click the Follow button to get updates and status changes. At this point I can tentatively say that we will do our best to get this fixed in R3 2016 SP2 next week.

Regards,

Marin Bratanov
Telerik by Progress

[Roman]

Hi Marin,

Thanks for the fast answer!

... and sorry for being in the wrong context. I thought the error has something to do with the menu...

Regards
Roman Haussener

[Newton]

About this workarounds...

Workaround 1) - I already use EnableScriptCombine="false" and doesn't work.

Workaround 2) - This work's, but break the appearance of RadMenu on the same page.

Workaround 3) - Doesn't work.

 

Regards,

Newton

[Marin Bratanov]

Hello Newton,

In a few days a service pack release will be shipped that will fix this issue, my best advice is waiting for it.

As for the other issues:

The only reason I can think of for 1) not working is that the CDN is used.

For 2) - you need to ensure the same RenderMode is used for all controls of the same type, so in this case RadMenu and RadContextMenu instances need to use the Lightweight RenderMode together with the editor

On 3) - could you try placing this script just before the closing </form> tag in your page? If it does not work, the most likely problem is that it is not overriding the built-in function as it should. You can also add a simple alert() somewhere in it to see if it is shown. If not, move the script further down the page.

Regards,

Marin Bratanov
Telerik by Progress

[Kristian]

We have the same issue and it is a serious problem because the previous release solved another problem.

So now we have to decide what problems to have.

It would be nice with a hotfix!

[Marin Bratanov]

Hi Kristian,

By the end of the week we will release a service pack (R3 2016 SP2).

It will be an official release so you can use it in production as well (as opposed to a hotfix that is suitable for development only).

Regards,

Marin Bratanov
Telerik by Progress

[Kristian]

Thanks for a quick reply.

I would prefer a hotfix today/now instead of an official release Friday.

Please realize that this is a critical error affecting all our users right now.

[Marin Bratanov]

Hello Kristian,

For the time being the bug report page I linked in my first response to this thread provides three workarounds.

Regards,

Marin Bratanov
Telerik by Progress

[Kristian]

Yes, but as other users (Newton) have replied to that:

Workaround 1) - I already use EnableScriptCombine="false" and doesn't work.
Workaround 2) - This work's, but break the appearance of RadMenu on the same page.
Workaround 3) - Doesn't work.

[Kristian]

Its a sneaky error because in development on local IIS (Windows 10) the error does not occur, but in production (Windows Server 2008 R2) nothing works ... :-(

[Marin Bratanov]

In some cases some of the workarounds may not work, but my second post in this thread explains reasons for that:

- disabling combination will not work if CDN is used or if other settings override and it is not actually disabled

- changing the render mode will not necessarily break your pages, this depends on the layouts and appearance customizations you have in place. If all controls of a certain type have the same render mode, there shouldn't be issues.

- the script override not working - this is, most likely, related to the placement of the script tag and it not taking effect. Moving that to the end of the form should make it work.

Regards,

Marin Bratanov
Telerik by Progress

[Kristian]

With such specific knowledge available, I fail to se why a hotfix cannot be produced?

Several times during the seven years we've used your software, I have seen exact fixes published in the forum.

We are worried and will probably leave Telerik in our next vesion of our software.

[Marin Bratanov]

Hi Kristian,

The proposed workarounds are just workarounds, the actual solution is more complex. We could have produced an internal build (hotfix) today, for example, that you could use for development. It just takes a bit more time to actually fix a problem than to work around it.

So, instead, we chose to release an official version that you can use in production as well and we are planning on doing that tomorrow, just a day after a potential hotfix could have been available.

This is the best way to provide a resolution for this problem, because it will allow all other clients to have an official release and fix, including people that hit the issue years from now (an internal build or hotfix would not have been available after the next official release).

We take such regression bugs very seriously and we want to minimize their impact in the long run as well.

I hope this explains why we chose this path and alleviates your concerns.

Regards,

Marin Bratanov
Telerik by Progress

[Kristian]

Thank you - if it is available tomorrow I think it is an acceptable response time.

[Marin Bratanov]

Hi,

I am happy to say that we just released the official R3 2016 SP2 (2016.3.1027) that contains a fix. You can download it from your Telerik.com account, upgrade your project(s) and use it in production.

Regards,

Marin Bratanov
Telerik by Progress