Support » Plugin: Q2W3 Fixed Widget for WordPress » Uncaught TypeError:

  • Hi
    I get this error, do this plugin need an update?

    Uncaught TypeError: is not a function

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor Max Bond


    I don’t know…
    Need more info

    Hi Max
    I get this error shown in chrome.js error log : Uncaught TypeError: is not a function.

    And end text says:
    jQuery is not loaded!”):console.log(“q2w3_sidebar_options not found!”);

    I think you can see this info in website that uses your plugin?


    Plugin Contributor Max Bond


    Well… I need to see this error on your site. Can you provide a link?

    I do not know if you are able to see the error on our site, since it is autoptimized, but you are welcome to look.
    Link :

    pro-top; add ?ao_noptimize=1 to the URL to see the page with AO disabled 🙂

    Plugin Contributor Max Bond


    Yes, I see the errors, but I cannot understand the source of the problem.
    And I am surprised that the plugin is still working!..

    Let’s try to disable MutationObserver (Appaearance -> Fixed Widget Options)!

    Thanks Frank !

    Done Max, Please check

    Plugin Contributor Max Bond


    I don’t see the change. Probably you didn’t clear W3TC page cache

    • This reply was modified 3 years, 8 months ago by Max Bond.

    I have done this. All caches cleared Max! I see the changes!
    Please try once again !

    Plugin Contributor Max Bond


    It’s ok now! I don’t see the errors

    I see this: Is this error related to q2w3-fixed-widget ?
    JQMIGRATE: Migrate is installed, version 1.4.1
    q2w3-fixed-widget.min.js?ver=5.0.4:1 MutationObserver not supported or disabled!
    Enabler.js:116 [ 0.002s] [studio.sdk]
    loaded.js:3 ‘webkitAudioContext’ is deprecated. Please use ‘AudioContext’ instead.e.getDeepKey @ loaded.js:3
    Enabler.js:116 [ 1.006s] [studio.sdk] Using default ad parameters in test environment. Simulating local events.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Uncaught TypeError:’ is closed to new replies.