Problem: The client's multilingual e-commerce website was experiencing 404 errors specifically with English category URLs, while other languages and page types functioned normally. The issue was suspected to be related to WPML's management of rewrite rules and permalink settings. Solution: We identified that the slug for the product category in English was set to 'category', which is a reserved term in WordPress. To resolve this, we changed the slug in Settings -> Permalinks to 'categoria-prodoto' and updated the translations accordingly. We asked the client to confirm if this change resolved the issue.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues and verifying that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket.
Problem: You are trying to display the translated product category archive page in English, but you encounter a 404 error. The issue arises because the '/category/' part of the URL is missing, likely due to a setting in an SEO plugin that removes this base. Solution: 1. Update Plugins First, update your WooCommerce Multilingual & Multicurrency plugin to the latest version. • Visit My Account → Downloads to get the latest release. • Install and activate it. • If no updates are shown, click 'Check for updates' in Plugins → Add New → Commercial tab. 2. Confirm Settings After updating, verify whether the '/category/' base is intact. If the issue persists, it’s likely related to a third-party plugin or custom theme feature that strips out that part of the URL. 3. Test With Default Configuration • Temporarily disable other SEO or permalink–related plugins and switch to a default theme. • Recheck the URL to isolate where the change is coming from. 4. Backup First Always ensure you have a full database and file backup before making updates or major configuration changes.
The client has resolved with a Rank Math setting that removes the product category URL.
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 installed WPML and registered their site, but the WPML setup page was blank. Despite following troubleshooting steps like adjusting wp-config, deactivating caching plugins, and reinstalling everything, the issue persisted. No errors were visible in the Chrome developer console. Solution: The client switched from PHP 8.2 to 8.1, which resolved the problem and the WPML setup page reappeared. Additionally, we recommended checking the debug.log for potential issues and provided a link to a known issue that might be relevant: https://wpml.org/errata/custom-database-prefix-and-having-a-30-languages-can-cause-a-database-error-when-visiting-translation-dashboard/. We advised the client to back up their database before attempting any fixes suggested in the link.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket at our support forum.
Problem: The client restored a backup of a development site, and subsequently, the WPML's Advanced Translation Editor (ATE) began to malfunction. Initially, it worked briefly after clearing caches and re-adding the WPML site key, but then it failed with an 'AMS Server Communication - API error missing resource: No sitekey found for this website' error. Additionally, on some pages, the ATE does not load, and on others, it loads but does not complete the translation, showing a 'Service Unavailable' error. Solution: We recommend the following steps to resolve the issue: 1. Update the original page and save your changes. 2. Navigate to the WPML translation editor and check if the issue persists.
If these steps do not resolve the problem or if the solution seems outdated or irrelevant to your case, 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 issues continue, please open a new support ticket at WPML support forum for further assistance.
