Problem: You are using the Pen news theme and have translated footer text using 'string translation' for the keys
[theme_mods_pennews-child]penci_footer_copyright
and
[theme_mods_pennews-child]penci_footer_text
, but the translations are not appearing on the frontend. Solution: This issue is due to a theme compatibility problem. As a workaround, we added the following code to your child theme’s functions.php file to ensure the string is correctly translated:
We have also informed our team about this issue to communicate with the theme author for a permanent solution.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing warnings from the WPML REST API endpoint despite it returning valid data. The issue is suspected to be due to a low WP Memory Limit. Solution: 1. Increase the WordPress memory limit by editing the
wp-config.php
file. Add the following line above the 'That's all, stop editing! Happy publishing.' line:
define('WP_MEMORY_LIMIT', '256M');
If the memory limit is already defined, update it to at least 256M, preferably 512M for optimal performance with WPML and other plugins. 2. If the issue persists, check the
php.ini
file for the
memory_limit
setting, or contact the hosting provider to ensure it's set to at least 256M. 3. After making these changes, clear all caches and re-test the REST API endpoint. 4. If the problem continues, deactivate any security plugins like WordFence and consult with the hosting provider about any firewall or security settings that might be affecting the REST API.
If these steps do not resolve the issue or if the solution 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. For further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with author pages redirecting to the homepage instead of displaying the correct author page in various languages. This occurs when there are no posts available in the requested language.
Solution: This is the theme-specific issue that was not replicable on a new test site. We recommend using a custom code snippet to modify the behavior of the WPML language switcher on author pages. This code ensures that the language switcher links directly to the author pages, even if there are no posts in that language, thus preventing redirection to the homepage.
add_filter( 'icl_ls_languages', 'wpml_author_switcher_fix', 10, 1 );
function wpml_author_switcher_fix( $languages ) {
if ( is_author() ) {
$author = get_queried_object();
$author_slug = $author->user_nicename;
$default_lang = apply_filters( 'wpml_default_language', null );
foreach ( $languages as $lang_code => &$lang ) {
if ( $lang_code === $default_lang ) {
// No language prefix for default language
$lang['url'] = '/author/' . $author_slug . '/';
} else {
$lang['url'] = '/' . $lang_code . '/author/' . $author_slug . '/';
}
}
}
return $languages;
}
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is unable to find specific templates in the WPML String Translation or Admin Texts Translation areas. These templates are created using a custom shortcode, [Ruby_E_Template id="3476"], and are not appearing due to their unique IDs which differ per language.
Solution: To resolve this issue, we recommend the following steps: 1. Add the following code to your theme’s functions.php file:
3. Edit the default language page where the shortcode is used. Make a small change (like updating the title), then save. 4. Open the translation in WPML’s Translation Editor. You should now see the template ID string (e.g., 3476). Replace it with the translated template ID. 5. Complete the translation and check if it shows correctly on the front end.
For more details on making shortcodes translatable, please visit our documentation.
If the solution provided does not resolve your issue or seems irrelevant due to being 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 issues persist, please open a new support ticket.
Problem: The client is unable to see credits in the WordPress dashboard after assigning them from their WPML account. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your WPML account and navigate to the Sites page. 2. Delete the existing site key. 3. Create a new subscription key for your site. 4. Go to your Site Dashboard, navigate to Plugins >> Add New >> Commercial tab. 5. Click on the “Unregister WPML from this site” button. 6. Register with the new site key and refresh the page.
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 the issue persists, please open a new support ticket.
Problem: If you're experiencing issues with translating a shortcode in your Foxiz theme, where the Arabic shortcode is registered as an English string, we can help you resolve this. Solution: First, you need to mark the problematic string and change its source language to Arabic. After that, translate the string again. For detailed guidance, follow the steps in our documentation on how to change the source language of strings. Additionally, if you add the English shortcode inside the Theme Options, you should be able to translate it from English to Arabic.
Please note that 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 the issue persists, please open a new support ticket.
Problem: The client is experiencing a 404 page error when trying to navigate the Arabic version of their website or any article. Solution: We recommend checking if the issue might be related to a cached version of the page. Please try accessing the site from a different browser or device to see if the problem persists. If the issue continues, it could be beneficial to clear the browser cache or use a private/incognito browsing mode to ensure you are viewing the most recent version of the site.
If these steps do not resolve the issue, and you are still experiencing problems, 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 problem persists, please do not hesitate to open a new support ticket for further assistance. You can do so at WPML support forum.
