Problem: The client is experiencing an issue where the PHP
date()
function is not displaying dates in the correct language on their Spanish translation page. The dates are being output with the data-date attribute set to "1970-01-01" instead of the correct effective date. The client has custom fields for dates that are set to COPY, and while the effective date is displayed next to the post title, the data attribute in the HTML is incorrect.
Solution: We understand that the issue arises because the PHP
date()
function is using the server's locale to generate month names, which may not be translated by WPML's String Translation. This feature is intended for static strings and might not apply to dynamic content such as PHP-formatted dates. To translate month names and dates in WordPress using WPML, additional steps or configurations might be necessary, such as using WordPress-specific functions or hooks to localize the date strings. We found a solution on StackOverflow that could be helpful:
Please note that support for issues arising from custom coding is beyond our support scope. If you require assistance with custom coding, consider hiring a professional developer who specializes in customizing WPML and its extensions from https://wpml.org/contractors/.
If this solution is not relevant to your case, because it's outdated or not applicable, we recommend opening 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.
If you need further assistance, please do not hesitate to contact us in the WPML support forum.
Problem: The client has a Custom Taxonomy called 'Product Categories' and posts in a Custom Post Type called 'Manufacturing Price Updates' that are grouped by these categories. The client wants to display the posts in the Spanish version of the page with Spanish category names without converting the posts themselves to Spanish. Solution: We recommend translating the categories at WPML > Taxonomy Translation. Here's a guide to help you: Translating Post Categories and Custom Taxonomies. Additionally, the posts need to exist in the second language. You can either translate the posts or duplicate them. To duplicate posts in bulk, use the Dashboard at WPML > Translation Management. Here's a guide for that: How to Duplicate Pages and Posts in Bulk. Duplicates will display the same content in all languages and update automatically when the original content is edited.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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 at WPML support forum.
There was an error: { "keywords": "WPML, string translation, gettext, custom theme, hardcoded strings", "summary": "Problem:
The client needed to translate hardcoded English strings in a custom theme to Spanish, such as a search box placeholder and button text, and was unsure how to replace these values efficiently.
Solution:
1. We suggested enabling the \"Look for strings while pages are rendered\" option in WPML > String Translation, visiting the page with the string, and then searching for the string in WPML > String Translation.
3. We explained that for WPML to recognize strings, they need to be wrapped in a gettext call. We provided an example of how to wrap strings and a link to find the theme's text domain:
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us." }
Problem: The client reported that their Spanish homepage was redirecting to the default language homepage instead of staying on the Spanish version. Solution: We suggested that the client should try accessing the website from a different browser or device to rule out the possibility of a caching issue on their current browser. If you're experiencing this, we recommend you try the same steps to see if it resolves the issue.
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 you still need assistance, please don't hesitate to open a new support ticket with us.
