Plugin is Extremely Dangerous

Dear @leobullero,

Hi. My name is Narek and I am the Director of the Customer Care team at 10Web.
?
Thank you for taking the time to share your feedback on www.ads-software.com. I want you to know that we appreciate all comments, both positive and negative, as they help us to improve our services.
?
However, I understand that your experience with our Speed Booster plugin did not meet your expectations, and for that, I sincerely apologize. Please accept my apologies for any inconvenience that we may have caused you.
?
I want to clarify that the Speed Booster plugin is designed not to affect website core files when in test mode or deactivated. It is possible that it may have conflicted with another plugin, such as an optimization plugin, which caused your website to be cached. This could explain why disabling the plugin did not resolve the issue.
?
To help us better understand the situation, we would like to investigate further and provide a solution. We would greatly appreciate it if you could allow us to look into the issue and fix it.
?
I also want to apologize for the delay in our response. Due to the high volume of customer care tickets, our agents missed your request. This is not an excuse, and we are taking steps to ensure that tickets like yours receive the highest priority and attention they deserve.
?
Once again, I want to express my apologies for any inconvenience you may have experienced. We take all feedback seriously and will do our best to ensure that your experience with our services is a positive one in the future. I am looking forward to your reply.

Thank you for your response. It’s difficult for me to definitively determine whether the issues with the website’s performance were caused solely by the plugin. I’m only certain that the website stopped functioning properly after its activation. Therefore, I’m changing my first review on https://www.ads-software.com/

I will prepare access to a test version of the website for you, maybe it will be possible to determine the causes of the errors.

Hi @leobullero,

We truly appreciate your willingness to hear us out. I’m eagerly anticipating your email and am confident that together we can pinpoint the root cause of the issue on the test version and resolve it promptly.

Once again, I’d like to express my sincere gratitude for your understanding and cooperation.

I will prepare access to a test version of the website for you, maybe it will be possible to determine the causes of the errors.

@leobullero Please don’t do that.

If @narektorosyan accepts that access then they may be banned from this site and the plugin may be removed from the WordPress repo. It is that serious.

Had the plugin support person asked for that access, and to be clear they did not ask for that, even to a test or temp site then this would be the reply to them.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

Dear @leobullero,

To investigate the issue you’ve reported, it would be helpful if you could install the plugin on a test copy of the website and provide us with the link. This will enable us to find the root cause of the problem without any access to the websites.

Dear @jdembowski,

We value and respect the guidelines set forth by the forum and the security concerns. We appreciate your message and assure you that we will not ask for any kind of access, not even to test copies of the websites. Thank you for bringing this to our attention.