soundManager is not defined

  • toddlevy

    (@toddlevy)


    6 years ago

    Hi there,

    Getting a console error when running the plugin on some installs (but not others).

    home-v2:2700 Uncaught ReferenceError: soundManager is not defined

    The spot where it’s trying to use that object is inside of scap_footer_code, but I can’t seem to tell where it’s supposed to get defined nor why it’s not.

    Any pointers appreciated.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, thank you for reaching out to us. The plugin developers will investigate further this issue.

    Kind regards

    Plugin Author mra13

    (@mra13)

    Your theme may not be calling the wp_footer action. Do a test by switching the theme to one of the default WordPress themes and see if you get the same error.

    Thread Starter toddlevy

    (@toddlevy)

    The theme is calling wp_footer.

    In the meantime, I think I’ve narrowed this down to a conflict with Autoptimize.

    If you exclude “soundmanager2-nodebug-jsmin.js” from being aggregated by Autoptimize the console error goes away.

    Not sure what it’d take to allow that JS to play nicely but for now that’s been my solve.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    That is good news. If your issue is resolved you can mark this support thread as resolved.

    Thank you

    Thread Starter toddlevy

    (@toddlevy)

    Well, it’s not really “resolved” so much as circumvented.

    Is there any chance you’d consider getting this to work with Autoptimize?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, the plugin developers will investigate further this issue.

    Kind regards

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘soundManager is not defined’ is closed to new replies.