Title: Plugin is Extremely Dangerous
Last modified: March 20, 2023

---

# Plugin is Extremely Dangerous

 *  Resolved [LeoBullero](https://wordpress.org/support/users/leobullero/)
 * (@leobullero)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/)
 * After installing the plugin, the site partially stopped working, especially in
   responsive mode. Unfortunately, most of the problems remain despite removing 
   the plugin! Even a backup of the website did not help, as if we were dealing 
   with a virus. Probably the plugin has overwritten some core theme settings.
 * For four days we waited for help from 10Web, but we did not receive it. No one
   even accessed the site to diagnose the problem.
 * One user wrote in his review on wordpress.org:
 * “Even when i remove disconnect the plugin it keeps my website with broken images
   and crazy behavior!”
 * Be warned!
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-is-extremely-dangerous%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Support [narektorosyan](https://wordpress.org/support/users/narektorosyan/)
 * (@narektorosyan)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/#post-16579035)
 * Dear [@leobullero](https://wordpress.org/support/users/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 WordPress.org. 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.
 *  Thread Starter [LeoBullero](https://wordpress.org/support/users/leobullero/)
 * (@leobullero)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/#post-16579931)
 * 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://wordpress.org/](https://wordpress.org/)
 * 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.
 *  Plugin Support [narektorosyan](https://wordpress.org/support/users/narektorosyan/)
 * (@narektorosyan)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/#post-16579979)
 * Hi [@leobullero](https://wordpress.org/support/users/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.
 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/#post-16580390)
 * > 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](https://wordpress.org/support/users/leobullero/) Please don’t do
   that.
 * If [@narektorosyan](https://wordpress.org/support/users/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](https://wordpress.org/support/plugin/health-check/)
      and get the data that way.
    - Ask for a link to the [http://pastebin.com/](http://pastebin.com/) or [https://gist.github.com](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.](https://wordpress.org/support/article/debugging-in-wordpress/)
    - 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.
 *  Plugin Support [narektorosyan](https://wordpress.org/support/users/narektorosyan/)
 * (@narektorosyan)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/#post-16581639)
 * Dear [@leobullero](https://wordpress.org/support/users/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](https://wordpress.org/support/users/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.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Plugin is Extremely Dangerous’ is closed to new replies.

 * ![](https://ps.w.org/tenweb-speed-optimizer/assets/icon-256x256.png?rev=2753401)
 * [10Web Booster - Website speed optimization, Cache & Page Speed optimizer](https://wordpress.org/plugins/tenweb-speed-optimizer/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/tenweb-speed-optimizer/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/tenweb-speed-optimizer/)
 * [Active Topics](https://wordpress.org/support/plugin/tenweb-speed-optimizer/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/tenweb-speed-optimizer/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/tenweb-speed-optimizer/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [narektorosyan](https://wordpress.org/support/users/narektorosyan/)
 * Last activity: [3 years, 2 months ago](https://wordpress.org/support/topic/plugin-is-extremely-dangerous/#post-16581639)
 * Status: resolved