Problem: You are testing whether the REST API is enabled or disabled and despite receiving a positive JSON response from https://angeldiver.pro/wp-json/, WPML still indicates that the REST API is disabled. Solution: We have identified that WPML can sometimes incorrectly report that the REST API is disabled, which is a known issue of false negatives. The crucial aspect to check is whether the API endpoints are accessible. Since you confirmed that the endpoints you tested are accessible, this indicates that the API is functioning correctly. You can safely disregard the WPML message stating that it's disabled.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should the problem persist, please open a new support ticket.
Problem: The client is unable to translate the content of the Elementor Price List widget on their pricelist page, resulting in only a partially translated page. They requested a custom XML to enable translation and asked for this XML to be included in future WPML releases.
Solution: We provided the client with the existing XML configuration for the Elementor Price List widget, which should generally cover the translation needs unless Elementor has changed its widget registration method. Here is the XML configuration:
We also asked the client to try replicating the issue on a new page with demo content to confirm if the problem persists. If the issue cannot be replicated, we may need access to their site for further investigation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing slower PageSpeed scores on the Polish version of your site compared to the English version, despite using the Litespeed Cache Plugin and both versions being identical except for the language. Solution: The discrepancy in speed between the English and Polish versions of your site is likely due to the additional processing required by WPML for translated pages. WPML needs to handle and filter translation layers, which involves accessing, processing, and displaying content based on the selected language. This necessary process introduces a slight overhead, which might affect the load times and PageSpeed scores of the translated pages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: If you're creating websites locally and then uploading them to a client's server, you might encounter an issue where dynamic links created with Elementor's 'Internal URL' feature do not redirect to the correct language translations when using WPML. This problem also affects dynamic categories in elements like Loop Carousel, where the content from selected categories remains untranslated.
Solution: To address this issue, we recommend the following steps: 1. Navigate to WPML -> Languages -> Make themes work multilingual. 2. Select the 'Adjust IDs for multilingual functionality' option. 3. Click the Save button. 4. Check if the problem is resolved. 5. If not, make a minor edit to the original post (even a dot or a space will suffice) and click the Update button to trigger a change in the translation. 6. Edit the translation of the post, ensuring the translation progress reaches 100%. 7. Verify if the issue is now resolved.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, we highly recommend checking the related 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 open a new support ticket.
