Trusted WordPress tutorials, when you need them most.
Beginner’s Guide to WordPress
Copa WPB
25 Million+
Websites using our plugins
16+
Years of WordPress experience
3000+
WordPress tutorials
by experts

Cómo desactivar todos los plugins cuando no se puede acceder a WP-Admin

Nota editorial: Ganamos una comisión de los enlaces de socios en WPBeginner. Las comisiones no afectan a las opiniones o evaluaciones de nuestros editores. Más información sobre Proceso editorial.

¿Necesitas desactivar todos los plugins de WordPress, pero no se ha podido acceder a la zona de administrador de WordPress?

Durante el proceso de diagnosticar problemas en WordPress, a menudo se le aconseja desactivar todos los plugins y luego reactivarlos uno por uno. Pero, ¿y si no puedes acceder a wp-admin para desactivarlos?

En este artículo, le mostraremos cómo desactivar fácilmente todos los plugins de WordPress cuando no pueda acceder al área wp-admin.

Deactivating all WordPress plugins without accessing admin area

Tutorial en vídeo

Subscribe to WPBeginner

Si prefiere instrucciones escritas o quiere avanzar a su propio ritmo, continúe leyendo las instrucciones a continuación.

Existen dos métodos comúnmente utilizados para desactivar plugins sin acceder al área de administrador de su sitio web WordPress. Puedes elegir el método que te parezca más sencillo:

Método 1: Desactivar todos los plugins de WordPress usando FTP

Para ello, deberá utilizar un cliente FTP o la aplicación de gestión de archivos de su panel de control de alojamiento de WordPress.

Si no has usado FTP antes, entonces puede que quieras ver nuestra guía sobre cómo usar FTP para subir archivos a WordPress.

En primer lugar, debe conectarse a su sitio web mediante un cliente FTP o el gestor de archivos de cPanel. Una vez conectado, tienes que navegar a la carpeta /wp-content/.

Dentro de la carpeta wp-content, verá una carpeta llamada plugins. Aquí es donde WordPress almacena todos los plugins instalados en su sitio web.

Rename plugins folder

Debe hacer clic con el botón derecho del ratón en la carpeta plugins y seleccionar “Cambiar nombre”.

A continuación, cambie el nombre de la carpeta por el que desee. En nuestro ejemplo, la llamaremos plugins.deactivated.

Plugins deactivated via FTP

Una vez hecho esto, todos sus plugins serán desactivados.

Esto se debe a que WordPress busca una carpeta llamada ‘plugins’ para cargar los archivos de los plugins. Cuando no encuentra la carpeta, desactiva automáticamente los plugins activos en la base de datos.

Por lo general, este método se utiliza cuando usted está bloqueado fuera de su área de administrador. Si el problema / incidencia era con sus plugins, entonces usted debería ser capaz de acceder a su área de administrador de WordPress.

Si visita la página Plugins ” Plugins Instalados dentro del área de administrador de WordPress, verá avisos de todos los plugins que han sido desactivados.

WordPress plugins deactivated

También te darás cuenta de que todos tus plugins han desaparecido. No te preocupes; todos están a salvo y puedes restaurarlos fácilmente.

Simplemente vuelva a su cliente FTP y vaya a la carpeta /wp-content/. Desde aquí, tienes que cambiar el nombre de la carpeta plugins.deactivated a plugins.

Ahora, puede volver a la página Plugins ” Plugins instalados dentro del área de administrador de WordPress y activar un plugin a la vez hasta que su sitio se rompa de nuevo.

En este punto, usted sabrá exactamente qué plugin causó el problema / conflicto / incidencia. A continuación, puede borrar la carpeta de ese plugin de su sitio mediante FTP o pedir al autor del plugin que le dé soporte.

Método 2: Desactivar todos los plugins usando phpMyAdmin

El método FTP es definitivamente más fácil, en nuestra opinión. Sin embargo, también puedes desactivar todos los plugins de WordPress usando phpMyAdmin.

Importante: Antes de hacer nada, haz una copia de seguridad completa de la base de datos. Esto será muy útil si algo sale mal.

A continuación, deberá acceder al panel de control de su alojamiento web. En este ejemplo, le mostramos un Escritorio cPanel. El Escritorio de su cuenta de alojamiento puede ser diferente.

