Plugin conflict

[Anonymous]

Hi Franky,

I’m testing the BuddyBoss platform as we’re thinking of moving themes, but it seems that EME is causing a specific piece of BuddyBoss functionality to not work.

BuddyBoss has the ability to have forums and post new discussions, as you can see here: http://test.learning.necsu.nhs.uk/groups/clinical-system-specialists/forum/ I’ve set this so you don’t have to be logged in to start a discussion so you can see what should happen.

When logged into the site and with EME activated, clicking on the new discussion button doesn’t load the lightbox with the new discussion form.

When logged into the site and with EME deactivated, clicking on the new discussion button does load the lightbox with the new discussion form.

When not logged into the site, EME can be either activated or deactivated, clicking on the new discussion button does load the lightbox with the new discussion form.

So it seems that EME is causing a conflict, not allowing this lightbox to load when you are logged into the site, but this conflict doesn’t occur when not logged into the site.

I’ve tried with 2 different accounts that have different roles and the problem remains.

There are no caching plugins installed and I’ve tried in IE, Chrome & Firefox getting the same problem.

Is this something you could take a look at please?

Thanks.

[Anonymous]

The same happens when trying to reply, link: http://test.learning.necsu.nhs.uk/groups/clinical-system-specialists/forum/discussion/first-discussion/

I assume it’s the same thing blocking both.

[Franky]

Did you check your browser console? Seems like a javascript issue … But buddyboss is commercial, so I can’t test this locally.

[Anonymous]

Hi Franky,

I’m seeing this:

Error: No select2/compat/dropdownCss select2.min.js:2:1364
Source map error: Error: request failed with status 404
Resource URL: http://test.learning.necsu.nhs.uk/wp-content/themes/buddyboss-theme/assets/js/vendors/progressbar.min.js?ver=1.5.0
Source Map URL: progressbar.min.js.map

It’s just odd how it’s only happening to logged in users. I could give you a login to our test site for you to investigate if that’s possible?

Thanks,
David.

[Franky]

I’m guessing it is because they use select2 and so do I. And they probably use an select2-option for logged in users that causes this (while probably the select2-version of EME is loaded first which version seems newer, based on that error).
It’s always a pita when plugins need to provide own js libs, while wordpress doesn’t provide these (which is causing these issues in the first place).
Maybe it helps if you dequeue the EME version (or theirs). For EME, try this in your theme functions.php:

function eme_dequeue_select2() {
    wp_dequeue_script( 'eme-select2' );
}
add_action( 'wp_print_scripts', 'eme_dequeue_select2', 100 );

For this to work, you’d need an extra change in EME:
https://plugins.trac.wordpress.org/changeset/2320818

I could even make this an option (whether or not to use select2 in the frontend)

[Anonymous]

Hi Franky,

My replies aren’t showing on the thread, I’ve tried logging in/out but the same thing keeps happening.

I’ve made the change to the eme_actions.php file, removing line 360 and adding the 3 new lines, added the function to the functions.php file of my child theme, but the same thing seems to be happening.

Is there something else I could try, or I could provide login details if that’s easier for you.

[Anonymous]

There is a function in functions.php of the theme which shows the following, seems to enqueue – not sure if that helps your investigation?

  // Javascript
  wp_enqueue_script( 'buddyboss-child-js', get_stylesheet_directory_uri().'/assets/js/custom.js', '', '1.0.0' );
}
add_action( 'wp_enqueue_scripts', 'buddyboss_theme_child_scripts_styles', 9999 );

[Anonymous]

Ignore my last reply Franky, what you posted has worked for me.
I don’t know whether it will be worth adding the option – beyond my skill set TBH.

[Franky]

Ok, apparently some where pending (waiting to be approved, not sure why …). Anyway, since it works for you, I’ll leave it at that. Even better would be that they changed of course, since it seems that is a theme and a theme should anticipate on plugins, not the other way around … maybe you can ask budyboss how to stop enqueuing select2?

[Anonymous]

Thanks Franky.

Will the change you made here: https://plugins.trac.wordpress.org/changeset/2320818 be in later releases of the plugin? Just so I know if I need to continually change it when updating.

I’ll speak to BuddyBoss to see what they say, but it’s the BuddyBoss platform which uses select2 (the plugin to activate the functionality) rather than the theme itself (I think).

[Franky]

Well, maybe tell them to no longer use the dropdowncss option for select2. See this:

https://github.com/select2/select2/releases
(in the release notes: “Removed dropdownCss option”).

Or maybe they are using a beta version … ?

[Author]

Posts