My first step would be to turn on WP_DEBUG
in your wp-config.php file.
Edit wp-config.php and add the following lines:
define( 'WP_DEBUG', true );
Then visit your site’s admin (example.com/wp-admin) and see if an error appears. More than likely the plugin you just added broke the site, so you can go into your local filesystem (where WordPress is stored) and deactivate the plugin.
- Go to your WordPress install (via your File Explorer).
- Open wp-content/plugins/
- Find the plugin you just activated when things broke. Rename that folder to something else (example:
bad-plugin
renamed tobad-plugin-1
)
Now try to visit your site. By renaming the plugin it forces WordPress to deactivate it and it may bring the site back.
Here are some additional debugging tips for WordPress as well:
- https://wordpress.org/support/article/debugging-in-wordpress/
- https://www.a2hosting.com/kb/installable-applications/optimization-and-configuration/wordpress2/debugging-wordpress
- https://www.youtube.com/watch?v=cLNIARUfSj8
- https://www.youtube.com/watch?v=Nj2ziU6_0F8
Updated Answer
The comments of this answer revealed that the main issue was with the file path leading to the WordPress installation. The file path was localhost/wordpress%20G
, but the WordPress site_url parameter was set to localhost/wordpress/
.
By visiting the url localhost/wordpress%20G
, WordPress was rendered but was firing a 404 error. By renaming the folder to wordpress
(removing the space and letter G) the WordPress installation began to work as expected.