Home›Support›English Support›[Resolved] The language changes when switching between the site pages and the profile.
[Resolved] The language changes when switching between the site pages and the profile.
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue where switching between the profile and the main page results in being taken to different language versions of the site. Specifically, navigating from the Ukrainian or Russian version to the main page redirects to the English version instead of staying on the same language. Solution: 1. We found that the menu links for the profile were not translated. To resolve this, we recommend creating a Custom Link in the menu for the profile page in each language. This can be done by visiting the profile in each language, copying the page URL, and then adding it as a Custom Link in your menu. 2. If clicking the profile icon redirects to the profile in the default language, this is due to the theme generating the link dynamically based on the user's session. This behavior is not translatable by WPML and would need to be addressed by the Theme Author.
We asked WPLMS for help, but they referred us to you. hidden link
Please tell us how to solve this issue: When I switch between the profile and the main page, it takes me to different languages. If I am in the Ukrainian or Russian version, then when I go to the main page of the site, it takes me to its English version, but I must stay in Ukrainian (for example).
Hello,
thank you for sharing the video! I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to a testing site where the issue is replicated.
You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this:
After analyzing your website, I noticed that the "Loggedin Menu UA" doesn't have the proper translations for the custom links. To resolve your issue, please follow these steps:
1) Go to Appearance > Menus and select the Loggedin Menu UA;
2) On the bar above the menu items select a second language (Ukranian, for example) by clicking on the pencil next to it;
3) Select the first menu item "<span class="vicon vicon-home"></span>Головна";
4) Add "/uk/" to the end of the link, to indicate it must be the home page in Ukranian;
5) Do the same for Russian, adding /ru/;
The problem was, that these custom links were without the language on the URL, so they were always taking the user to the English version, which is the default one.
Hi Lucas =)
I have followed the steps you described above but unfortunately, it didn`t help... hidden linkhidden link
The video is here hidden link
Also, in the Russian menu, I noticed an extra item from another language, and this happens not only in Russian but in Ukrainian but situationally. hidden link
Hello,
I understand, thank you for sharing. To better assist you, I need to deactivate plugins, run scripts and test different WPML configurations. Those things can break the website, that's why I asked you to recreate the problem in the Sandbox environment. Could you please reach out to your theme's support and check if it's possible to have a key for development purposes? As I said, it really makes it easier for us to narrow down the cause of your issue.
The access you sent me is from development, correct? It's best to make sure. If it is, I can already test different configurations and see if I find any conflicts.
Hello!
Please do not close the ticket, we are working on many issues at the same time and we need more time. I will be very grateful for your understanding.
your ticket won't be closed. Did you have the chance to see if we can reproduce the error on a Sandbox? As I said, it really helps us to debug your issue.
Can you confirm that the access you sent is for a staging/development version of your website? This way I can test different approaches without damaging the live version of your website.
I'm waiting for your feedback, so I can further support you.
thank you for the long wait!
We've made a backup and now you can do whatever you need to do to fix the problem.
Please inform us of any results, we will be looking forward to it.
Thank you for your response and for providing access to your website. However, for us to effectively investigate and resolve the issue, it is essential that our support team works in an isolated environment. This is crucial for two reasons:
Safety: Working on a live site, even with backups, poses risks. Any changes or debugging processes might affect the live environment and your users.
Protocol: Our policy mandates that all escalated issues are examined in a controlled environment, such as a Sandbox or a staging site. This ensures accurate diagnosis and resolution without interference from the live site's ongoing activities.
I understand this might be an inconvenience, but it's a necessary step to ensure the highest quality of service and maintain the integrity of your live site. Please let me know if you need assistance in setting up a Sandbox or staging version. Your cooperation is greatly appreciated.
Thank you for sharing. I escalated your issue to our development team and will get back to you as soon as I have new information, as they are looking for a permanent solution to your issue. Meanwhile, have a nice day 🙂
I didn't receive any feedback from our development team yet, we have a high workload and the holidays, so it's probable it's going to take a few days until we have an answer. Just to give you some context, the issue seems to be specifically happening in your environment. As I stated, when refreshing the page without cache the menu works as expected, but there's something overwriting it. That's what they are investigating at the moment. Thank you for your patience! I'll give you feedback as soon as hear from our developers.
