Plugin conflict blocks hamburger

[alexgingras]

Hi X - I’m webmastering at www.csgo.ca, a local soccer league and we’ve used WooCommerce Poor Guy’s Swiss Knife to add extra information fields to WooCommerce checkout since we put the site together in 2014.

The plugin has stopped being updated some time ago and now it’s starting to create conflicts with X, such as blocking the opening of the hamburger on mobile. Deactivating the plugin solves the problem however it allows us to gather more essential details about players who subscribe and we’re in the middle of registration season.

Could you suggest a workaround?

[Prasant]

Hello @alexgingras,

Thanks for asking.

Unfortunately, it’s difficult for us to suggest you solution as the problem is clearly causing because of a 3rd party plugin that developer has stopped providing update. As WordPress ecosystem is evolving old plugin codes will create conflict issues. I checked the GitHub page of WooCommerce Poor Guy's Swiss Knife plugin and it seems that the developer hasn’t updated the code for close to 3 yrs.

wp-plugins/woocommerce-poor-guys-swiss-knife

Can you please let us know the exact requirement that above plugin is fulfilling on the website? Maybe we can suggest you some alternatives.

Thanks for understanding.

[alexgingras]

Hi Prasant! Thanks for your feedback. The plugin allows the creations of additional fields at client checkout on Woocommerce. Usually you have name address phone number etc… but we needed to add fields specific to the league, such as years of experience, preferred playing position and so on as checkboxes, radio buttons and drop down menus. As I said the problem we’re having is that registrations have been under way for the last 3 months (and finishes in one month) and lots of information is already stored that is dependent on that plugin so removing the plugin right now is not a practical solution… Thanks so much for your help

[friech]

Hi There,

Regretfully, we cannot provide support for third party plugins or scripts due to the fact that there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script.

Have you tried our very own Woo Checkout Editor Extension? Was that does not fit of what you need?

You can install that under X > Validation > Extensions

Thanks,

[alexgingras]

Hi Friech! Thanks for this. We’ll do a temporary workaround for now but we’ll use the Checkout Editor extension after our registration period is closed (it wasn’t available in 2014 when we first launched ;))

[Prasant]

You are most welcome.