Title: WPML compatibility problem
Last modified: August 16, 2022

---

# WPML compatibility problem

 *  Resolved [RichardMisencik](https://wordpress.org/support/users/richardmisencik/)
 * (@richardmisencik)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/wpml-compatibility-problem/)
 * Hello, the plugin is sadly not compatible with WPML – domain per language setup.
   On the secondary domain if i visit /secretlogin i’m redirected to main domain(
   basically 404) because of invalid permalink but when disabling this plugin and
   using classic /wp-login i’m correctly redirected to the login screen.
 * Is there a way around this please?

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

 *  Plugin Support [MaximeWPS](https://wordpress.org/support/users/seinomedia/)
 * (@seinomedia)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/wpml-compatibility-problem/#post-15923172)
 * Hello,
 * Thanks for using WPS Hide Login.
 * This issue isn’t caused by WPS Hide Login but WPML. It has already been reported
   and solved here and in WPML’s forum :
    [https://wpml.org/forums/topic/wps-hide-login-secondary-language-logout-error/](https://wpml.org/forums/topic/wps-hide-login-secondary-language-logout-error/)
 *  Thread Starter [RichardMisencik](https://wordpress.org/support/users/richardmisencik/)
 * (@richardmisencik)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/wpml-compatibility-problem/#post-15941893)
 * Hello,
    thanks for a reply, I’ve read the thread and saw the fix they provided
   for “/classes/plugin.php” in WPS Hide Login.
 * But if it has been patched why am I running into the same issue again? Is it 
   possible it’s a new error?
 *  Plugin Support [MaximeWPS](https://wordpress.org/support/users/seinomedia/)
 * (@seinomedia)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/wpml-compatibility-problem/#post-15942044)
 * Hello,
 * It’s not the same.
 * You’ve to add `return $this->user_trailingslashit( site_url( '/', $scheme ) .
   $this->new_login_slug() );` whereas you found `return $this->user_trailingslashit(
   home_url( '/', $scheme ) . $this->new_redirect_slug() );`
 *  Thread Starter [RichardMisencik](https://wordpress.org/support/users/richardmisencik/)
 * (@richardmisencik)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/wpml-compatibility-problem/#post-15956063)
 * Hello,
    to be sure, are we talking about line 203 in that file? Is it possible
   to add a wpml compatibility check in the plugin core to avoid overwrites with
   updates? Thanks.

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

The topic ‘WPML compatibility problem’ is closed to new replies.

 * ![](https://ps.w.org/wps-hide-login/assets/icon-256x256.png?rev=1820667)
 * [WPS Hide Login](https://wordpress.org/plugins/wps-hide-login/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wps-hide-login/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wps-hide-login/)
 * [Active Topics](https://wordpress.org/support/plugin/wps-hide-login/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wps-hide-login/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wps-hide-login/reviews/)

## Tags

 * [permalink](https://wordpress.org/support/topic-tag/permalink/)
 * [redirect](https://wordpress.org/support/topic-tag/redirect/)

 * 4 replies
 * 2 participants
 * Last reply from: [RichardMisencik](https://wordpress.org/support/users/richardmisencik/)
 * Last activity: [3 years, 9 months ago](https://wordpress.org/support/topic/wpml-compatibility-problem/#post-15956063)
 * Status: resolved