Problem: The client is experiencing issues with translated 'account' pages showing as blank and Elementor templates and JetFormBuilder forms not displaying in French on their website. Solution: 1. Ensure that JetEngine Profile Builder pages are set as Translatable in WPML → Settings under the Post Types Translation section. 2. Verify that each account page has a French translation by checking under the French flag in Pages. Edit and update the French version if necessary. 3. If the navigation menu is missing or blank in French, go to Appearance → Menus, select the French menu, and ensure all relevant profile/account pages are added and published in French. 4. Use WPML → String Translation to translate any static or dynamic text, such as menu labels or JetEngine-generated elements. 5. Set Elementor templates and JetFormBuilder forms to Translatable under Post Types Translation in WPML → Settings. Check for French translations in Templates → Saved Templates and JetFormBuilder → Forms, and add or review the translation as needed. 6. Use the Advanced Translation Editor to verify and publish the translation. 7. Clear any site or browser cache if the preview still does not show the template in French. 8. If issues persist, consider switching to the parent theme temporarily to rule out issues with child theme customizations.
If after following these steps the issues persist, or if you encounter any error messages or blank content, it might be necessary to consult further with our support team. We 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 the problem continues, please open a new support ticket at WPML support forum for personalized assistance.
Problem: The client is experiencing an issue where ACF fields in the hero layout become readonly on a translated page, despite being set to 'Copy Once'.
Solution: 1. Verify that the ACF field and its sub-fields within the Flexible Content field are set to 'Copy Once' in WPML → Settings → Custom Fields Translation. 2. Ensure you are using the WordPress Editor to translate the page. If using the WPML Translation Editor, switch to the WordPress Editor by clicking the pencil icon next to the translation and selecting the WordPress Editor. 3. After switching, check if the hero layout ACF fields are editable on the translated page. If they remain readonly, review the field group settings in ACF → Field Groups to confirm correct translation preferences. 4. If issues persist after these steps, remove the translation and recreate it using the WordPress Editor to correctly apply the 'Copy Once' setting.
If the solution provided does not resolve your issue or seems outdated, we recommend opening a new support ticket for personalized assistance. Additionally, please check related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and confirm the version of the permanent fix. For further support, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: After updating WPML to the latest version, the client is unable to translate content and encounters a 500 error when attempting to use the string translation or open the WPML support tab. The issue began after URL slug manipulations were made, which might have caused disruptions in the translation engine. Solution: We recommend enabling the debug log to identify the specific cause of the 500 error. You can follow the instructions here: https://wpml.org/documentation/support/debugging-wpml/. After enabling the debug log, please share the log files with us for further analysis. If the problem persists, consider reverting to a previous stable version of WPML and its components, as this resolved the issue temporarily for the client.
Please note that this solution might be outdated or not applicable 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 the issue continues, please open a new support ticket at WPML support forum for personalized assistance.
Problem: El cliente está experimentando un error 500 de servidor debido a que el plugin WPML modifica el archivo htaccess, añadiendo el prefijo '/es' a las URLs, lo que provoca el error. Solution: 1. Para identificar la causa del problema, recomendamos seguir los pasos descritos en esta guía: https://wpml.org/es/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/ 2. Además, sugerimos actualizar los plugins de WPML desde Plugins -> Añadir nuevo -> Pestaña 'Comercial'.
Si esta solución no resuelve el problema o si parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client was experiencing an issue where the translation job was stuck 'In Progress' even after marking it as complete. The error log indicated that the uploaded xliff file was not properly formed, with missing or wrong data. Solution: We resolved the issue on our Advanced Translation Editor server side. We recommended the client to resend the page for translation. Additionally, we suggested clearing any server cache and resaving the translated page, as this seemed to fix the issue after translation, as demonstrated in a screen recording provided by our support team.
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 problems persist, please do not hesitate to open a new support ticket at our support forum.
Problem: You are working on a multilingual site (NL, FR, GB) and have a grouped product with many linked products. After removing linked products in the NL version, they still appear in the FR and GB versions. Solution: Ensure that your WPML and its add-ons are updated to the latest versions. After updating, remove the linked products from the original product and click the Update button. This should also remove the linked products from the translations. If the issue persists, please provide your site's Debug information for further assistance. You can find how to provide this information here.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also suggest 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.
