A “white screen” issue, otherwise called the WordPress White Screen of Death (WSOD), can happen because of different reasons, and it’s not really well defined for a conflict among Jetpack and Gantry. In any case, potential struggles between various modules or subjects can prompt this issue. This is the way you can investigate and possibly resolve the issue:
Cripple Modules: Begin by deactivating all of your WordPress modules. You can do this by renaming the “modules” envelope in your WordPress establishment registry through FTP or cPanel. Subsequent to renaming it, make another unfilled organizer with a similar name (“modules”). This will deactivate all modules. Check assuming that the white screen is no more. In the event that it is, one of the modules was probable causing the issue.
Actuate Modules Individually: If impairing all modules settle the issue, enact them individually to distinguish which one is causing the contention. This will assist you with pinpointing the tricky module.
Howdy!
As an initial step here, could you kindly erase Jetpack and afterward reinstall it? You can follow these moves toward do that:
- Begin at Plugins → Installed Plugins.
- Assuming Jetpack is presently dynamic, click Deactivate to debilitate it. Then, at that point, click Delete to eliminate it from your site:
- Go to Plugins → Add New.
- Look for “Jetpack by WordPress.com”.
- Click Install and afterward Activate.
At the point when Jetpack is introduced, click the green Set up Jetpack button to reconnect.
Actually look at Subject Similarity: Assuming the issue continues to happen in the wake of deactivating all modules, the following stage is to check your WordPress subject. Briefly change to a default WordPress subject (e.g., Twenty 21) to check whether the white screen vanishes. On the off chance that it does, there might be a similarity issue between your ongoing subject (e.g., Gantry) and other modules.
Update Everything: Guarantee that WordPress, your subject, and all modules are refreshed to their most recent forms. Obsolete programming can once in a while cause clashes or weaknesses.
Check Blunder Logs: Search for mistake signs on your web server or in your WordPress establishment. These logs can give more unambiguous data about the issue. In the event that you don’t know how to get to blunder logs, check with your web facilitating supplier or utilize a module like “WP Troubleshooting” to log mistakes.
Memory Cutoff: at times, a white screen can be brought about by arriving at the PHP memory limit. You can have a go at expanding as far as possible by altering your site’s wp-config.php document or reaching your facilitating supplier for help.
Investigating: Empower WordPress troubleshooting to check whether any PHP mistakes are being shown. Add the accompanying lines to your wp-config.php record:
php
Duplicate code
define(‘WP_DEBUG’, valid);
define(‘WP_DEBUG_LOG’, valid);
define(‘WP_DEBUG_DISPLAY’, bogus);
This will log blunders to a debug.log document in the/wp-content/registry without showing them on the screen.
Counsel Backing: Assuming you can’t determine the issue all alone, consider contacting the help groups of the dangerous modules or subjects (Jetpack and Gantry for this situation). They might have experienced comparable contentions and can give direction or updates to determine the issue.
Reinforcement: Prior to rolling out any critical improvements to your site, consistently back up your WordPress establishment and information base to guarantee you can reestablish it assuming that something turns out badly.
Recall that investigating a white screen issue can at times be perplexing, and it could require persistence and purposeful testing to recognize and determine the main driver.
Recover