The client is trying to remove WPML and all related content from their site completely. Despite following the provided instructions and dropping database rows, all WPML translated taxonomies, pages, posts, and Beaver Themer layouts remain.
Solution:
We recommend creating a staging or development site, a clone of the live site, for further debugging without affecting the live environment. Please follow these steps after a full site backup:
1) Go to WPML >> Languages >> Site Languages (of subsite) 2) Click on the Add/Remove Languages button 3) Uncheck the Spanish language and save 4) Refresh the page 5) Delete all the contents of the Spanish language: https://cdn.wpml.org/wp-content/uploads/2022/03/Deleting-all-translations.png 6) Go to the Network Dashboard 7) Open the WPML menu 8) Perform the Reset WPML action for the subsite 9) Deactivate WPML for the subsite
If you encounter issues during Step 5, such as error messages, try refreshing and retrying. It should eventually remove everything. For more details, refer to the following documentation:
If the solution provided 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with images in an ACF field only displaying on English posts and not on Spanish posts, despite using the ACF WPML add-on. Solution: We found that the issue was due to the translation settings for the ACF Field Group. It is not recommended to set the translation preference for the 'acf-field-group' post type to Translatable as it creates separate field groups for each language, requiring manual configuration for each. To fix this, we set the ACF Field Group's translation preference to "Not Translatable" and deactivated the translated field group. We then set the translation preference for the `topic_featured_image` and `_topic_featured_image` meta fields to "Copy." After making a minor change and saving it via "Posts > Tag > Quick Edit," the featured image was successfully copied to the translated tag and displayed correctly on the frontend. For more details, please check this Errata.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client accidentally deleted a production site key in WPML and encountered an error when trying to add a new site key, with the system reporting that the key doesn't match. Solution: If you're experiencing this issue, we recommend that you unregister your website and then register it again with the new site key. This should resolve the problem. You can find a step-by-step guide on how to unregister your website here.
Please note that this solution might be irrelevant if it's 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.