Tendrá que hacer clic en el icono ‘phpMyAdmin’ bajo la sección Bases de datos.

Selecting phpMyAdmin on cPanel

Esto iniciará phpMyAdmin en una nueva ventana del navegador / explorador.

Tendrá que seleccionar su base de datos de WordPress si no está ya seleccionada. Después de eso, usted será capaz de ver las tablas de base de datos de WordPress.

Click at wp-options

Como puede ver, todas las tablas de la base de datos tienen el prefijo wp_ antes del nombre de la tabla. Sus tablas pueden tener un prefijo de base de datos diferente.

Debe hacer clic en la tabla wp_options. Dentro de la tabla wp_options, verá filas de diferentes opciones. Busque la opción ‘active_plugins’ y luego haga clic en el enlace ‘Editar’ al lado de él.

Click the Activate_Plugins option

En la siguiente pantalla, deberá cambiar el campo option_value a a:0:{}.

A continuación, haz clic en el botón “Ir” para guardar los cambios.

Reset active plugins

Has desactivado correctamente todos los plugins de WordPress usando phpMyAdmin. Si un plugin te impedía acceder al administrador de WordPress, ahora deberías poder acceder.

Guías de expertos en plugins de WordPress

Ahora que ya sabes cómo desactivar plugins cuando no puedes acceder a wp-admin, quizás te interese ver otras guías relacionadas con los plugins de WordPress:

Esperamos que este artículo te haya ayudado a desactivar todos los plugins en WordPress. Puede que también quieras aprender a establecer los objetivos de Google Analytics o comprobar nuestra lista de los mejores plugins de copia de seguridad de WordPress para mantener tus datos de WordPress a salvo.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

Descargo: Nuestro contenido está apoyado por los lectores. Esto significa que si hace clic en algunos de nuestros enlaces, podemos ganar una comisión. Vea cómo se financia WPBeginner , por qué es importante, y cómo puede apoyarnos. Aquí está nuestro proceso editorial .

Avatar

Editorial Staff at WPBeginner is a team of WordPress experts led by Syed Balkhi with over 16 years of experience in WordPress, Web Hosting, eCommerce, SEO, and Marketing. Started in 2009, WPBeginner is now the largest free WordPress resource site in the industry and is often referred to as the Wikipedia for WordPress.

El último kit de herramientas de WordPress

Obtenga acceso GRATUITO a nuestro kit de herramientas - una colección de productos y recursos relacionados con WordPress que todo profesional debería tener!

Reader Interactions

