Problem: You are trying to change your wp-admin login page for security reasons, but the page automatically includes a language subfolder, resulting in a URL like domain.com/en/alternatelogin. You want to disable this language subfolder for the login page. Solution: 1. Navigate to WPML > Settings > Login and registration pages. 2. Uncheck the option "Allow translating the login and registration pages" to prevent WPML from translating the login page and adding a language subfolder. 3. If your website is using a directory for the default language and you want to remove this for all default language pages, you can disable this setting. This change will make your default language pages appear as domain.com instead of domain.com/en/. 4. Alternatively, you can set up different domains for each language. This setup can help if you are using multiple domains. For more details on setting up different domains per language, visit how to use WPML with different domains per language.
If this solution does not apply to your situation, or if it 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. If issues persist, please open a new support ticket.
Problem: The client is experiencing issues where newly imported translations from XLIFF files are not appearing or updating correctly on their website. Additionally, when attempting to edit these translations in the WPML Translation Editor, the changes do not reflect, and they have to redo the translations manually. Solution: We explained that once translations are imported via XLIFF files directly into the database, they cannot be edited using the WPML Translation Editor. This is because the WPML editor operates with a separate memory system that does not synchronize with direct database edits. To resolve this, the client should choose a consistent method of translation: either continue using XLIFF for all updates and re-import after making changes or switch to using the WPML Translation Editor for all translations to ensure consistency and avoid loss of data.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where the error message 'Jobs could not be loaded' appears on the Jobs and Translations pages of their production site. Despite deactivating non-essential plugins, the error persists. The issue does not occur in the staging environment, suggesting an environment-specific problem, potentially related to CORS policy settings. Solution: The issue stems from a CORS policy error, where the client's production server is blocking requests from their domain due to missing 'Access-Control-Allow-Origin' headers. To resolve this, the client should contact their hosting provider or the team managing the kariera.pragmaticcoders.com server to enable CORS settings that allow requests from http://www.pragmaticcoders.com. This adjustment should resolve the error.
If this solution does not apply to your situation, or if it seems outdated, we highly recommend checking for related 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 retrieve the Spanish version of ACF image URLs in the backend for their WordPress site, which affects the display of the 'header top bar' for different language versions. Solution: To resolve this issue, we recommend the following steps: 1. Navigate to WPML-> Settings-> Post Type Translation. 2. Set the following post types to be not translatable: - Field Groups (acf-field-group) - Taxonomies (acf-taxonomy) - Post Types (acf-post-type) - Options Pages (acf-ui-options-page) 3. Click 'Save'. 4. Go to 'General Settings'. 5. Switch the language using the top admin bar. 6. Add the translated settings. For further guidance on translating Option pages, please refer to this guide.
If this solution does not apply to your case, or if it 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 you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are using the Smart Offers plugin to display an offer when a product is added to the cart. This works fine in English, but the offer does not trigger correctly for translations. Specifically, in the German version, even after setting the offer to trigger when the German product is added, it incorrectly shows the English product as the trigger after saving. Solution: We have identified that on your staging site, you are using the WPML Translation Editor, whereas on your sandbox site, you have translated the content manually. To resolve this issue, please follow these steps: 1. Go to the translation of the Smart Offers in the German language on your website. 2. Delete this translation and also remove it from the trash. 3. Re-translate the offer manually, similar to how you did on the sandbox site. For guidance on how to translate manually, you can refer to our documentation here: Using Different Translation Editors for Different Pages.
If this solution does not resolve your 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. If the problem persists, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: You are experiencing issues with the Advanced Translation Editor in WPML, where it flags text that is not present in the translation due to differences in bold formatting between the source and translated text. Solution: Currently, it is not possible to disable the check for bold formatting differences in the Advanced Translation Editor. All content, including HTML markers, must be the same in both the original and translated pages. If you require different content or formatting, you can opt for a manual translation method by following this guide: Using Different Translation Editors for Different Pages. Alternatively, you can customize the appearance of the second language page using custom CSS, but the text and content must still be fully translated and consistent across both languages.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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: WPML Support Forum.
Problem: The client is experiencing a PHP Fatal error during the import process using the WPML plugin, specifically when using the WPML All Import addon. The error message indicates a type error with array_filter() expecting an array but receiving a boolean.
Solution: 1. We recommend deactivating all plugins except for WPML and any essential plugins required for the import. 2. Navigate to WPML → Settings → Troubleshooting and perform the following actions: - Clear the cache in WPML - Set language information - Fix the collation of element types - Remove ghost entries from the translation tables - Assign translation statuses to duplicated content 3. Replace the outdated 'WPML All Import' addon with the new 'WPML Export & Import' addon, which is compatible with WP All Export, WP All Import, and native WordPress and WooCommerce export and import methods. You can download it from here. 4. Ensure that the import process in WP All Import is fully completed before running the WPML importer in WPML > Export & Import.
If you're still experiencing issues after following these steps, or if the solution provided here becomes 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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
