Problem: You are using WPML to translate WooCommerce admin texts, but the plugin generates .mo and .php files for product attribute translations, which you prefer to store only in the database. This issue is causing difficulties in changing translations of WooCommerce product attributes and caching problems with custom post types. Solution: WPML generates .mo files to utilize WordPress core's translation loading optimizations. Currently, WPML does not offer an option to disable the generation of .mo files. If you're experiencing issues with changing or retranslating product attributes, we recommend opening a new support ticket for further debugging. Additionally, the JSON files you mentioned are not related to WPML but are part of WordPress. For more details on these files, you can visit https://wordpress.stackexchange.com/questions/326332/unknown-language-json-files.
If this solution does not apply to your case, or if it seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML support forum.
Problem: The client updated the slugs for custom post types (CPTs) in different languages using WPML settings but encountered issues where the CPT pages sometimes display a 404 error or redirect to the homepage after the first page refresh. This issue persists even after clearing various caches. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Ensure that the slug translations are correctly set for each CPT in WPML -> Settings -> Post types translation. 2. Clear the WPML cache by navigating to WPML -> Support -> Troubleshooting -> Clear the cache in WPML. 3. Also, clear the full site cache on your hosting provider's dashboard. 4. If the issue persists, it might be related to how caching is handled on your server. Since the client's server is with Kinsta and caching cannot be disabled, consider testing changes in a staging environment where caching is not enabled.
If these steps do not resolve the issue or if it reoccurs, it might be due to a configuration that is specific to your environment or possibly an outdated solution. 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 continues, please open a new support ticket with us for further assistance at WPML support forum.
Problem: If you're experiencing an issue where ALT tag fields double in the translation editor when adding new images to a post, it might be due to adding an ALT value both in the media library and directly in the image block within the post editor. Solution: We have identified that this behavior is expected and not caused by WPML. When you add an ALT tag directly to an image block, this attribute is saved with the post content rather than in the media library. To avoid translating media library values along with each post, you can navigate to WPML > Settings > Media Translation and disable the last option in this section. This adjustment ensures that only the ALT text added to the block is used, preventing duplication in the translation editor.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with translating ACF repeater fields registered via PHP using the WPML editor, where the field doesn't translate correctly and only shows the number of rows instead of the array, this might be similar to your situation. Solution: We recommend trying the workaround mentioned in the WPML errata for issues related to the translation preference of PHP registered system fields. You can find more details and steps on how to apply this workaround at Advanced Custom Fields local fields translation preference issue for PHP registered system fields.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
