7.0.0-Beta Feedback
Instructions 7.0.0 wil be our next major release and will feature a simple approach to fending off and mitigating vulnerabilities in plugins,. themes and WordPress core. As you can expect from Really Simple SSL this has a simple configuration under settings, while the heavy lifting is done under the hood. In the best case scenario you will never find out what happens if a vulnerability is found, but if you want to try (safely) you can trigger some of Really
Email notification doesn’t show correct content
Email notifications are sent when triggered by certain features or possible updates from Really Simple SSL. This is what you need to know: The email is sent to your email, either defaulted to the admin email or, if entered, the email under General Settings. The email will trigger if needed, also if another administrator enables or disables a feature. Some emails are sent without previous action by an administrator. You can disable this feature under General Settings. If you are
About email notifications in Really Simple Security
Really Simple Security sends email notifications for important events, such as when features are enabled or when vulnerabilities are detected in installed plugins or themes on your WordPress site. To ensure that 2FA codes and security notifications are reliably delivered to your inbox, email address verification is required. You can verify your email address in the plugin by navigating to Settings -> Security -> General. This step is used to confirm that your server is properly configured to send email,
Steps to take after migrating to SSL
Step 1. Mixed Content Scan After installing Really Simple SSL and activating SSL, it is still possible that your site is flagged as not secure. The most common cause for this is ‘Mixed content’. If you do not see the secure lock in your browser address bar, you still have mixed content. It is very important that this is fixed because browsers will throw all sorts of warnings at users, who might get scared. Learn more about mixed content Step 2.
DISALLOW_FILE_EDIT is defined and set to “false”
When activating the “Disable the built-in file editors” feature under Settings > Hardening in Really Simple SSL, you may receive a notice that “the DISALLOW_FILE_EDIT constant is defined and set to false” as shown in the below image. When DISALLOW_FILE_EDIT has been defined in the wp-config.php with a false value, Really Simple SSL cannot override this. The solution is to remove the following line from your wp-config.php file: define( ‘DISALLOW_FILE_EDIT’, false );