Skip to main content

I don’t know if anyone who has used the K2 Menu System (https://community.nintex.com/archive-25/k2-menu-system-9347) on 5.7 in this regard encoutered...


I did notice it since I upgraded today from 5.6 to 5.7 when I checked the console log.
All and all, my investigation took me to this page…


Has anyone encountered this issue, and if yes, what was your workaround?

@mlangeveld15 Did you put k2ms.init.js in the ..\Runtime\Script\ folder?


@mlangeveld15 Did you put k2ms.init.js in the ..\Runtime\Script\ folder?

In K2 blackpearl\K2 smartforms Runtime\Runtime\Script, or in K2 blackpearl\K2 smartforms Runtime\Script ?

 

Just to tell you, the file is not in the former directory, but it is in the latter.


@mlangeveld15 Did you put k2ms.init.js in the ..\Runtime\Script\ folder?

In K2 blackpearl\K2 smartforms Runtime\Runtime\Script, or in K2 blackpearl\K2 smartforms Runtime\Script ?

 

Just to tell you, the file is not in the former directory, but it is in the latter.

@adithepo Just fyi, I did try to ad the file into that folder, but the same error still showed up


@mlangeveld15 From note:

Copy the "Script" folder into "C:\Program Files (x86)\K2 blackpearl\K2 smartforms Runtime\" or if you are using a custom runtime folder then copy these files in there.


@mlangeveld15  Did you try to re-deploy MenuSystem package?

 


thanks @adithepo 
Will respond back to you as soon as possible on what works and doesn’t work


Hi @adithepo 

So, me and my colleagues were able to resolve the error by doing three things.

  1. On the K2Menu.GetMenuHtml stored proc, we commented the '<script>selectCurrentUrlMenuItem();</script>' from the SET @HTML section at the bottom of the script;
     

    It would seem that the function in question may have been removed, because we at least couldn’t find it anywhere (not even within all the Javascript files).

  2. Restarted the K2 Service and IIS at least two times.

  3. Do a hard reload on Chrome and Edge to get rid of all the legacy cache that gave us trouble.

There is probably an alternative to resolve this more efficiently, but this worked for us at least.


Reply