Background of the issue:
I am trying to switch between languages on my site, but the switcher does not refer to translated pages. The issue can be seen on this page: hidden link.
Symptoms:
I expected to see a translated site, but instead, I got a 'page not found' error. The error log shows multiple 'Unable to authenticate' messages with status 'auth_error'.
Questions:
Why does the language switcher not refer to translated pages?
What is causing the 'Unable to authenticate' error in the logs?
Is it possible for you to change those to the minimum requirement?
You may need to contact your hosting provider for that. Meeting those baseline requirements is critical before debugging and sometimes solves issues you experience. The most important thing is to raise the WP Memory Limit. Please try to raise it before you contact your hosting company. You can do it from the wp-config.php file in your WordPress installation. Insert this code in that file:
I updated the mem issue. that didnt resolve the issue. [in the problem solver it does show now 256m available] so the config file is now correctly updated.
what I do see, when I followed your steps, that there are no english translation available in the overview of pages. but If i click on the translations icon in the default language [dutch] I am forwarded to the translation which is available and completed. I pressed update and then update and close. But this still didnt bring forward the translated page.
Based on the screenshot you shared, I can see that you, probably by mistake, sent those English pages to the trash section. Please see the attached screenshot. You probably need to restore them from there.
good evening
yes I saw that and I did restore the english articles. but still having issues
If I switch to english and open the blog, the page is English but the articles are dutch. If I click on one of the articles, it will open the dutch version and the entire page switches back to the dutch side.
secondly: if I go to English / dashboard/ articles and click one of the articles [open sample] it does show the english version, however not the regular visual one, but the one of with the line codes in it
so if I go to the menu in the backend, the dutch version shows nicely in the side bar, the dutch pages, but the english menu shows none.
it also odd, that the WP dashboard, which normally switches with the language by choice, remains in dutch
You wrote: "yes I saw that and I did restore the english articles. but still having issues"
Is the initial problem of this ticket fixed after restoring the pages from the trash section?
You wrote: "If I switch to english and open the blog, the page is English but the articles are dutch. If I click on one of the articles, it will open the dutch version and the entire page switches back to the dutch side."
I can not see this problem on your site because I don't see the Language Switcher.
Have you deactivated WPML on your site? If yes, then what is the reason for this?
You wrote: "secondly: if I go to English / dashboard/ articles and click one of the articles [open sample] it does show the english version, however not the regular visual one, but the one of with the line codes in it
so if I go to the menu in the backend, the dutch version shows nicely in the side bar, the dutch pages, but the english menu shows none."
We focus on one issue per ticket in our technical support forum. Otherwise, tickets can get cluttered and confusing for both users and supporters. Please open new tickets with those other problems.
You wrote: "it also odd, that the WP dashboard, which normally switches with the language by choice, remains in dutch"
The admin (WP dashboard) language is set in your profile Users -> Profile. It is not supposed to change when you switch the Language Switcher at the top admin bar. Please read about it in the following guide.
If you need further help with this, please share the access details to your site with me. I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
I'm sorry for the late reply. The access details work now.
Since your site is in production (a live site), I need to take a copy and investigate this issue on a test server. I must install a plugin like Duplicator or All In One Migration for this. Please let me know if you agree.
I checked things on the copy of your site on our Cloudways server. I found that the 'page not found' error occurred for the following reasons. The English pages restored from the trash section were in the 'Draft' mode. After I edited the draft pages and changed their status to Published, the problem was solved. You can see a copy of your site on the server at this address:
hidden link
(For your information, search engines can't find this site. If you want to check things, you can log in to the copy of your site.)
I can see those English pages are in the draft status on your production site. Please see the attached screenshot.
To correct the problem on your production site, follow these steps.
1. Activate WPML and the Strings Translation plugins.
2. Go to Pages -> All Pages and switch to English.
3. Select the pages you want to publish.
4. Select' Edit' In the 'Bulk action' option and click Apply.
5. Switch the status to 'Published' and click the Update button. Please see the attached screenshot.
This should solve the problem. Please let me know how it goes.
If you have other issues with WPML, you can open a new ticket in our support forum. If you want me to continue to help you, please know I'll be available again on Thursday.
only thing I have to do, is adjust publishing dates, because now all english articles are published on 21/1/2025. which is out of order compared to the dutch version. but i know how to resolve that
