Fixing the Loco Translate 'Blank Page' When Adding a New Language

One of the most common issues users report with the Loco Translate plugin is encountering a completely blank page when trying to perform a key action, such as clicking "New Language" or "Upload .PO file." This problem can be incredibly frustrating because it provides no error message to work with. Based on extensive community reports and troubleshooting, this article explains the likely causes and provides a step-by-step guide to resolve the issue.

Why Does This Blank Page Happen?

A blank white screen in WordPress typically indicates that a PHP error has occurred, but error reporting is turned off, so the message is hidden. In the context of Loco Translate, this is often not a bug in the plugin itself but a conflict with another piece of software on your site. The error could be triggered by:

• A conflicting WordPress plugin or theme.
• A JavaScript error caused by another script.
• Browser extensions, such as ad-blockers or privacy tools, that interfere with the page's content.
• Specific code designed to hide administrative notices.

How to Troubleshoot and Fix the Blank Page

Follow these steps to identify and eliminate the cause of the blank page.

Step 1: Enable WordPress Debugging

The first step is to reveal any hidden PHP errors. You can do this by enabling WordPress debug logging.

1. Access your website's files using FTP or your hosting provider's file manager.
2. Locate the wp-config.php file in your root WordPress directory.
3. Open the file for editing and find the line that says define( 'WP_DEBUG', false );.
4. Replace it with the following lines:

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

5. Save the file and upload it back to your server.
6. Now, reproduce the blank page by clicking "New Language" in Loco Translate.
7. Check for a new file called debug.log in the /wp-content/ directory. Any errors generated will be logged here, providing a crucial clue.

Step 2: Check the Browser Console for JavaScript Errors

Since the Loco Translate interface relies on JavaScript, an error from another plugin can break it entirely.

1. While on your WordPress admin page, right-click and select Inspect.
2. Click on the Console tab.
3. With the console open, click the "New Language" button in Loco Translate.
4. Look for any red error messages in the console. These errors often point to the conflicting script.

Step 3: The Most Common Fix: Conflict Testing

If the steps above don't reveal a clear error, the most effective method is to test for a plugin or theme conflict.

1. Deactivate All Other Plugins: Go to Plugins → Installed Plugins and deactivate every plugin except Loco Translate.
2. Test: Try to add a new language again. If it works, you know a plugin is causing the conflict.
3. Reactivate One-by-One: Reactivate your plugins one by one, testing the "New Language" button after each activation. When the blank page returns, you have found the conflicting plugin.

Community-Note: Users have specifically reported conflicts with plugins like Admin Notices Manager, Hide Admin Notices, and various ad-blocking or speed optimization tools. Pay close attention to these if you have them installed.

Step 4: Switch to a Default Theme

If deactivating all plugins didn't help, the conflict might be with your theme.

1. Go to Appearance → Themes.
2. Temporarily switch to a default WordPress theme like Twenty Twenty-One or Twenty Twenty-Four.
3. Test if Loco Translate works with the default theme.

Step 5: Disable Browser Extensions

Try accessing your WordPress admin in an incognito/private browser window with all extensions disabled. If the blank page is gone, a browser extension (like an ad-blocker) is the culprit.

Conclusion

The infamous Loco Translate blank page is almost always a symptom of a conflict elsewhere in your WordPress setup. By methodically enabling debugging, checking for JavaScript errors, and performing conflict isolation, you can almost always identify and resolve the underlying cause. The key is to be patient and test each component individually.

If you discover a specific plugin causing the issue, check its settings for options to disable it on admin pages or consider reaching out to that plugin's support for further assistance.