Support

January 23, 2018 at 7:08 am

Hello,

May I ask which versions of Event Espresso and s2members are installed on your site? Also, does the error occur if all other plugins are deactivated and the site is temporarily switched to the default theme?

January 24, 2018 at 9:13 am

Hi there,

That’s interesting that S2Member support asked about a way to block EE’s scripts from loading on non-EE pages. This is because with one exception, EE’s scripts do not load on on non-EE pages.

I have S2 installed on a test site and checked its admin pages and there were no conflicts there.

Does S2 support know exactly which script needs to be blocked? My guess would be ee-cpt-wp-injects.js, because that’s the only script that’s loaded on non-EE pages. It’d be a really strange thing for that script to cause a conflict though.

• This reply was modified 6 years, 12 months ago by Josh. Reason: clarifications added

January 26, 2018 at 1:39 pm

You can block that script from loading from the S2 General Options page by adding the following code to a site functions plugin:

add_action('admin_enqueue_scripts','my_remove_ee_script_from_s2_pages', 21);
function my_remove_ee_script_from_s2_pages(){
    $current_screen = get_current_screen();
    if($current_screen->id == 's2member-pro_page_ws-plugin--s2member-gen-ops'){
        wp_dequeue_script('ee-inject-wp');
    }
}

Here’s how to set up a site functions plugin. If the above fixes the issue for the S2 General Options page of your site we can add the other pages to the script.

January 30, 2018 at 7:12 am

I didn’t think that would help because like I mentioned earlier, it would be really strange thing for that script to cause a conflict.

Can you get a copy of the source of the s2member webpage and paste it into a gist or pastebin, then link here? I’m afraid we can only guess what S2 is doing on that page and why there’d be an error there. If you cannot do that, you could also complete this form so we can investigate further.