Problem: The client was unable to view the custom post type 'properties' in Greek on their website. They encountered an 'invalid post type' error when switching from English to Greek. Solution: We identified that the custom post types (CPTs) 'Properties' were created via Advanced Custom Fields (ACF). The issue was that the translation for the CPT was missing. We advised the client to go to ACF -> CPT -> properties and add the necessary translation. Once the translation was added, the CPT became available under the Greek language.
If this solution does not resolve your issue, or if it seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: The client needed a solution for inserting different affiliate codes for each language in their posts without losing changes after updates or re-translations. The affiliate codes were not appearing in the ATE translator as regular text links, and manual replacements were being overwritten with updates. Solution: We recommended using a custom PHP snippet or shortcode that dynamically inserts the affiliate code based on the current language. This approach ensures that the correct widget appears automatically for each language version and remains unchanged after updates or re-translations. Here is an example of how you might set this up:
function cityxee_viator_widget() {<br /> if (defined('ICL_LANGUAGE_CODE')) {<br /> switch (ICL_LANGUAGE_CODE) {<br /> case 'da':<br /> return 'kode til dansk viator';<br /> case 'en':<br /> return 'kode til engelsk viator';<br /> case 'fr':<br /> return 'kode til fransk viator';<br /> }<br /> }<br />}<br />add_shortcode('cityxee_viator', 'cityxee_viator_widget');
For posts requiring unique codes, we suggested using a custom field to store the affiliate ID, which can then be dynamically inserted into the affiliate widget code for each post:
<?php<br />$idkey = get_field('acf_partner_id'); // or whatever your field name is<br />?><br /><div data-vi-partner-id="<?php echo esc_attr($idkey); ?>" data-vi-widget-ref="W-6712b6be-d928-47db-b9a6-c96bce812859"></div><br /><script async src="https://www.viator.com/orion/partner/widget.js"></script>
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is using WPML to translate Gravity Forms on their website and has resolved the initial issue of enabling translation. However, they now need to send admin notifications to different email addresses based on the language of the form. Solution: We recommend using the gform_notification hook to customize the email notifications based on the form's language. Here is an example of how you can implement this:
Please note that 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client was unable to locate the translation options for specific Divi design pages, specifically the newsletter and thank you pages on their website. Solution: We identified the correct templates for the client's pages. For the newsletter page, the template can be accessed here: Newsletter Page Template. Similarly, for the thank you page, the template is available at: Thank You Page Template. To find these templates, we manually checked the list of templates under: Template List.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current situation, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client wants to change the source string of a translation while keeping the existing translations intact on their website. Solution: We explained that it is not possible to change the source string directly through WPML, as this is part of the theme or plugin itself. To modify the source string, customization of the source code is necessary, which is beyond the scope of our support. However, for managing translations of strings, we recommend checking the String Translation section of our documentation.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can always contact us through the WPML support forum.
Problem: The client is experiencing issues with custom widgets turning into 'Missing widget' entries after saving a page in SiteOrigin Page Builder, following updates to WPML v4.8.4 and String Translation v3.4.1. Additionally, there is a 404 error on the pagination of a custom post type archive, which temporarily resolves upon re-saving the ACF custom post type but reappears later.
Solution: We have determined that the issue with the widgets is not directly caused by WPML or String Translation, but rather by how the custom widgets are loaded and registered. Ensure that all custom widgets are registered using the standard
widgets_init
action and confirm that widget IDs and class names exactly match those saved in SiteOrigin. Also, check for PHP 8.3 compatibility as the plugin might use outdated code.
For the 'Missing widget' issue, disabling the 'Automatically detect best options for translating image texts' setting under WPML → Settings → Media Translation might resolve the issue. This is because WPML's media duplication process could be stripping necessary backslashes from the widget's data when saved in a secondary language. If problems persist, it's recommended to use
wp_slash()
when saving data to ensure backslashes are preserved.
If these solutions do not resolve the issues or if new problems arise, we recommend opening a new support ticket. Additionally, it's advisable to check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
