dainiusV-2

Problem:
You are trying to translate the slug from

to

, but this translation is not available in custom post type translations due to a WPML limitation.
Solution:
Currently, translating the slug in this scenario is not possible because WPML only allows the

to be set to a string. If the string value is set to something other than

, or if the custom post type name slug is not set, the archive slug will not be translatable. We recommend checking the documentation on translating slugs for custom post type archives for more information.

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, you can contact our support team at WPML support forum.

Problem:
The client was experiencing a critical error when trying to create a new product or page. The debug log indicated an issue with the WPML plugin, specifically an InvalidArgumentException related to the WPML_Translation_Element class.

Solution:
We recommended checking the database to ensure that auto increments are set properly, particularly for the following tables:

• wp_icl_translations
• wp_icl_translation_status
• wp_icl_strings

Additionally, we suggested checking other wp_icl tables. To access the database, we provided links to two WordPress plugins that could be used:

• Adminer
• WP phpMyAdmin

If you're experiencing this issue, we recommend you try the steps above. However, the solution might be irrelevant if it's outdated or not applicable to your case. In such instances, 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 the problem persists, please open a new support ticket with us.