Problem: The client was stuck in a loop where their support ticket was repeatedly closed by the system, causing difficulties in reporting issues. Despite adding debug information, they were asked for more necessary info. This was their third attempt to address the issue, and they did not receive email notifications about the ticket updates. Solution: We reopened the original ticket and assigned it to a specific support member to ensure continuity and direct communication. We advised the client to continue the discussion in the reopened ticket to resolve the issue effectively.
Please note that this solution might be outdated or not applicable to your case. If you're experiencing similar issues, 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 persists, please open a new support ticket.
Problem: The client was unable to apply dynamic variables like 'site title' and 'tagline' using the SEOPress SEO plugin across the whole site or specific posts/pages. They also encountered issues with translations not appearing correctly on their live site, despite settings adjustments and cache flushing. Solution: 1. The client set dynamic variables in the SEOPress settings under 'Titles and Metas - Home'. 2. They translated the necessary strings for the site title and tagline into the second language. 3. After discovering discrepancies in the database strings through PHPMyAdmin, the client corrected these by removing commas and ensuring consistency in naming. 4. This adjustment led to the correct display of the site title in the second language on the front end. If you're experiencing similar issues, we recommend checking your SEO plugin settings and ensuring all relevant strings are translated in WPML. Additionally, verify database entries for consistency if problems persist. If this solution does not resolve your issue or seems outdated, please visit our support forum to open a new 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.
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.
