Title: msousa's Replies | WordPress.org

---

# msousa

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Kadence Security – Password, Two Factor Authentication, and Brute Force Protection] Multi-language login fails after 'Hide backend' enabled…](https://wordpress.org/support/topic/multi-language-login-fails-after-hide-backend-enabled/)
 *  [msousa](https://wordpress.org/support/users/msousa/)
 * (@msousa)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/multi-language-login-fails-after-hide-backend-enabled/#post-7071851)
 * Any chance you have a multisite instalation?
    Just found out, because of reset
   password, that I needed to insert the following line at ./core/modules/hide-backend/
   class-itsec-hide-backend.php at line 50 (just after site_url one)
 *     ```
       add_filter( 'network_site_url', array( $this, 'filter_login_url' ), 10, 2 );
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[W3 Total Cache] W3 Total Cache – Issues with HTTP 301/302 PageCache [workaround]](https://wordpress.org/support/topic/w3-total-cache-issues-with-http-301302pagecache-workaround/)
 *  Thread Starter [msousa](https://wordpress.org/support/users/msousa/)
 * (@msousa)
 * [10 years, 12 months ago](https://wordpress.org/support/topic/w3-total-cache-issues-with-http-301302pagecache-workaround/#post-6146725)
 * Thank you both for your comments, and in one of the cases I’d also noticed the
   hook that was getting called wasn’t get_header and read it should be.
 * However I didn’t go this route since this issue also happens with plugins we 
   don’t develop, such as the domain mapping one, and probably others.
 * I don’t think there’s any case in which the W3TC, as it’s working now, should
   cache the 301/302 and as such opted to deliver the workaround at the W3TC plugin
   instead of all possible plugins that might have the wrong hook.
 * The plugins should fix the issue, but W3TC shouldn’t cache responses that will
   produce issues. 404 already has the exception, 301/302 have caused issues to 
   me and other, but probably anything other then 200 shouldn’t be cached.

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