Problem: The client is experiencing an issue where a random *__trashed* string is being added to the end of page slugs, which seems to prevent translations from working. Additionally, there is a PHP Fatal error related to the Advanced Custom Fields (ACF) plugin. Solution: We asked the client to provide a detailed description of what the code is intended to do, and when and where it should run. This information is crucial for us to troubleshoot the issue further. We also informed the client that
is_admin()
is not a reliable way to check if a site visitor is on the front end or back end, especially with the Gutenberg editor, as detailed in the WordPress core ticket: https://core.trac.wordpress.org/ticket/47394.
If you're experiencing a similar issue, we recommend providing as much detail as possible about your code's intentions and context. However, please note that this solution might be outdated or not applicable to your case. If the problem persists, we highly 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 you still need assistance, please open a new support ticket with us.
For further assistance, please visit our support forum.
Problem: The client has completed translations for their homepage in Dutch, French, and German, but when viewing the homepage in any language other than English, no content appears, despite the translation edit screens showing 100% completion.
Solution: We checked the homepage and found that the fields were not copied or translated to the second language. We edited the "Components" field group and set the fields to be copied, which resulted in some content appearing on the Dutch homepage. We recommend the client to: 1. Edit fields that use Expert Mode and ensure the correct translation preference is set. 2. Update the default language page and its translations after changing the translation preferences.
We also provided guides to assist with this process:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, please open a new support ticket here.
