Problem: The client needs to filter posts in the WPML Translation Dashboard to show only those that are not translated and not duplicated, excluding posts where the translation process has started. Additionally, the client wants to duplicate all published posts of a particular type that do not have any duplicated pages for other languages or where the translation is not started. Solution: To filter posts as required: 1. Go to WPML → Translation Dashboard. 2. In the filter options at the top, locate the Translation status dropdown. 3. Select Not translated from the options. This will display only the posts that are completely untranslated and not duplicated.
To duplicate posts: 1. In the Translation Dashboard, select the Type of post you want to duplicate (e.g., 'Post', 'Page', or a specific Custom Post Type). 2. For the Status filter, choose Published. 3. For the Translation status filter, select Not translated. 4. Select all the posts you wish to duplicate by checking the box next to the Title column header. 5. Scroll down and use the Translate selected content section to duplicate the selected posts.
For automation via a custom script, WPML's Coding API provides hooks such as
apply_filters('wpml_post_duplicates', $post_id)
and
do_action('wpml_make_post_duplicates', $post_id)
to detect and create duplicates programmatically. However, this requires custom development outside the standard support services. More details and examples are available at WPML Coding API documentation.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we recommend opening a new support ticket or contacting one of our recommended contractors at WPML contractors.
Problem: The client is experiencing slow loading times on their website when using WPML with 19 active languages, particularly noticeable during the initial load of pages. The client is concerned about the backend operations WPML performs and the impact on site performance. Solution: We identified that the slow loading times are partly due to the complex operations required by WPML to manage translations across multiple languages, but the main issue seemed to be that various Cache plugins were enabled at the same time. To improve performance, we recommend: 1. Disabling multiple cache plugins as they can conflict and degrade performance. Specifically, if using "Pressable Cache Management", ensure that "WP Rocket" is disabled. 2. Considering the use of an Object Cache Plugin to reduce the load on database operations, which can be particularly beneficial in setups with many active languages. 3. Checking the documentation on WPML's database table structure for further insights into how WPML manages data.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: The client would like to lower the amount of HTTP requests, due to each language flag being loaded as an individual SVG file. This results in multiple HTTP requests, which increase Time To First Byte (TTFB) and initial rendering time, particularly affecting visitors on slower networks.
Solution: We have forwarded a feature request to load SVGs programatically instead of using SVG files, which is currently under revision. You can find a custom solution approach for the issue inside the comments of this ticket.
If this solution does not apply to your case, or if it seems 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is managing the WP_ICL_TRANSLATE table in their WordPress site using the WPML plugin and is concerned about nearly 1 million records affecting site performance. Solution: If you're experiencing similar issues with large WPML tables, we recommend checking our documentation on reducing the size of WPML tables. Start by visiting Reducing the size of ICL_TRANSLATE_JOB, ICL_TRANSLATE, and other WPML tables. Additionally, you might find it helpful to review a related support ticket: My database is too large with ICL_TRANSLATE. Please note that while these resources can guide you in managing database size, upcoming updates in WPML 4.8 are expected to address these issues more comprehensively. However, manual data removal is not recommended as it may not be safe.
If this solution does not apply to your case, or if it seems 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 issues persist, please open a new support ticket.
Problem: The client is unable to update the WPML Multilingual CMS to version 4.7.4 due to the installer not being able to fetch the subscription. Solution: We recommend checking if the site URL and the registered site URL match. If they do not, follow these steps: 1. Log in to your WPML.org account and navigate to the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new plugin > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy and paste the new key into the input box and press the Register button. 7. Take a backup of your site and update the WPML plugins to the latest version. If the problem persists, please add a debug report in the Debug Information box. We have enabled the debug info box for your next reply: https://wpml.org/faq/provide-debug-information-faster-support/
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 needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing deprecated PHP errors with the 'Sticky Links' and 'CMS Navigation' plugins, which were identified as abandoned by the Wordfence plugin. The client is unsure whether to keep or remove these plugins. Solution: We have acknowledged the PHP notices and plan to address them in a future release. These notices should not affect your website's functionality. If you are not using the features provided by 'Sticky Links' and 'CMS Navigation', you can safely deactivate them. For more information on these plugins, you can visit the following documentation links:
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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 WPML Support Forum.
