Problem: The client created a new page and is trying to translate it using WPML, but one block is missing during the translation process. Solution: If you're experiencing a missing block when trying to translate a page, we recommend you try the following steps: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a space or a '+' sign in your page/post title. 3. Update the page by pressing the “Update” button. 4. Remove the small change you made in step 2. 5. Update the page again. 6. Open the translated page in the WPML Translation Editor and check if the missing content appears for translation. If the issue persists, we suggest providing temporary access (WP-Admin and FTP Login info) to your site, preferably a staging site, so we can further investigate and debug the issue. Please ensure to back up your database and website before providing access. We may need to deactivate and reactivate plugins and the theme, and change configurations on your site, which is why a backup is crucial.
This solution might be irrelevant if it's outdated or not applicable 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are seeing a message stating "This copy of the site has the same content as the original site on https://city-pass.it, but it doesn’t have credits for automatic translation." This occurs because you cloned a site and WPML recognizes the same content and translation memory from the original site. Solution: If you intend for both sites to share the same translation memory, you can confirm this by selecting "Yes - This is only a copy, original site is still running." For more details, visit this documentation. If you prefer to keep the sites completely separate, please take a backup and follow the steps in this guide to reset the connection.
Please note that the solution might be irrelevant if it’s outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: After cloning a site with CPanel and configuring new settings, the client attempted to reinstall WPML plugins using the OTGS installer. Despite selecting 'activate after download', the plugins did not appear in the installed plugins list. Solution: We recommend ensuring that the site URL matches the registered site URL in your WPML.org account. Here are the steps to resolve the issue: 1. Log in to your WPML.org account and go to the Sites page. 2. Delete the existing site key. 3. Log in to your site, navigate to Dashboard >> Plugins >> Add new plugin > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy and paste the new key into the input box and press the Register button. 7. Take a backup of your site and try to install the WPML plugins again. If the problem persists, please provide a debug report in the Debug Information box. For instructions on how to add a debug report, visit WPML Debug Information Guide.
If this solution does not apply because it is outdated or not relevant to your case, we highly recommend checking related known issues at WPML 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.
Problem: The client was unable to display the 'dashicons-admin-home' icon in the primary navigation of their WordPress site across subdirectories. Solution: We identified that the issue was due to dashicons not being loaded on the front-end because the site used different logins, and wp-admin wasn't loaded by default. To resolve this, we recommended loading dashicons on the front-end. You can add the following line to your theme's functions.php file:
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client needed to adapt affiliate widget code for language support on their site, specifically to translate the 'data-gyg-locale-code' attribute in the widget code. Solution: We recommended using a custom XML configuration in WPML to make the widget code translatable. Here are the steps we suggested: 1. Navigate to WPML >> Settings >> Custom XML >> Configuration section: https://purple-drumbox.sandbox.otgs.work/wp-admin/admin.php?page=tm%2Fmenu%2Fsettings&sm=custom-xml-config 2. Add the following XML code:
3. Save the changes. 4. Make a small edit to the default language page to trigger a reload of the translation. 5. Open the translated page in WPML Advanced Translation Editor, search for the English locale code en-EN, and replace it with the translated locale code.
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 https://wpml.org/forums/forum/english-support/.
Problem: The client is considering configuring WPML with different domains and subdomains for their WordPress site and is unsure if this will result in one WordPress site or multiple sites per domain/subdomain. They are also concerned about how this configuration affects the use of themes and pro plugins that are licensed for a certain number of installations. Solution: We recommend setting up WPML on a single WordPress installation. When using the domain-per-language feature, install WordPress on the main domain (the primary language) and set up WPML there. For additional languages, configure each other domain or subdomain accordingly. You can find detailed instructions on how to do this in our documentation here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/
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 https://wpml.org/forums/forum/english-support/.
