• Resolved Apple.R

    (@red-apple)


    Hi,

    My site uses the FlatSome theme and the UX Builder for creating pages. Today, I found a JavaScript error that is stopping the UX Builder script. The JavaScript error displayed in the console is shown below.

    Uncaught ReferenceError: Marionette is not defined

    plugins/google-site-kit/dist/assets/js/googlesitekit-events-provider-ninja-forms-ddd9645222a85c7954f3.js

    Is there anything I can do on my site? I use a Free Ninja form plugin and it is active.

    Thanks,
    Apple

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @red-apple. If you’d like to share the following we can try to determine more on this and hopefully ensure this no longer occurs:

    1. Your Site Health information. You can use this form to share privately if preferred.  
    2. A screen recording of your experience. You can use a service such as Loom or Zight to share a screen recording, while using the same form above to share this privately. 
    3. Is this appearing only when editing a page, or do you encounter any errors on the front end of your site as a regular visitor, in particular from any page with a Ninja form present?

    It’s possible you’re facing a conflict with the additional enhanced conversion tracking feature for Ninja forms. You may wish to check does the same occur if you temporarily disable this Analytics setting from within Site Kit.

    Let me know if you have any questions with the above.

    Thread Starter Apple.R

    (@red-apple)

    Hi James,

    Thanks for the quick response.

    Where I see the JS error?
    The JavaScript error occurs on every page because the UX Builder script for the site loader (which displays the logo during loading) runs on all pages. Although I haven’t added any Ninja Forms to published pages or posts yet, the plugin is enabled and some forms have been created. The error is visible on the frontend for regular visitors (who are not logged into WordPress). When I log into WordPress and view the homepage or other pages, the JavaScript error does not appear in the browser console.

    Enhanced Conversion Tracking issue
    Disabling the “Enhanced Conversion Tracking” option in Google Analytics, accessible through the Site Kit plugin, has resolved the issue. I have temporarily disabled it but hope to enable and use this feature later. It seems this option interferes with all the third-party plugins listed as supported for enhanced conversion tracking by Site Kit. Since disabling it, regular frontend visitors no longer encounter the “Marionette is not defined” error.

    Site Heath Information:

    • Autoloaded options could affect performance
    • You should use a persistent object cache

    Let me know if you need more information from me.

    Thanks,
    Apple

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the additional information @red-apple. Unfortunately we didn’t receive your full Site Health information (Tools > Site Health > info > Copy site info to clipboard) The information you shared was from your Site Health status. You can share privately via this form.

    If you can share a recording of this experience, with a link to this recording in the same Site Health information form, we can hopefully determine more on this.

    Thread Starter Apple.R

    (@red-apple)

    I submit the private form with the site health info following (Tools > Site Health > info > Copy site info to clipboard) . Hope it helps.

    Regards,
    Apple

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing the additional information @red-apple. As the Flatsome theme is a commercial theme, we’re unable to test for this error, however, if you can perform the checks below, this will help confirm a conflict with your UX Page Builder:

    1. Login to your live site from a Chrome browser incognito window.
    2. Install and activate the Health Check & Troubleshooting plugin.
    3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
    4. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google“.
    5. Check for the same error once more.

    Note that you may need to install a core theme to use while in troubleshooting mode.

    If the error doesn’t occur in troubleshooting mode, this will help confirm a UX Page Builder related conflict.

    It would also be great if you could share a recording of your experience, so we can dee more on this. From your side, given it sounds like a multi plugin conflict with Ninja Forms, did you check whether the same occurs after disabling enhanced conversion tracking from within Site Kit (Site Kit > Settings > Google Analytics >Edit > Enhanced Conversion Tracking).

    Let me know if you have any questions with the above.

    Thread Starter Apple.R

    (@red-apple)

    Hi James,

    As I explained in the previous post, after disabling enhanced conversion tracking within Site Kit (Site Kit > Settings > Google Analytics > Edit > Enhanced Conversion Tracking), the JavaScript error no longer appears in the browser console.

    I have decided to remove the Site Kit plugin to resolve the issue permanently. Thank you for your help.


    Regards,
    Apple

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update Apple.

    You shouldn’t need to have to disabled enhanced conversion tracking, and this is something we will investigate. You can continue to use Site Kit if you wish, with this setting togged off. If you are able to enable Site Kit once more, I can also provide you with some steps to help pinpoint the potential conflict, using the Health Check & Troubleshooting plugin. I suspect a theme related configuration may be conflicting with Google Analytics tracking, as you indicated with the page loader feature. This may be something that can be addressed. Do let me know if you wish to troubleshoot this further, and no problem if not. Thank you.

    I was getting a similar error, and my Ninja forms were not loading on one of my sites. Not on all my sites with SiteKit + Ninja Forms have the issue, but one did. Turning off Enhanced Conversion Tracking under Analytics in the SiteKit Plugin just resolved this for me.

    Thanks!

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @annabealizabeth, and thanks for initially reporting this @red-apple.

    We are currently investigating this and I can provide an update here when available. I’m aware it’s not ideal to have to deactivate enhanced conversion tracking, but hopefully we’ll have a fix out soon.

    Thread Starter Apple.R

    (@red-apple)

    Thanks @jamesosborne for following up. 🙂

    Plugin Support James Osborne

    (@jamesosborne)

    Just to let you know that we just released Site Kit version 1.153.0, and a fix for this issue you reported is contained as part of this release. Many thanks for raising this, and in turn your contribution to this latest release!

    Let me know if you have any further questions on this.

    Thread Starter Apple.R

    (@red-apple)

    @jamesosborne Thank you for the update. Thank you for great support! 🙂

    Hi @jamesosborne I am having the same issue as annabealizabeth abovewith the latest version.

    Ninja Forms Version 3.10.1
    Site Kit by Google Version 1.153.0

    • the issue only happening on a product page with variants, and selecting a variant and add to cart doesn’t work because of the js issue
    • turning off ninja form resolved the issue
    • turning off site kit resolved the issue
    • turning off the enhanced tracking resolved the issue
    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the addition @kaelkim. I’d be happy to check this with the team further and see what may be happening. While I’m doing so, can you open an individual support topic so we can communicate from there, while also sharing your Site Health information so I can review your environment?

Viewing 14 replies - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.