• Hi, I see these 3 errors in the console when I try to access the Admin menu edit page. Any idea what’s causing it or how to fix it ?

    Thanks

    load-scripts.php?c=0&load%5B%5D=thickbox,hoverIntent,common,admin-bar,svg-painter,shortcode,backbone,wp-backbone,media-models,wp-plupload,wp-mediaelement,wp-api&load%5B%5D=-request,media-views,media-editor,media-audiovideo,mce-view,imgareaselect,image-edit,heartbeat,wp-auth-check,wp-pointer,jquery-u&load%5B%5D=i-menu,jquery-ui-autocomplete&ver=4.9.14:584 Uncaught TypeError: Cannot read properties of undefined (reading 'memoize')


    actor-manager.js?ver=1662123253:147 Uncaught TypeError: AmeActorManager._.get is not a function
    at actor-manager.js?ver=1662123253:147:102
    at m.<anonymous> (load-scripts.php?c=0&load%5B%5D=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-resizable,jquery-u&load%5B%5D=i-draggable,jquery-ui-button,jquery-ui-position,jquery-ui-dialog,jquery-ui-tabs,jquery-ui-droppable,jquery-ui-slider,jquery-touc&load%5B%5D=h-punch,iris,wp-color-picker,underscore,wp-util,wp-a11y,updates,moxiejs,plupload&ver=4.9.14:163:2410)
    at new AmeActorManager (actor-manager.js?ver=1662123253:146:27)
    at actor-manager.js?ver=1662123253:560:17


    menu-editor.js?ver=1662123253:76 Uncaught ReferenceError: AmeActors is not defined
    at menu-editor.js?ver=1662123253:76:1

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    It’s hard to say; my first guess would be that it looks like a plugin or theme conflict, but the plugin is designed in a way that’s supposed to make this particular type of conflict unlikely. Still, you could check for conflicts by temporarily deactivating other plugins. If that fixes the errors, reactivate plugins one by one until the errors reappear to identify the conflicting plugin.

    Also, if your site has anything that affects how scripts are loaded – like some optimization tools that deal with JS in particular – try turning those off temporarily.

    Finally, I’m not sure if it matters, but only the second two errors are definitely related to this plugin. The first one could potentially be coming from something else.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.