Problem: The client is unable to find specific templates in the WPML String Translation or Admin Texts Translation areas. These templates are created using a custom shortcode, [Ruby_E_Template id="3476"], and are not appearing due to their unique IDs which differ per language.
Solution: To resolve this issue, we recommend the following steps: 1. Add the following code to your theme’s functions.php file:
3. Edit the default language page where the shortcode is used. Make a small change (like updating the title), then save. 4. Open the translation in WPML’s Translation Editor. You should now see the template ID string (e.g., 3476). Replace it with the translated template ID. 5. Complete the translation and check if it shows correctly on the front end.
For more details on making shortcodes translatable, please visit our documentation.
If the solution provided does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 issues persist, please open a new support ticket.
Problem: The client is unable to see credits in the WordPress dashboard after assigning them from their WPML account. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your WPML account and navigate to the Sites page. 2. Delete the existing site key. 3. Create a new subscription key for your site. 4. Go to your Site Dashboard, navigate to Plugins >> Add New >> Commercial tab. 5. Click on the “Unregister WPML from this site” button. 6. Register with the new site key and refresh the page.
This solution might be irrelevant if it’s outdated or not applicable 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 the issue persists, please open a new support ticket.
Problem: If you're experiencing issues with translating a shortcode in your Foxiz theme, where the Arabic shortcode is registered as an English string, we can help you resolve this. Solution: First, you need to mark the problematic string and change its source language to Arabic. After that, translate the string again. For detailed guidance, follow the steps in our documentation on how to change the source language of strings. Additionally, if you add the English shortcode inside the Theme Options, you should be able to translate it from English to Arabic.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket.
Problem: The client is experiencing a 404 page error when trying to navigate the Arabic version of their website or any article. Solution: We recommend checking if the issue might be related to a cached version of the page. Please try accessing the site from a different browser or device to see if the problem persists. If the issue continues, it could be beneficial to clear the browser cache or use a private/incognito browsing mode to ensure you are viewing the most recent version of the site.
If these steps do not resolve the issue, and you are still experiencing problems, 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 problem persists, please do not hesitate to open a new support ticket for further assistance. You can do so at WPML support forum.
Problem: The client is attempting to translate the footer from English to Arabic using two Penci blocks, one for each language. They have tried to add the block to string translation via the 'Admin Texts Translation' but it was not successful. Solution: 1. We resolved the issue by translating the footer slug instead of the footer ID. We recommend checking the footer translation by visiting this link and ensuring it works correctly in both languages. 2. We advise keeping the strings in the Soledad > Theme option > Quick text translation in English, and then translating them to Arabic via WPML -> String Translation.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket by visiting the WPML support forum.
Problem: The client is experiencing an issue where the 'language switcher' is automatically removed from the menu after adding it. Solution: We recommend the following steps to identify and resolve the issue: 1. Create a full backup of your website. 2. Disable all plugins except for WPML and its add-ons. 3. Check if the issue persists. 4. If the issue is resolved, reactivate your plugins one by one and check after each activation to identify the plugin causing the issue. 5. If the issue still occurs with only WPML plugins active, switch to a default WordPress theme like TwentySeventeen and test again. It is best to perform these steps in a staging environment if possible.
If these steps do not resolve your issue or if the solution does not seem relevant, please open a new support ticket with us.
Problem: The client was unable to find the section labeled as per the documentation after publishing a page, which is necessary for registering a new Elementor widget for translation. Solution: We recommend adding the following code to the WPML-> Settings-> Custom XML tab:
After adding the code, update the page in the default language first before updating the translation to see the strings in the string translation. If this solution doesn't look relevant, please open a new support ticket.
