When the Site Editor fails to load in DigiFlash, you’ll typically see a blank screen, infinite loading spinner, or error message. This prevents you from accessing templates, template parts, and global styles.
Clear Browser Cache and Cookies
Start with a hard refresh by pressing Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac). If the Site Editor still doesn’t load, clear your browser’s cache and cookies completely through your browser settings, then restart the browser.
Disable Browser Extensions
Browser extensions, particularly ad blockers and privacy tools, can interfere with the Site Editor. Open your browser in incognito/private mode or disable all extensions temporarily. If the Site Editor loads, reactivate extensions one by one to identify the problematic one.
Check JavaScript Console for Errors
Open your browser’s developer tools (F12 or right-click > Inspect) and click the Console tab. Refresh the Site Editor page and look for red error messages. These errors often indicate the source of the problem, whether it’s a plugin conflict or missing resource.
Deactivate Conflicting Plugins
Certain plugins interfere with the Site Editor’s functionality. Deactivate all plugins by going to Plugins > Installed Plugins, selecting all plugins, choosing “Deactivate” from the bulk actions menu, and clicking Apply.
Access the Site Editor at Appearance > Editor. If it loads, reactivate plugins individually to find the conflict. Common culprits include:
- Optimization plugins with aggressive JavaScript minification
- Security plugins blocking REST API requests
- Page builders and legacy theme builders
- Custom admin interface plugins
Verify REST API Functionality
The Site Editor requires the WordPress REST API. Test if your REST API works by visiting this URL (replace yoursite.com with your actual domain):
https://yoursite.com/wp-json/wp/v2/templatesYou should see JSON data. If you get a 404 error or blank page, your REST API is blocked. Check your security plugin settings or .htaccess file for rules blocking the REST API.
Increase PHP Memory and Execution Time
The Site Editor requires adequate server resources. Add these lines to your wp-config.php file before “That’s all, stop editing”:
define('WP_MEMORY_LIMIT', '256M');
define('WP_MAX_MEMORY_LIMIT', '512M');Also increase PHP execution time by adding this to your .htaccess file:php_value max_execution_time 300
Check Permalink Settings
Incorrect permalink structure can break the Site Editor. Go to Settings > Permalinks and click “Save Changes” without making any modifications. This refreshes the permalink structure.
Disable Conflicting .htaccess Rules
Some .htaccess rules block the Site Editor’s AJAX requests. Connect via FTP, download your .htaccess file as backup, then temporarily rename it to .htaccess.old. Try loading the Site Editor. If it works, your .htaccess contains problematic rules.
Switch to a Default Theme Temporarily
Activate a default WordPress block theme like Twenty Twenty-Four. If the Site Editor loads with the default theme but not with DigiFlash, reinstall DigiFlash with a fresh copy from your original source.
Check File Permissions
Incorrect permissions prevent WordPress from loading Site Editor files. Connect via FTP and verify:
- wp-content/themes/digiflash: 755
- All theme files: 644
Verify WordPress Version
DigiFlash requires WordPress 6.0 or higher for Full Site Editing. Check your version in Dashboard > Updates. If you’re running an older version, update to the latest WordPress release.
Disable CloudFlare Rocket Loader
If using Cloudflare, the Rocket Loader feature can break the Site Editor. Log into your Cloudflare dashboard, go to Speed > Optimization, and disable Rocket Loader. Clear Cloudflare’s cache afterward.
Check for Server Timeout Issues
Contact your hosting provider if the Site Editor starts loading but times out. They can increase server timeout limits or identify server-side resource restrictions preventing the Site Editor from loading completely.
Examine Error Logs
Access your WordPress debug log or server error log to identify specific errors. Enable WordPress debugging by adding this to wp-config.php:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);Check wp-content/debug.log for error messages related to the Site Editor.
Reset User Preferences
Corrupted user preferences can prevent Site Editor access. Install the “User Session Control” plugin, go to Users > All Users, select your user, and clear user meta related to the Site Editor. Alternatively, create a new administrator account and test if the Site Editor loads for that user.