Is it in the menu? Can we see it?
@dbardaji To help, we need to see your site. Please post the URL here and tell us exactly where the link is.
Thank you!
P.S. Closing this issue for now. Please reopen when you reply.
Same problem as described by Dbardaji.
My site:
http://ok-led.com.ua/
The external link is second in the menu and it normally should look like:
http://td-odeskabel.com.ua/
In ru translation it changes to:
http://td-odeskabel.com.ua/ru/
Excuse me please, if it has been already discussed elsewhere, but it’s the only topic I found.
@john.Borovski
OK, so that’s a custom link in menu, and WPGlobus is localizing the URL, thinking it was an internal one.
Could be a bug related to the two-part TLD… Will check ASAP.
Thanks for reporting!
@tiv.NET INC.
Thanks for response!
A temporary workaround for anyone who has the same problem is to set default language of your site as of the one referred by the link.
This will work only if your site has same translations as the one being referred.
Unfortunately, I’ve entered wrong lang code/locale code at configuration step, so it won’t work for me, unless I find a way to change the codes without loss of translations.
P.S. Actually, such plugin behavior could be a nice integration feature, if it only could be switched on/off…
@john,
Bug confirmed: it’s only for two-part TLDs. If your site (or the external link) is a regular .com / .org etc – all works…
Working on the fix now.
Thanks
The fix has been posted to GitHub:
https://github.com/WPGlobus/WPGlobus/commit/e0c8e8747f738eb327ce8a1521e9ea667e358540
and will be included in the version 1.2.9 of WPGlobus
Thanks again for reporting this issue.
@tiv.NET INC.
Great! Thank you for your work!)
I didn’t even expect that the fix will come up so fast.
Hey Guys, I am having this same issue with a site. I think it is do to the use of sub domains. So the domains are structured as such:
– ‘blog.mydomain.com’ with external links pointing to ‘mydomain.com’
– ‘mydomain.com/about-us’ becomes ‘mydomain.com/uk/about-us’
I’m using 1.4.8
Any suggestions?
It’s not the same issue. Thanks for posting it on Github also.
We’ll take a look.
