Troubleshooting Solid Security Notification Settings That Won't Save

Many users of the Solid Security plugin encounter a frustrating issue where changes to their notification settings fail to save. This often manifests as error messages like Default Recipients[user_list] must contain at least 1 item or From Email must match exactly one schema in oneOf, or the Save button may appear to load indefinitely without any confirmation.

Based on community reports and troubleshooting threads, this problem is typically not due to user error but often stems from bugs within the plugin itself or conflicts with other software. The good news is that there are several proven workarounds and solutions you can try.

Common Symptoms

• Error messages when clicking "Save All Changes".
• The save button spins or loads forever without completing.
• Settings appear to save but revert to their previous state when you navigate away and return.
• JavaScript errors in the browser console related to schema validation.

Why This Happens

The root cause can vary. Sometimes, a specific plugin update introduces a bug that interferes with the settings REST API or the user interface validation. In other cases, the issue is caused by a conflict with another plugin, your theme, or server configuration that blocks the necessary API requests.

Most Effective Solutions and Workarounds

Try the following solutions, starting with the simplest first.

1. Use the Default WordPress From Email Address

A very common workaround for the From Email must match exactly one schema in oneOf error is to format the "From Email" address in a specific way.

How to do it: If your website is www.example.com, set the "From Email" field to [email protected]. This specific format often satisfies the plugin's validation checks and allows the settings to be saved successfully.

2. Clear All Caching

Caching can sometimes serve old versions of the plugin's administrative interface or block the POST requests that save settings.

How to do it: Clear all types of cache you have running. This includes your browser cache, any caching plugins (e.g., WP Rocket, W3 Total Cache), your Content Delivery Network (CDN) cache (e.g., Cloudflare), and any server-level caching (contact your hosting provider for this). After clearing everything, log out and back into WordPress and try saving the settings again.

3. Check for Conflicts

A theme or plugin conflict is a frequent culprit behind settings not saving.

How to do it:

1. Temporarily switch your website to a default WordPress theme like Twenty Twenty-Four.
2. Deactivate all plugins except for Solid Security.
3. Attempt to change and save your notification settings.
4. If it works, reactivate your plugins one-by-one, testing the settings after each activation, to identify the conflicting software.

You can perform this test safely using the Health Check plugin, which allows you to troubleshoot without affecting your site's visitors.

4. Check for JavaScript Errors

Browser console errors can provide a direct clue about what is failing.

How to do it:

1. Open the browser's developer tools (usually F12).
2. Navigate to the "Console" tab.
3. With the Solid Security settings page open, click the "Save All Changes" button.
4. Look for any red error messages that appear in the console and search for them online for more specific guidance.

5. Verify REST API Access

Solid Security relies on the WordPress REST API to save its settings. If your server is blocking these requests, saving will fail.

How to do it: Contact your web hosting provider and ask them to verify that the following HTTP methods are enabled and not blocked by any server-level firewall: GET, POST, PUT, PATCH, DELETE, OPTIONS. The error "The response is not a valid JSON response" often points to this issue.

Conclusion

If you are struggling to save notification settings in Solid Security, you are not alone. This is a known issue that has affected many users across different versions. The most reliable first step is to set your "From Email" to the default [email protected] format. If that does not work, systematically work through disabling caching, checking for conflicts, and ensuring your REST API is fully accessible.

For ongoing issues, it is recommended to check the official SolidWP blog or community forums for updates, as the development team is typically aware of these bugs and may release a patch in a future update.