WGRank does not support logged-in user

umoekagodman0
(@umoekagodman0)

3 days, 18 hours ago

The user is logout on language switch.

If the user is browsing with any language other than the source language (English), the following cookie error is thrown when the user tries to login (first attemp):

“Error: Cookies are blocked or not supported by your browser. You must enable
cookies to use WordPress.” Actually, cookie is enabled in the Browser – Yandex Browser.

When the user clicks on login again (second attempt), the user would be logged-in to the site default language (English); if the user switch the language to any other one – the user would be logout.

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

Plugin Author Anil Singh
(@singhanilit)

3 days, 15 hours ago
Thank you so much for reporting this issue!

You are completely right. The issue was occurring because the plugin was rewriting the wp-login.php URL to a translated sub-directory (e.g. /fr/wp-login.php), which caused WordPress to fail its native cookie test. Additionally, the server-side caching engine was serving static cached pages to logged-in users, hiding their active sessions.

We have just released version 1.1.0 which includes a permanent fix for this:
1. wp-login.php and wp-register.php URLs are now completely excluded from translation rewrites.
2. Logged-in users will automatically bypass the static .html.gz server cache to preserve their active session state and admin bar visibility.
Please update the plugin to version 1.1.0 and let us know if everything works perfectly for you now!
Thread Starter umoekagodman0
(@umoekagodman0)

3 days, 10 hours ago

There’s no such thing as WGRank version 1.1.0 in the WordPress respository.

The available update version is 1.0.7 which does not solve any of the highlighted troubles.

Plugin Author Anil Singh
(@singhanilit)

3 days, 8 hours ago

Perhaps the update notification has not reached your WordPress dashboard yet, which is why version 1.0.7 is still being shown.

You can download the WGRank Translate plugin directly from the WordPress.org repository, where version 1.1.0 is available. Please download and install the latest version, then check if the issue is resolved.
Thread Starter umoekagodman0
(@umoekagodman0)

2 days, 23 hours ago
WGRank version 1.1.0 CURRENT LOGIN REDIRECT BEHAVIOUR

1. Regardless of the language one is browsing the site with, login button – on click, goes to:

https://example.com/wp-login.php?redirect_to=https%3A%2F%2Fexample.com%3A443%2Fmodel%2Fruddy%2F [NO LANG CODE – even if the user was at “https://example.com/pt/model/Fruddy/” (CASE A)]

OR

https://example.com/wp-login.php?redirect_to=https%3A%2F%2Fexample.com%3A443%2F [NO LANG CODE – even if the user was at “https://example.com/es/” (CASE B)]

2. If the user was browsing the site in any other language other than WGRank site source language (English) AND the user logged-in from CASE A URL, the user would be redirected to the WGRank site source language (English), instead of the language the user was browsing the site with before logged-in.

THE GOOD NEWS

i. window.location.pathname = https://example.com/model/Fruddy/ AND the page = the expected model page content – although in English.

ii. Site continue to browse normally/predictably in the WGRank site source language (English).

NOW THAT THE USER IS LOGGED-IN, IT’S TIME TO GO BACK TO ANY OF HER PREFER LANGUAGE, EXCEPT WGRANK SOURCE LANG (ENGLISH)

3. But, when she picked a language other than English, window.location.pathname = https://example.com/pt/model/Fruddy/ BUT page content = https://example.com/blog/

THE BAD NEWS

i. Only WP default pages, like About, Privacy Policy, Terms of Service… are accessible, but NOT translated, even though window.location.pathname = https://example.com/it/about/

ii. Theme pages like https://example.com/ru/model/Fruddy/ or https://example.com/pt/model/joy/ only shows https://example.com/blog/, even though window.location.pathname = https://example.com/ru/model/Fruddy/

This only happens when the user is logged-in. ⚠️

If the user is logged-out – everything behave predictably – when language is switch, page is translated, when window.location.pathname changes – page changes, etc.

4. LOGOUT button, goes to:

https://example.com/wp-login.php?action=logout&redirect_to=https%3A%2F%2Fexample.com%2F&_wpnonce=1dff144303 [expected WP/theme behaviour ✅]

⚠️ WGRank DEBUG LOG SHOWS ⚠️

[2026-08-11 11:06:53] Translator: User logged in. Bypassing server translation for security.
- This reply was modified 2 days, 23 hours ago by Steven Stern (sterndata).
- This reply was modified 2 days, 23 hours ago by Steven Stern (sterndata). Reason: format
- This reply was modified 2 days, 23 hours ago by Steven Stern (sterndata). Reason: replaced NSFW URL
- This reply was modified 2 days, 22 hours ago by Steven Stern (sterndata).

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

You must be logged in to reply to this topic.