Problem: You are trying to translate the contents in the Footnotes block on your pages using the Advanced Translation Editor (ATE), but the contents cannot be found for translation. Solution: 1. Navigate to your WordPress Dashboard > WPML > Settings > Custom Fields Translation. 2. Search for "footnote" and set it to "Translate". 3. Click the blue save button. 4. Visit the page containing the footnote and make a change in the original language to trigger the need for a translation update. 5. Open the Advanced Translation Editor. You will find a search bar at the top. Search for the content of the Footnote, and you should be able to find it. 6. Ensure you copy the entire code as is, and only change the text inside. For example, for a code like this:
For more detailed instructions on how to search content inside Advanced Translation Editor, visit this link.
If this solution does not resolve your issue or seems outdated, we 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: The client is using the Blocksy Theme on their WordPress site and has encountered an issue where the post-time format in English ('F j, Y') is not translating correctly to Chinese Traditional ('Y 年 n 月 j 日') for single posts. Despite ensuring all translations related to the time/date format have been applied, the translation only affects the update time, not the post-time.
Solution: We identified that the issue stemmed from the Customizer settings under Blog -> Single Post -> Post Title -> Post Meta. The solution involves ensuring that the theme is updated to the latest version as the Blocksy team has released an update addressing this compatibility issue. Additionally, it is crucial to enable aggressive options for string scan and auto-registration. The client should also check and adjust the date format settings from 'Default' to 'Custom' if necessary, to ensure the translations are registered and appear correctly. If the problem persists on a customized theme, we recommend reinstalling a fresh copy of the theme to eliminate any customization conflicts.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our support forum at https://wpml.org/forums/ to open a new support ticket. We also 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.
