That’s quite unfortunate and honestly, I can’t stress enough how much of this 💩 I have to deal with in my day-to-day work life. I’m going to guess this is your situation

1 – You are getting console errors pointing to the plugin, you then go through the error files or the error message and scour thru the internet and pray you hopefully find a fix. Well, tough luck if you aren’t a developer the chances of you fixing it like this is very unlikely.

Here are my 2 cents. Do you know what plugin is having issues but are you sure it’s the plugin that’s causing the issue? What I mean here is what if the plugin is having issues because of another plugin IE a conflict. The worst part is if it’s part of the core requirements of the plugin that’s having issues.

In reality, since it’s a core plugin it shouldn’t cause any issues with its children plugin. An example of this is free plugins, and premium plugins to extend the features of the free plugin. Okay, now you got that, back to debugging to see if a feature is causing the bug or re-install, you know? The basic procedure of debugging. If you don’t know this, here is my procedure

  1. Disable all plugins except for the core plugins
  2. Reinstall the plugins
  3. Install core plugins on a fresh and/or clean WordPress site
  4. Try out the features, there might be bugs.
  5. Change themes

If you want to know what I hate the most is that, if a plugin works on your end but it doesn’t work on the customer’s end. Even though you have the exact settings as them, the absolute worst.