Problem: You are trying to understand why some pages do not have hreflang tags, despite your WPML settings being configured to create them for all pages. Solution: We have verified that the hreflang tags are indeed present when checking the page source directly. If you are using an SEO tool that reports missing hreflang tags, it might be incorrectly detecting their presence. We recommend manually checking the page source to confirm the hreflang tags are correctly implemented. If the issue persists according to the SEO tool, consider reporting this discrepancy to the tool's support team.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 needed, do not hesitate to open a new support ticket with us for further assistance.
Problem: The client is unable to add products with different variations to the cart on translated pages. Additionally, the client cannot edit the prices of products translated into another currency as these fields are locked. Solution: Firstly, we recommend clearing the caches on your site and browser as the issue might be related to cached data. For the issue of adding products to the cart, it appears that the problem might be related to translating the attribute slug. While the name of the attribute can be translated, the slug should remain in Latin letters. Please refer to this guide on the Woodmart support forum for more details: https://xtemos.com/forums/topic/can-not-select-attributes-inside-products/#post-297647
If these solutions do not resolve your issues or if the information provided becomes outdated, 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. Should you need further assistance, please feel free to open a new support ticket at our support forum.
Problem:
As soon as I scan the site on Google page speed insights I get the following error in Best Practice:
Properly defines charset Error!
A character encoding declaration is required. It can be done with a tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding. Solution:
