Problem: The client was having trouble displaying certain sections of their site after translation, which is built with WP Bakery and uses the GARDIS theme.
Solution: 1. We updated the translated testimonial posts on the home page, which resolved the display issue. We asked the client to check if the translated home page works correctly.
2. For the About page, we registered two unregistered modules by adding custom XML code in WPML-> Settings-> Custom XML tab:
After adding the code, we updated the page in the default language and its translation. We asked the client to verify if it's translated correctly.
3. We provided additional tips for the translation process: - The contact form needs to be translated, and we provided a guide for assistance: Using Contact Form 7 with WPML. - In Services posts, the icon is not automatically copied to the translated post, so it needs to be selected manually. - Theme options inside the page's edit screen are not copied to the translated pages, so they also need to be selected manually.
Problema: Si está intentando traducir una sección de SERVICIOS en su sitio web construido con WP Bakery y el tema GARDIS, y tiene problemas para habilitar la traducción de dicha sección. Solución: Para resolver este problema, siga estos pasos: 1. Vaya a WPML -> Settings -> Post type translation -> Services (cpt_services). 2. Configure a 'Translatable - only show translated items'. 3. Guarde los cambios. Después de realizar estos pasos, podrá regresar a la sección de servicios y traducirlos como lo haría con las páginas y entradas normales. Le recomendamos que revise la guía sobre la traducción de tipos de contenido personalizado para obtener más información: https://wpml.org/documentation/getting-started-guide/translating-custom-posts/
Problema: Si estás intentando trabajar en una página web y te encuentras con problemas relacionados con la traducción de widgets personalizados de Elementor o con un límite de memoria de PHP insuficiente, como se describió en el caso del cliente. Solución: Para resolver el problema de los widgets personalizados de Elementor, necesitas registrar el widget para la traducción siguiendo las instrucciones proporcionadas en nuestra documentación: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/.
En cuanto al límite de memoria de PHP, se recomienda que sea de al menos 256MB. Si tu sitio tiene un límite menor, como el límite de 128MB que se requiere como mínimo, debes contactar a tu proveedor de alojamiento web y solicitar un aumento en el valor de PHP. Puedes encontrar más información sobre los requisitos mínimos de WPML aquí: https://wpml.org/home/minimum-requirements/.
Problem: The client is unable to see the texts for translation on the homepage after installing WPML and registering the site. Solution: We recommend following the steps below to resolve the issue: 1. Go to WPML > Settings > Custom XML Configuration. 2. Add the following custom XML code to register the Elementor widgets for translation:
<wpml-config>
<elementor-widgets>
... (rest of the XML code) ...
</elementor-widgets>
</wpml-config>
After adding this code, the widgets from the theme should now be available for translation. We also suggest contacting the theme's developers to integrate this XML code into the theme for future ease of use. For more detailed instructions, please refer to our documentation on registering custom Elementor widgets for translation.
Problem: The client was unable to activate the OTGS Installer plugin after downloading and attempting to install it multiple times. An error message indicated a failure to copy a specific file. The client had checked the CPanel configuration, which was correct, and the WPML plugin was not listed in the WordPress dashboard.
Solution: We requested temporary access to the client's site to investigate the issue. After gaining access, we found that the WPML plugin was ready for activation in the WordPress dashboard. We provided a direct link for the client to activate the plugin. Additionally, we explained the manual installation process, which involved using a file manager plugin to upload the WPML plugin zip file to the 'wp-content/plugins' directory, extracting it, and then removing the zip file and the file manager plugin itself. This process resulted in the creation of a new directory called 'sitepress-multilingual-cms' containing the WPML plugin files.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us.
Problem: The client is unable to install and activate the WPML plugin due to a directory creation error and a file copy issue.
Solution: We recommend manually installing the WPML plugin by following these steps: 1. Download the WPML plugin from our downloads page. 2. Navigate to your website's backend > Plugins > Add New > Upload Plugin, then upload the zip file, install, and activate WPML.
If the above does not work, use cPanel's "File Manager" to: 1. Navigate to the /public_html directory > wp-content > plugins. 2. Upload the zip file downloaded from our site. 3. Extract the zip file in the /plugins directory, which will create a new folder called "sitepress-multilingual-cms". 4. Go to your site's backend > Plugins, where you should see the WPML plugin and be able to activate it. 5. After confirming the plugin is present, delete the .zip file from your hosting via cPanel.
If these steps do not resolve the issue, please open a new support ticket so we can investigate further.
