Title: Really Simple Plugins's Replies | WordPress.org

---

# Really Simple Plugins

  [  ](https://wordpress.org/support/users/reallysimpleplugins/)

 *   [Profile](https://wordpress.org/support/users/reallysimpleplugins/)
 *   [Topics Started](https://wordpress.org/support/users/reallysimpleplugins/topics/)
 *   [Replies Created](https://wordpress.org/support/users/reallysimpleplugins/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/reallysimpleplugins/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/reallysimpleplugins/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/reallysimpleplugins/engagements/)
 *   [Favorites](https://wordpress.org/support/users/reallysimpleplugins/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Complianz - GDPR/CCPA Cookie Consent] Compatibility Issue with WPIDE Plugin](https://wordpress.org/support/topic/compatibility-issue-with-wpide-plugin/)
 *  [Really Simple Plugins](https://wordpress.org/support/users/reallysimpleplugins/)
 * (@reallysimpleplugins)
 * [2 years ago](https://wordpress.org/support/topic/compatibility-issue-with-wpide-plugin/#post-17547543)
 * You can use the filter cmplz_cookie_blocker_output to strip off the attribute.
   It is not required for front-end functionality, only to confirm the blocker is
   working as expected. So you can safely remove it.
 * add_filter(‘cmplz_cookie_blocker_output’, ‘my_cmplz_remove_attribute’);
   function
   my_cmplz_remove_attribute($html){ return str_replace(‘data-cmplz=1’,”,$html);
 * }
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Complianz - GDPR/CCPA Cookie Consent] Accepting the notice doesn’t mean anything](https://wordpress.org/support/topic/accepting-the-notice-doesnt-mean-anything/)
 *  [Really Simple Plugins](https://wordpress.org/support/users/reallysimpleplugins/)
 * (@reallysimpleplugins)
 * [5 years ago](https://wordpress.org/support/topic/accepting-the-notice-doesnt-mean-anything/#post-14230588)
 * To add a mu plugin, please follow these instructions:
 * [https://complianz.io/adding-filters-with-mu-plugins-quick-easy/](https://complianz.io/adding-filters-with-mu-plugins-quick-easy/)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] SSL certificate for 2 domains](https://wordpress.org/support/topic/ssl-certificate-for-2-domains/)
 *  Plugin Author [Really Simple Plugins](https://wordpress.org/support/users/reallysimpleplugins/)
 * (@reallysimpleplugins)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/ssl-certificate-for-2-domains/#post-13862784)
 * A workaround for this is to add a redirect to your main domain in the .htaccess
   file. This way, the domain is redirected before it is loaded in the user’s browser.
 *     ```
       <IfModule mod_rewrite.c>
         RewriteEngine On
         RewriteCond %{HTTP_HOST} ^domain1.com$ [OR]
         RewriteCond %{HTTP_HOST} ^www.domain1.com$
         RewriteRule (.*)$ https://www.maindomain.com/$1 [R=301,L]
       </IfModule>
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)] Can’t access wordpress admin console](https://wordpress.org/support/topic/cant-access-wordpress-admin-console/)
 *  Plugin Author [Really Simple Plugins](https://wordpress.org/support/users/reallysimpleplugins/)
 * (@reallysimpleplugins)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/cant-access-wordpress-admin-console/#post-13862767)
 * You have a 302 redirect to http on your wp-admin. Really Simple SSL redirects
   to https. This results in a redirect loop.
 * The easiest way to fix this is to remove the 302 redirect. It is probably a plugin,
   or a .htaccess rule.
 * To deactivate plugins, you can rename a plugin folder, which will effectively
   deactivate it (using FTP).
 * In the .htaccess file you can check for redirects to http, then remove that redirect.

Viewing 4 replies - 1 through 4 (of 4 total)