Problem: The client reported an issue where the hreflang tags were incorrectly including '/en/' in the URL for the Spanish version, leading to 404 errors. Solution: We recommended deactivating all plugins except those necessary for WPML and the theme, and then reactivating them one by one to identify the cause. If the issue persisted, we provided a custom code solution involving updating the database and modifying the functions.php file in the child theme directory. The steps included: 1. Creating a full site backup. 2. Running the following SQL query:
INSERT INTO `wp_postmeta` (`post_id`, `meta_key`, `meta_value`) VALUES ('49068', '_yoast_wpseo_primary_property_city', '654');
3. Adding the provided PHP code to functions.php, which adjusts the URL structure based on the primary city term associated with each property.
If this solution does not resolve the issue or seems irrelevant due to updates or different configurations, 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 further assistance is needed, please open a new support ticket.
Problem: The client is experiencing an issue where post tags include an unwanted language suffix (e.g., -en) at the end. Solution: We have investigated the issue and consulted with our colleagues. Unfortunately, it is not possible to have identical slugs for taxonomy terms in different languages within WordPress. WordPress requires unique slugs for taxonomy terms, and if you attempt to create terms with the same slug, WordPress will append a numerical suffix to ensure uniqueness. Similarly, WPML follows this practice by adding the language code to the slug.
As of the current versions, you cannot modify these slugs to be the same from the WPML interface. If you change a category slug from the WPML interface, WordPress will add a number, and if you change it from the quick edit in WPML > Taxonomy translation, it will append the language tag.
This limitation is due to WordPress's functionality and is not something that WPML can fix. We apologize for the inconvenience and the lack of a solution in this case.
If this solution does not apply to your situation, or if it seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and ensuring that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket with us.
