• After I edited a plugin and update it. This problem happens. I try the troubleshooting method which is to deactivate all plugin using phpmyadmin. which is going to the wp_options and update its value to a:0:{}, theres also several wp_options in my database, which is wp_2_options, wp_3_options and wp_5_options, i considered doing the same for these, but doing it to the first one doesnt fix the problem so I skip it.

    Then, I also tried the file manager method, which is to rename the folder plugins to “plugins.hold” and followed all the steps, and still doesnt solve the problems

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator t-p

    (@t-p)

    – Errors like this are logged. Check the error log on your server. If you can’t find the log, please contact your host. – Meantime, enable wp_debug and wp_debug_log and after an error, look at wp-content/debug.log to see if anything gets logged there. https://wordpress.org/support/article/debugging-in-wordpress/
    – You can also try this: Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.
    – If you cannot access wp-admin, there are other ways to deactivate plugins: https://wordpress.org/support/article/faq-troubleshooting/#how-to-deactivate-all-plugins-when-not-able-to-access-the-administrative-menus

    Thread Starter jenzel

    (@jenzel)

    I already put the debug code in the wp-config.php, and i dont see any debug.log file in the root folder. Like i said, i already did the steps for the link youve gave me which is https://wordpress.org/support/article/faq-troubleshooting/#how-to-deactivate-all-plugins-when-not-able-to-access-the-administrative-menus. I did the steps. But nothing works

    Moderator threadi

    (@threadi)

    The debug.log file is stored in the wp-content directory, not in the root directory.

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

You must be logged in to reply to this topic.