338 comentariosDeja una respuesta

  1. Syed Balkhi says

    Hey WPBeginner readers,
    Did you know you can win exciting prizes by commenting on WPBeginner?
    Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
    You can get more details about the contest from here.
    Start sharing your thoughts below to stand a chance to win!

  2. ARoibal says

    I am really thankful that you posted this article. I had no idea how to fix the problem and in my case it was a plugin. Thank you!!!!

  3. Robb Dearth says

    I usually don’t comment on posts like this, and I know this post is insanely old (by today’s standards) but I just wanted to thank you for this quick fix. I was able to access the /plugins folder via Media Temple’s file manager, change the folder name, and target the problem plugin… THANK YOU!!!

  4. Cindy says

    I could not get into my blog at all to edit anything. I followed your directions on deleting a plug-in. That fixed it. Thank you for the info and for explaining it in a way that is easy to understand!!

  5. Jairo Levi says

    Super! I was able to fix my site by renaming the Plug ins folder, then re activating the plug ins one by one.

    Just wanted to say thank you!

    Jairo.

  6. Dennis says

    Hello thanks so much for the article,
    i was developing my wordpress offline using wampserver localhost.
    When i finished it worked just fine on my localhost but after uploading it i started having the issue, only the index page could load and every other page still have the offline url ( that is localhost/mysite/thepost) when i manually change the localhost url to the normal url it ought to be, i gets a 500 Internal Server Error.

    I’ve tried all method mentioned here but my problem persist.
    Please I really Need help.

    Thanks so much.

  7. Franck says

    Great article! saved me a headache. Had to go through the whole process but was worth it. Now my site is back and everything up to date. Great job guys!

  8. maros says

    ssh:
    debian@otherland:*/wp-content/plugins$ sudo chown root:root menu-icons/
    debian@otherland:*/wp-content/plugins$ sudo chmod -R 700 ./menu-icons/
    debian@otherland:*/wp-content/plugins$

    then I reloaded “tab with server error 500” and it said to me something like plugin deactivated …files not found.

  9. Lesley Parolis says

    Thanks very much. It was really helpful. Deactivating the plugins solved the problem. There was one plugin which was causing the white out.

  10. Richard says

    Hi. I’ve renamed the plugin folder to plugin.deactivate but still have the white screen. I was so hoping I could fix my problem as quickly and easily as other have but not as yet. Any other suggestions? Many thanks.

  11. brian h says

    You can actually do this with the theme directory as well. This is what I had to do as I had both issues, plugins behaving poorly AND a theme issue that locked me out.

    Renamed themes to themes.deactivate and it let me back in to theme management which was keeping me from going any further than dashboard PERIOD.

    Once in there it told me what theme caused the issue in detail but I still had to recreate a new directory called “themes” and copy the good themes over to it before it would let me activate a new theme!

    Hope this sheds some light on possible additional errors :)

    Brian:

  12. Teejax says

    Hi,

    Thanks for the good job.

    I run WordPress on a self-hosted IIS via virtual machine.

    Unfortunately I could not rename my plugins folder, I kept getting “folder in use”

    What do I do?

    Thanks in advance.

  13. Fareena says

    Hi pls help! I have a blog on the free wordpress.com as such there is no independenthost but wordpress itself. I m unable to log on to the backend dur to 2 step authentication plugin on wordpress.
    Im trying to connect to my WP page via ftp can ypu pls confirm whether the username and password for ftp access is the same as my wordpress username password ? . At this stage I’m unable to acesss the backend and keep getting a could not connect to server error.

    I am trying to disable the 2 step authentication plugin for my site. As I no longer have the mobile sim it’s sending the verification code to. Pls help out as I’m pretty frustrated. Cheers

  14. jean jacques amani says

    please help me!
    there is 4 days i can access my wp pannel even by FTP using filezila.
    day before i open my wp pannel and saw one plugin need an update. i’ve did the automatical updade and since my website don’t pass.
    i can’t access the directory to deactive the plugin.
    i’ve followed the step you said using phpMyAdmin but can’t find “active plugin” in wp-option
    please help me

      • jean jacques amani says

        first i have to thank you for your assistance.
        I’m using a free mode in my web host and this don’t allows me to interract with them.
        when i try to open my website in the browswer i get this message:

        Warning: require_once(assets/ilenframework/assets/lib/utils.php): failed to open stream: No such file or directory in /home/u673270787/public_html/wp-content/plugins/yuzo-related-post/yuzo_related_post.php on line 24 Fatal error: require_once(): Failed opening required ‘assets/ilenframework/assets/lib/utils.php’ (include_path=’.:/usr/lib/php’) in /home/u673270787/public_html/wp-content/plugins/yuzo-related-post/yuzo_related_post.php on line 24

  15. Carla says

    I know my white screen came from a bad plugin and everything went sideways when I tried to uninstall it from wp-admin. Now I’m getting the white screen and the plugin is not showing up in my cPanel….what now?

  16. Squalle says

    Huge help for me this morning! I hadn’t been on my admin panel in a few days. I open it up and selected all the plugin updates and updated them all at once… big mistake. Got the WSOD and started freaking out. lol

    Then I found this article which helped immensely! Worked like a charm. I found the bad plugin and deleted it.

    Thanks for the great article!

    • Muhammad Awais Sarwar says

      I have a same problem. I can open dashboard of wordpress and also home page. But when I open any other page it says This webpage has a redirect loop

      ERR_TOO_MANY_REDIRECTS
      I remmber I only delete 2 plugins. I didn’t any update. But it remains. Kindly guide me.

      • WPBeginner Support says

        If you have tried deactivating all your WordPress plugins, then try this.

        Connect to your website using an FTP client. In the root directory you will find a .htaccess file. Download it to your computer. Delete the original file from your website. Visit your site’s admin area and go to Settings » Permalinks. Do not change any settings on the page, just click on the save changes button. Check your website to see if the error has resolved.

        Administrador

        • Muhammad Awais Sarwar says

          Thank you for you kind reply.
          I solved the problem last night after post here.


          This is the solution and how to fix it:
          In our wp-config.php, we overwrite the given server-variables that cause the problem by adding this below your database-configuration in wp-config:

          if(isset($_SERVER[‘HTTP_X_FORWARDED_FOR’])) {
          $list = explode(‘,’,$_SERVER[‘HTTP_X_FORWARDED_FOR’]);
          $_SERVER[‘REMOTE_ADDR’] = $list[0];
          }
          $_SERVER[ ‘SERVER_ADDR’ ] = DOMAIN_CURRENT_SITE;
          $_SERVER[ ‘REMOTE_ADDR’ ] = DOMAIN_CURRENT_SITE;
          $_SERVER[ ‘HTTP_HOST’ ] = DOMAIN_CURRENT_SITE;


          I saw this link.
          You all can visit it. Thank God, I was trying for three days. Thank you all of you.

  17. Martin Fuller says

    Hi, I ran into this problem today. I knew the name of the plugin causing the problem and engaged a consultant.

    He had access to my cPanel. Somhow he was able to deactivate the problem plugin but would not tell me how he did it.

    Do you have any idea how he might have done it?

  18. Elaine says

    Thank you. I installed a bad plug-in updated and got the white screen of death. Your clear explanation helped me restore the correct plug-ins and regain access to my site.

  19. Rhyauna says

    I followed all of the steps and was able to deactivate my plugins, but when I tried to activate them again, it gave me a white screen. Not sure whats going on. Please help

  20. MagK says

    When I got the “white screen of death”, I did not even panic for a minute and instead went straight to your site, I knew I would find a solution here.
    Thank you very much for all the advice and resources you make available.

  21. mike rigley says

    Thanks – killing the plugins folder via FTP worked great for me :) Now I can update them and reactivate if needed :)

    thanks
    mike

  22. Nick Karvounis says

    OMG! You saved my day, I had installed a security plugin that only allowed me to login from a specific IP address and I could not log in through FTF, thank you for the php access instructions!

  23. Saurabh Gupta says

    Brilliant writeup, simple and easy. Our environmental blog Earth5R had this critical problem where authors and admin could not log it, applied this solution and it worked like magic. There was one of the few unnecessary plugins that was causing the problem. That also bring a lesson, keep only the most necessary plugin! Thanks a lot, that was such a time save.

  24. Jonathan says

    Thanks! I could get to my wordpress site, but not into the admin area. I got a fatal error because of a cache plugin. I did this to get it to the admin, deleted and reinstalled the plugin, and it’s working fine.

  25. Yarina says

    None of this worked for me… but then I switched to Internet Explorer and now I can access my wp dashboard. The site has always been live. Any ideas of what could be causing the issue in Chrome?

  26. Chris says

    Thank you. Problem was a bad plugin upgrade. Using FTP and changing plugin directory name, instantly gave back my ability to get to the wp-login page, then change the plugin directory back again via FTP allowed me to re-activate plugins in turn, thereby identifying the dodgy plugin easily. This was incredibly helpful and resolved my problem. Thanks you.

  27. Ron Blake says

    Great article. Thank you! Bad plug-in and using the plugin.deactivate rename was a lot easier than trying to do it through the admin panel.

  28. John Detlefs says

    You. Rock. This article just made me a couple of grand and saved me from having to redo a week’s worth of work. Thankyou very much!

    Specifically, changing debug to “True” made life a whole lot easier. :)

  29. Ashley says

    Someone can help me please i did this through my FTP but i still have the “reauth=1 ” after that i deactivate my plugins folder. Thank You

  30. flafin says

    Great post, thank you!
    I got an Internal Server Error while trying to add tracking code to my functions.php file through the editor on WP. After getting the error I removed the code from the file, which should have fixed it, but I still had the error. I opened the file manager in my hosting account and navigated to the functions.php file. When I opened it the code that caused the error was still in the file. Once I removed the code the error went away. Hope this helps.

  31. anticrap says

    amazing. i’m a complete novice at all of this and you made it so easy to sort out this problem. thank you so much

Responder a sharmila Cancelar respuesta

Gracias por elegir dejar un comentario. Tenga en cuenta que todos los comentarios son moderados de acuerdo con nuestros política de comentarios, y su dirección de correo electrónico NO será publicada. Por favor, NO utilice palabras clave en el campo de nombre. Tengamos una conversación personal y significativa.