Support » Plugin: Hustle Marketing, Social Share, Email Opt-in Form, and Popup Plugin » Error on mobile (tested Chrome and Firefox)

  • Resolved illma


    the problem: plugin loads html content without applying the js to it, hence the content is loaded at the very bottom of the page and visible. This error happens only on mobile, on PC the pop-up shows correctly.
    The front.min.js is included in the code.
    When debugging mobile through firefox, I found this error for the site:

    TypeError: e.provider_args is null

    I am not very skilled with web based programming languages. Could you please help me correct this? I did not find anything on google regarding this issue.
    Thanks a lot for your time and possibly also help!

    Kind regards,

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Kasia – WPMU DEV Support


    Hello Illma,

    I’m sorry to hear that Hustle is not working correctly on your site.

    I checked now on my site if I can replicate this issue with mobile devices but I could not. Popup code doesn’t show in the footer of the site.

    First thing to check if this error is not related to any other plugin or theme that is used.
    To check that you need to disable all the other plugins and switch to default WordPress theme and see if error is still there.
    Let us know how it goes.

    kind regards,

    Hi Kasia,
    thanks for help!
    It is because of W3 total cache plugin, because the popup shows when I am logged in as admin (and for logged in users there is non cached version shown).
    Also, I removed the condition in regards to provider_args from the source, which did make the error go away and no other are shown so it did not make anything worse.
    But, it did not solve my problem. I want to keep w3c since I set it up very carefully and I am happy with the plugin.

    Plugin Support Predrag Dubajic WPMU DEV Support


    Hi @illma,

    Could you perform couple of more tests by changing W3TC settings to figure out which option exactly from plugin is causing this, since W3TC has quite a few options 🙂

    If we could pinpoint the exact cause we can debug it further from there and see what could be done from our end to go around this.


Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error on mobile (tested Chrome and Firefox)’ is closed to new replies.