Author: Leon Wimmenhoeve
Complianz GDPR free WordPress plugin
The last months we have been working hard on our full service GDPR plugin for WordPress, and yesterday we have released the free version of the Complianz GDPR WordPress plugin. This plugin is meant for website owners with visitors in the European Union, who want to comply with the new GDPR privacy regulations. There are a lot of cookie warning plugins around, and a lot GDPR tools available, but Complianz GDPR provides the website owner not only with a cookie
Is your website GDPR compliant?
With the upcoming stricter privacy laws, GDPR, a lot of website owners are asking themselves if their site is ready for this new law. Right now we’re working on a plugin which will help you get your site ready. Let Complianz handle the GDPR for your website! The Complianz GDPR plugin will generate the required privacy statement, cookie statement and other required documents (like the processing contract) for you based on your website configuration, used cookies, and your answers to
Really Simple Security and GDPR
As a result of modern privacy and cookie regulations (e.g., GDPR), some users have been asking if Really Simple Security is compliant and whether the plugin performs any user tracking. Because Really Simple Security does not process personal identifiable information, the GDPR does not apply to these plugins or usage of the plugin on your website. If you need a GDPR (EU) or CCPA (US) solution for a Privacy Policy and Cookie Policy for your website, please take a look
htaccess redirect to https may cause redirect to 401.shtml when using password protection
When using the .htaccess to add password protection to your site in combination with the .htaccess 301 redirect added by Really Simple Security; this could result in a redirect to URL’s such as: https://example.com/401.shtml. A simple solution that has been reported to work is to add the following line: ErrorDocument 401 default To the top of your .htaccess file. So, the end result looks approximately like this (the error document should come before the password lines): # Error Document ErrorDocument
How to solve a http 500 error on activation of Really Simple Security
When you get a white screen or a “500 Internal Server Error” after activating Really Simple Security, this can have a number of different causes; but it is almost always due to a fatal PHP error. A common cause of such issues is insufficient memory on the server, but a 500 error can also be caused by invalid .htaccess rules, for instance: a syntax error, or when the plugin’s advanced-headers.php is included in the auto_prepend_file directive, while the file does