Un-namespaced Vue.js function causing theme conflict in frontend

  • Resolved Philipp Bammes

    (@tyrannous)


    5 years, 8 months ago

    Hi,

    a client of mine is having a theme conflict. He uses “Milano” (last updated 2016-06-26) that provides a JS function called core. Vue.js provides a function of the same name. When logged in, Vue.js’s assets are enqueued in frontend (why?), causing a JS error.

    I’m wondering what would be the best way to handle this? Since the theme has not been updated in a while I doubt they will change the function’s name (e.g. namespacing it). Is it necessary to enqueue Vue.js’s asset in frontend at all?

    Thanks!

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

Viewing 1 replies (of 1 total)
  • Plugin Author chriscct7

    (@chriscct7)

    Hi there,
    My guess is you are logged in as an administrator. This is the only reason we’d load Vue on the frontend as we use it for frontend statistics on the admin bar. This feature can be turned off in our admin settings area as a short term solution.

    If you could also send us a ticket at MonsterInsights.com/lite-support, I’d also like to look into this and see if we can’t get this conflict fixed for you and future users

    -Chris

Viewing 1 replies (of 1 total)
  • The topic ‘Un-namespaced Vue.js function causing theme conflict in frontend’ is closed to new replies.