Problem: The client is trying to auto-translate over 600 hierarchical posts of a custom post type into a new language in batches, but the hierarchy is not properly retained after translation. Solution: We recommend sending the parent posts for translation first, followed by the child posts to maintain the hierarchy in the secondary language. Since there is no option to filter parent posts directly, the client will need to manually select them from the posts list in the backend. Alternatively, the client can duplicate the content first by selecting all the custom post types in WPML -> Translation Management, then duplicating them before sending for automatic translation. This approach should retain the hierarchy. Additionally, ensure the correct configuration for slugs in WPML -> Settings as per the documentation here: Translating Page Slugs.
If this solution does not resolve the issue or 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. Should the problem persist, please open a new support ticket on our forum for further assistance at WPML Support Forum.
Problem: The client's development server URL was visible in Google search results through WPML support questions, and they requested to make the tickets private and remove the URLs.
Solution: We removed any references to the development site URLs from the specified tickets.
Problema: Si estás experimentando dificultades para mostrar todos los idiomas en el selector de idiomas debido a que tienes alrededor de 30 idiomas y deseas personalizar el código corto "[wpml_language_selector_widget]" para que se parezca al diseño proporcionado, entendemos que la visualización de tantos idiomas puede no ser amigable para el usuario. Solución: Para convertir el selector de idiomas desplegable en el formato del diseño que adjuntaste, se requiere codificación personalizada. Esta tarea está fuera del alcance de nuestra Política de Soporte. Sin embargo, puedes encontrar orientación en tickets existentes donde otros clientes han buscado soluciones similares. Aquí tienes algunos ejemplos de búsquedas que podrían ser útiles:
Si no tienes experiencia previa con CSS, te recomendamos contratar a un contratista de WPML (http://wpml.org/contractors) o a un desarrollador front-end para lograr tu objetivo.
Si esta solución no parece relevante, por favor abre un nuevo ticket de soporte en nuestro foro de soporte.
Problem: The client is experiencing a 500 Internal Server Error when trying to access the WP Menu Sync page in the backend, which keeps loading without success. Solution: 1. We recommend enabling debug mode to identify the PHP errors causing the issue. To do this, edit the
wp-config.php
file and change the line
define('WP_DEBUG', false);
to
define('WP_DEBUG', true);
. 2. To log these errors to a file, add
define( 'WP_DEBUG_LOG', true );
to the
wp-config.php
file. Errors will be saved to a
debug.log
file in the
/wp-content/
directory. For more information on debugging WPML, visit WPML Debugging Documentation. 3. After enabling debug mode, if you still encounter the 500 error, follow these steps: - Make a backup of your website. - Delete the existing
debug.log
file. - Visit the WP Menu Sync page again. - Check the new
debug.log
for errors. If these steps do not resolve your issue or the solution does not seem relevant, please open a new support ticket with us for further assistance.
