[Resolved] Password-protect page not working for translated page.
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is trying to set a specific translated page to be password protected, but the password setting is not being retained when the Yoast SEO plugin is enabled.
Solution: If you're experiencing an issue where a translated page is not retaining its password protection setting when Yoast SEO is enabled, we recommend the following steps: 1. Navigate to WPML > Settings. 2. Scroll down to "Posts and pages synchronization". 3. Uncheck the options for "Synchronize passwords for password-protected posts" and "Synchronize private flag". 4. Save the changes. 5. Apply the password to the translated page/post and check again.
Please note that if you have existing password-protected pages or posts in the default language and you update their translations with the Password Synchronization option turned off, the translations will not inherit the password protection and will need to be manually password-protected.
Please note the return address is: phil@avalonmarketing.co.nz. I am supporting the hrmi website. I have created this staging site to resolve this problem.
I am trying to: set visibility of page to "password".
Link to a page where the issue can be seen: hidden link
I expected to see: password protection on page.
Instead, I got: password setting forgotten. Page displayed as normal.
I have changed theme to 2024 and deactivated all plugins, EXCEPT WPML and Yoast SEO. Fault only happens if Yoast SEO is enabled. If I deactivate Yoast SEO, it is possible to set visibility to "password" and for the setting to be retained.
I understand your concern about password-protected pages not functioning correctly in other languages. Based on the WPML Debug information, it appears that both the Private flag and Password synchronization are activated. This means that if a page is password-protected in the default language, its translated version should also be under password protection.
However, since you've noted that the issue doesn't arise when the Yoast SEO plugin is disabled, it suggests that some settings within Yoast might be conflicting with the password protection feature.
I recommend reaching out to the Yoast SEO support team to report this issue, as they might be better equipped to assist you in resolving it. On the other hand, if you suspect that WPML might also be contributing to the problem, please share the steps to replicate the issue with me. I will attempt to recreate it, and if I find any WPML-related issues, I will do my utmost to assist you in finding a solution.
Thank you for your quick reply. I regret I did not receive an alert.
I have reported the issue to Yoast SEO and await a response.
You commented:
> "if a page is password-protected in the default language, its translated version should also be under password protection."
Does this mean, it is important to password-protect the page in the default language? In my scenario, the default-language page is NOT protected, but the requirement is to protect the chinese translation page only. Please could you clarify?
**To replicate the issue:**
Theme 2024.
Plugins: WPML Multilingual CMS, WPML String Translation, WPML SEO, Yoast SEO.
Edit page: hidden link
Set page visibility to "password protected".
Add a simple password.
Update page.
View page.
Page should be password protected but is not.
If the password protection setting in WPML is set to sync with the default post, the translated post will remain unprotected unless the original post is password-protected.
If you want to password-protect the Translated post only, please try the following and hope it will help.
- Please go to 'WPML > Settings' and scroll down to the "Posts and pages synchronization"
- Uncheck the following option and save the changes
-- Synchronize passwords for password-protected posts
-- Synchronize private flag
Once done, apply the password for the translated page/post and check again. I hope it will help. If you need further assistance, feel free to let me know. I will be happy to help.
Very many thanks. There was no alert again so I didn't know you had replied.
That set of steps fixes the problem on the STG site, thank you.
Before I implement the fix on the PRD site, please can you clarify what impact (if any) this change of settings could have on the existing page/post configuration? Will there be any impact on any existing passwords or other settings?
I will need to ensure the users are fully across this. Please can you guide me to the relevant part in the documentation so I can make sure they get the required advice/training?
Hi Phil,
Glad to hear that the steps help to fix the issue.
I can understand your concerns. If you have pages or posts in the default language that are already password-protected, and you attempt to update their translations with the Password Synchronization option turned off, then the translations of these password-protected pages or posts will not automatically inherit the password protection. In such a case, you will need to manually assign a password to these translated pages or posts.
However, If you don't have a plan to update the existing password-protected pages or posts and their translations, then you're unlikely to encounter any problems. In such cases, everything should continue to function normally, with the existing pages/posts and their translations remaining unchanged. I hope you can understand.
While there isn't specific documentation on this feature, based on the information provided above, you can expect that the current setup of your pages/posts and their translations will be maintained.
Please feel free to let me know if you need further assistance or clarification regarding this matter. I will be happy to help.
[Please note that email notifications will be sent exclusively to the email address associated with your WPML account. Unfortunately, we are unable to send notifications to any other email addresses.]
