Problem: If you're experiencing an issue where the site logo of the English translation displays a random image instead of the uploaded site logo in the Storefront settings, even though you've added
admin_texts_site_logo
to the String Translation, the problem might be due to a must-use plugin affecting image translations. Solution: We recommend checking if there is a must-use plugin active on your main website that could be affecting your subsites. In this case, the plugin identified was 'network-media-library'. Disabling this plugin via File Manager, re-uploading the logo image, and setting it via the theme customizer resolved the issue. If you're unsure how to proceed or need further assistance, we suggest visiting our support forum at https://wpml.org/forums/.
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 persists, please open a new support ticket.
Problem: You are trying to translate the 'Agenda' custom post type using the WPML Translation Editor, but the translation keeps switching back to the WordPress editor instead of opening in the WPML Translation Editor. Solution: We have set the WPML Translation Editor as the default editor for all 'Agenda' custom post types. Please check if the issue persists by attempting to translate an 'Agenda' post again. If the translation still opens in the WordPress editor, it might be due to a temporary setting or cache issue.
If this solution does not resolve your issue or seems outdated, we recommend checking the related 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.
Problem: You are unable to see ACF fields in the WPML translation editor when trying to translate them. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Go to your database manager, such as PhpMyAdmin. 2. Navigate to the "wp_options" table. 3. Search for the "icl_sitepress_settings" key. 4. Delete this key. 5. Access your site's dashboard. 6. Configure WPML settings. 7. Edit all the custom field groups. 8. Save all the field groups. 9. Edit the product in the default language. 10. Make a minor edit and update it. 11. Update the translation using the translation editor.
Please ensure to backup your database before proceeding with these steps.
If this solution 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 the problem persists, please open a new support ticket.
Problem: If you're experiencing issues with ACF fields not being visible in the WPML translation editor, even though you have set the translation preferences correctly, this might be due to a configuration issue. Solution: We recommend checking the translation preferences for these text fields. They might be set to "Copy Once" even if "Same fields across languages" is enabled. To fix this, switch the group to "Different fields across languages" and then revert it back to "Same fields across languages." This action should apply the necessary changes.
Additionally, if this process triggers background tasks that seem to be stuck, you might need to delete the entries in the
If this solution 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 further assistance is needed, please open a new support ticket at our support forum.
