Problem: You are experiencing very slow performance on your website, both on the frontend and in the WP-admin area, after publishing it. The performance issue is particularly severe in the WP-admin area.
Solution: We recommend that you first address the optimization of WPML tables. This involves adding indexes and a primary key to improve database efficiency. For detailed guidance on how to do this, please refer to our documentation on WPML tables.
Once you have made these adjustments, if the problem persists, it might be due to other factors that are not covered by this solution or might be 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.
If these steps do not resolve the issue, please do not hesitate to open a new support ticket. You can reach us directly for further assistance at WPML support forum.
Problem: You are trying to translate anchor points in links using WPML, but find that while the main part of the URL translates correctly, the anchor part does not. For example, translating https://www.mysite.org/link/#anchor to https://www.mysite.org/es/link-es/#anchor-translated does not work for the anchor segment. Solution: We recommend adding a custom XML configuration to your WPML settings to enable translation of the anchor parts of links. Here is the XML configuration you should add:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
<wpml-config>
<elementor-widgets>
<widget name="text-editor">
<fields>
<field>editor</field>
</fields>
</widget>
<widget name="button">
<fields>
<field>text</field>
<field>link>url</field>
</fields>
</widget>
<widget name="menu-anchor">
<fields>
<field>anchor</field>
</fields>
</widget>
</elementor-widgets>
</wpml-config>
After adding this configuration, use the Advanced Translation Editor to search for "http" and translate the link as needed.
Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, 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 further assistance is needed, please open a new support ticket.
