How to troubleshoot Issues in your Community Site
Since BuddyPress runs on WordPress, you can encounter a number of errors either arising from theme conflicts, plugin conflicts or bugs.
Within this lesson, we will cover how to troubleshoot these issues within your community site.
To have this accomplished you can carry out the following steps if you still have access to your WordPress dashboard:
- Navigate to the Plugins section within your dashboard
- Disable all plugins except BuddyPress
- Check whether the issue is resolved. If so, reactivate the plugins one by one to identify the conflicting plugin. If not, reactivate the plugins.
If you do not have access to the WordPress dashboard, you can access your site files via CPanel file manager or FTP.
Here, you will need to carry out the following:
- Navigate to the public_html/site folder/wp-content/plugins directory path
- From the plugins list, add the suffix old to all the plugin name folders except BuddyPress plugin folder. Below is a sample illustration.
- Try accessing your WordPress dashboard as well as site, and check whether the issue is resolved. If not, undo the changes.
- Navigate to the Appearance > Themes section within your WordPress dashboard if you are still in a position to access the dashboard
- Activate a default WordPress theme such as the Twenty Twenty One theme
- Check whether the issue is resolved. If solved, then you need to contact your theme support.
If you do not have access to the WordPress dashboard, again you can access your site files via CPanel file manager or FTP.
To do so;
- Navigate to the public_html/site folder/wp-content/themes directory path
- From the themes list, add the suffix old to your previously active theme name folder.
Below is a sample illustration:
Try accessing your WordPress dashboard as well as site, and check whether the issue is resolved.
Turning on debugging within your WordPress site will help in logging errors being reported by your site.This will help you in identifying the culprit code or software.
To have this accomplished, you will need to access your site files still via CPanel or FTP and:
- Navigate to the public_html/site folder/ directory path and select to edit the wp-config.php file
- On the line just before “/* That’s all, stop editing! Happy publishing. */”, add the following code snippets:
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
We leave WP_DEBUG_DISPLAY as false to avoid this information being displayed on the frontend and help in preventing exploitation by hackers.
- Save your changes
- Access your site where the issue is triggered from
- Navigate to the public_html/site folder/wp-content/ directory path
- Access the debug_log file now in place and open it to view the errors rendered
Ensure that you check the errors that are reported within that day and time.
If the errors listed are plugin or theme related, then you need to consult the respective support teams on them. If it’s a more general issue such as a file error, then you need to consult a developer to assist with the repair.