Problem: The client is trying to add a translation to a blog post using the WordPress Editor, but the translated blog post is not automatically connected to the original English post and exists as a separate entity unless manually connected.
Solution:
The problem turned out to be because of NGINX security headers that they added recently to improve the website security. Specifically these two:
If the problem continues, please visit our support forum and open a new ticket for further assistance. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
If this solution does not apply to your case because it might be outdated or not relevant, please do not hesitate to contact us by opening a new support ticket at our support forum.
Problem: The client reported a 404 error on a translated CPT archive page that appeared after updating WPML to the latest version.
Solution: We identified that the issues might be related to conflicts between custom taxonomies and post types managed by JetEngine and WPML settings. For the missing translations and status issues, we recommended: 1. Checking and correcting the WPML settings for custom taxonomies and ensuring they are not overwritten unintentionally. 2. Updating JetEngine and other plugins to their latest versions to resolve any compatibility issues. 3. If the problem persists, recreating the affected taxonomies might be necessary, although this could lead to the loss of assigned taxonomies due to how JetEngine handles deletions.
For the blog articles issue, ensuring that all plugins are up-to-date and checking the child theme settings were recommended as these could be causing the observed problems.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
Problem: The client wanted to know if the "Automatic Redirect Based on Browser Language" feature in WPML would slow down page loading for all pages or just the root page. They were also curious about how the redirection would work if they accessed a subpage directly with a different browser language set. Solution: We explained that WPML checks the browser language using JavaScript, which occurs only on the first page load. After the language is detected, it won't check again until the cookie expires, which is set in WPML > Languages > Language browser redirection. For the specific scenario, if the client opens a subpage (like gogoespana.com/en/blog) for the first time with the browser language set to Korean, they would be redirected to the equivalent page in Korean (gogoespana.com/kr/blog).
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, we encourage you to open a new support ticket. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
If you need further assistance, please contact our support team at the WPML support forum.
Problem: The client reported an issue with pages translated using WPML not being indexed by Google, as indicated by a report from Google Search Console titled "Alternate page with the proper canonical tag".
Solution: We reviewed the pages marked in the client's screenshot and confirmed that all have self-referencing canonical tags, which is the expected behavior and should not cause indexing issues. Additionally, we verified that these pages are indeed indexed in Google. We suggested that the client contact Google Search Console support for further clarification on the report, as the issue might not be related to WPML or the site's SEO setup.
If you're experiencing similar issues, we recommend checking that your translated pages have the correct self-referencing canonical tags and are indexed by searching for their URLs in Google Search. If the problem persists, consider reaching out to Google Search Console support for assistance.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you continue to face issues, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket with us.
Issue: The client wanted to confirm information about browser language-based redirection in WPML and how it affects page load time and interaction with Google indexing.
Solution: 1. Browser language-based redirection affects only the first time a user visits the site, not each time they navigate to a new page. Does not double the charging time; Generally, it is just a page refresh that takes no more than 1-2 seconds.
2. Redirecting can affect how Google bots crawl and index pages, as they could be redirected to a different language than the one they were initially trying to crawl. This is still an issue and applies to any type of redirect, including those configured on the Nginx server. It is recommended to use a 301 redirect in Nginx to inform Google bots about the permanent nature of the change.
If the solution provided is not relevant to your case, because it could be outdated or not applicable to your specific situation, we suggest you open a new support ticket. We also strongly recommend reviewing the known issues, checking the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, feel free to contact us at the WPML support forum .
Problem: You are trying to translate the default posts slug added in WP permalink settings. While the translation appears correctly on the archive page, it does not reflect on single post pages. Solution: Unfortunately, it is not possible to translate custom strings added to the custom structure permalink directly through WPML. However, you can create a custom parent category with the same slug and assign it to the posts. This method will make the slug appear similar when using the category/post-name permalink structure. If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at https://wpml.org/forums/.
