Similar issue

  • Resolved ll09

    (@ll09)


    5 years, 7 months ago

    Hi,

    I have a similar issue to – https://wordpress.org/support/topic/unable-to-access-dashboard-of-site/

    When I try the following, I get the critical error:

    > Logging into wordpress. When refreshing the page to /wp-admin/ I can view the interface of the admin panel tho.
    > Adding a new post: Posts -> Add New (/post-new.php)
    > Adding a custom link to a Menu does nothing. It’s just stuck on trying to add it.

    I’ve gone through the plugin troubleshooting method originally to revert to a previous version of the plugin to see if it was an issue with the current/latest version of the plugin, so I had renamed the plugin folder to auto-deactivate the plugin. When I try to reactivate the plugin, I got:

    “Plugin could not be activated because it triggered a fatal error.”

    Even with the plugin deactivated, I still get the error. So I assume there might be something still in the database affecting it, or maybe WP Rocket is caching something. I haven’t deleted the folder but I have deleted the previous plugin version that I uploaded that wouldn’t activate through WP Admin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Temyk

    (@webtemyk)

    5 years, 7 months ago

    Hello.

    To understand what happened, we need to look at the errors. To do this, enable debug mode – add these lines to the wp-config.php file:

    define( 'WP_DEBUG', true ); 
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

    After that go to the error screen page.
    Error messages will appear in the wp-content/debug.log file. Send them all here

    Thread Starter ll09

    (@ll09)

    5 years, 7 months ago

    Can you send me a contact email so I can forward you some information/files that may help you reproduce this on your test site?

    Going into safe mode helped solve this issue but I’m unable to go into safe mode because the addon is deactivated and it wouldn’t let me reactivate it because of a fatal error. This error is not logged in the debug log. No idea why.

    The first error mentions Woody because there is a problem and it asks you to go into safe mode.

    Changing themes doesn’t help.
    I’m afraid to deactivate addons one by one in case they can’t be reactivated.

    From my research, this plugin has a history with these types of errors too.

    Thread Starter ll09

    (@ll09)

    5 years, 7 months ago

    I think I’ve resolved this issue for now.

    Disabling Sucuri Security seemed to have fixed it. Maybe the Woody plugin displays these errors and ask to enter safe mode whenever their is an error, regardless of if it’s to blame or not.

    There was nothing of importance in the debug file, so that error is a bit misleading.

    Temyk

    (@webtemyk)

    5 years, 7 months ago

    Woody does add information about himself to the error message, but this does not mean that woody is to blame. It’s good that the problem was solved.

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

The topic ‘Similar issue’ is closed to new replies.