Home›Support›English Support›[Resolved] English Translation not working in "Global Sections" (Salient Theme
[Resolved] English Translation not working in "Global Sections" (Salient Theme
This thread is resolved. Here is a description of the problem and solution.
Problem: You are using the Salient theme and have encountered an issue where WPML translations are not appearing in the Global Sections, despite being correctly set in String Translations and after clearing the cache. Solution: First, ensure that the Global Sections are set to be translatable. You can do this by navigating to WPML-> Settings-> Post Type Translation section and setting the global section post type to be translatable. After this adjustment, you should see a + icon next to the global sections, allowing you to add translations for each language.
If this solution does not resolve your issue or 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. If the problem persists, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I’m using the Salient theme on my site hidden link, and I want to ensure that WPML applies translations to the Global Sections, such as a CTA block that appears on every page.
Symptoms:
WPML translations are not appearing in the Global Sections of the Salient theme, despite being correctly set in String Translations and cache being cleared.
Questions:
Can you please help with getting WPML translations to appear in Global Sections?
Thanks for contacting WPML forums support. I'll be glad to help you today.
First of all, sorry for the late reply; it was due to a higher workload.
1) I would need to look closely at your site, so I would need to request temporary access (WP-Admin and FTP) Preferably to a test site where the problem has been replicated.
Your answer will be private, meaning only you and I can access it.
❌ Please backup your database and website ❌
✙ I need your permission to deactivate and reactivate the plugins and themes and change site configurations. This is also why the backup is critical.
✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site.
2) Could you please share your Debug information with me?
You can read a detailed explanation about it here. (http://wpml.org/faq/provide-debug-information-faster-support)
The debug info will give me a lot of information about how your site is configured.
Thx, but how can I translate the Global Sections? There is no pencil icon to activate this - and I already put in the manual translation with strings. Thanks for clarifying
WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, WPML Multilingual CMS.
First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) and check for any visible issues.
Please contact your host for assistance with investigating this issue further.
If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
hidden link
To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.7.1
Active theme: Salient (version 17.0.5)
Current plugin: WPML Multilingual CMS (version 4.6.15)
PHP version 8.2.26
Error Details
=============
An error of type E_ERROR was caused in line 26 of the file /home/customer/www/staging.witpac.de/public_html/wp-content/plugins/sitepress-multilingual-cms/menu/post-menus/wpml-posts-listing-page.class.php. Error message: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /home/customer/www/staging.witpac.de/public_html/wp-content/plugins/sitepress-multilingual-cms/menu/post-menus/wpml-posts-listing-page.class.php:26
Stack trace:
#0 /home/customer/www/staging.witpac.de/public_html/wp-includes/class-wp-hook.php(324): WPML_Posts_Listing_Page->pre_populate_caches(Object(WP))
#1 /home/customer/www/staging.witpac.de/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#2 /home/customer/www/staging.witpac.de/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
#3 /home/customer/www/staging.witpac.de/public_html/wp-includes/class-wp.php(830): do_action_ref_array('wp', Array)
#4 /home/customer/www/staging.witpac.de/public_html/wp-includes/functions.php(1336): WP->main(Array)
#5 /home/customer/www/staging.witpac.de/public_html/wp-admin/includes/post.php(1306): wp(Array)
#6 /home/customer/www/staging.witpac.de/public_html/wp-admin/includes/class-wp-posts-list-table.php(165): wp_edit_posts_query()
#7 /home/customer/www/staging.witpac.de/public_html/wp-admin/edit.php(235): WP_Posts_List_Table->prepare_items()
#8 {main}
thrown>
It's great to hear that the issue is fixed. 🙂 Please don't hesitate to open a new ticket if you face any other issues. We are always happy to help you.
