Problem: The client is unable to translate the name of a custom post type created by MetaBox from Croatian into English and Slovenian. The untranslated post type name appears in the breadcrumbs. Solution: We recommend translating the custom post type slugs by following the steps outlined in the WPML documentation. You can find detailed instructions on how to do this by visiting the following links:
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: After installing WPML and adding two additional languages, the client's website became unsearchable on Google, except when selecting 'show English results'. The client was concerned about the site not appearing in Google search results and inquired about the necessary configurations in WPML to ensure proper indexing. Solution: We recommended the client to install a dedicated SEO plugin, such as Yoast SEO or Rankmath SEO, to manage multilingual SEO effectively. This setup allows the translation of meta information for each page, post, or archive, which is crucial for SEO in multiple languages. We provided documentation on how to integrate WPML with these SEO plugins for optimal results. You can read more about this integration here: WPML SEO documentation.
Please note that the solution provided might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket.
Problem: The client was experiencing an 'Invalid post type' error when WPML was active, which disappeared upon deactivating WPML. The issue was suspected to be related to a conflict with another plugin. Solution: We recommended the client to test their site in a minimum environment by deactivating all plugins except for WPML and its add-ons. This would help identify if the issue was indeed due to a plugin conflict. The client was advised to reactivate the plugins one by one to pinpoint which one caused the issue. It was important to make a full site backup before proceeding with these steps. If the site was live, we suggested performing these procedures in a staging environment or a snapshot on a local or another server.
If you're experiencing similar issues, we recommend trying these steps to see if it resolves the problem. However, this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum.
