dev3410

Closing the ticket

I appreciate the response. I had a long discussion with my clients and they asked while the bug was being fixed to see if there were any alternatives. This client and many of our other clients were not pleased to be spending over 1000.00> a year on add-ons. During this time I found “Support Candy”. I tested it on multiple dev sites. I am quite impressed. Many of your add-on come free in the free core version of Support Candy. Plus “ALL” their addons can be purchased for a TOTAL of $59.00 per year that includes all your add-ons. Saving me and my clients HUNDREDS of dollars a year. They made the choice to switch. In fact, I switched them over to Support Candy and was informed today they are extremely happy.
Again, I do appreciate your help but we have decided to move over to Support Candy.

Thank you for your response. I will inform the client.
Concerning your questions and statements.

No plugin can be responsible for another plugin. But, due to bugs/errors in one plugin that make another plugin inoperable is the reponsibility of the plugin developer that is causing the problem due to the bug that I have previously reported.

Regarding the question does this issue started from the the update to WP 5.6 or < WP.
I’m not sure. I took the time to spin up a fresh install of WordPress 5.6 with only Awesome Support installed. You’re more then welcome to spin up your own clean version(s) of previous WP to see if the errors are present in past versions. I’m only concerned with the most current version on WordPress.

Again, thank you for your response.