Problem: The client was concerned about the unprofessional and system-generated appearance of the URL slug 'wp-global-styles-unisved-12' for a page, which did not match the expected descriptive and cleaner 'om-oss' similar to its Polish counterpart. Solution: We reviewed the WPML settings and confirmed that the 'Auto-generate from title (default)' option was selected, which should automatically generate the slug based on the page title. It appeared that the slug might have been manually altered on the Swedish page's editing screen. We corrected the slug to 'om-oss' to match the expected format. We asked the client to confirm if the issue was resolved.
If this solution does not apply to your case, or if it seems outdated, 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. Should the problem persist, please open a new support ticket.
Problem: If you're experiencing issues with styles not working when your site is translated into another language, such as Swedish, and encountering invisible text in the banner section, the problem might be related to the theme files. Specifically, conditions in the
header.php
file might be set to show content only on pages with a specific ID, which does not account for translated pages having different IDs. Solution: We recommend checking your theme's
header.php
file for conditions that limit content display based on page IDs. You should modify these conditions to accommodate the dynamic nature of page IDs in multilingual setups. Here's an example of how you can adjust the code:
This adjustment ensures that the correct page ID is used for the current language, allowing styles and text to appear as expected.
If this solution does not resolve your issue, or if it 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. Additionally, if you need further assistance, please do not hesitate to open a new support ticket with us at WPML support forum.
Problem: The client was unable to translate the content of ACF (Advanced Custom Fields) fields and the page content itself in a custom WordPress site using WPML. The translation interface did not allow changes to the content for different languages, although the ACF field labels were detected correctly. Solution: 1. We recommended ensuring that ACFs are set as translatable by comparing the site's configuration with the guide on translating sites built with ACF. 2. It was important to set the ACF Groups post type as 'Not Translate' in WPML -> Settings -> Post Type Translation. 3. We advised increasing the WordPress memory limit to at least 128MB, suggesting adding the following code in wp-config.php:
4. Installation of the String Translation plugin was recommended to manage string translations effectively. 5. We updated the configuration to set ACF fields as translatable, which resolved the issue of fields not appearing in the translation interface.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 further assistance is needed, please open a new support ticket.
