Problem: The client was experiencing an issue with Gravity Forms Multilingual version 1.8.0 and above, where the 'gform_review_page' filter did not display the review page as expected, only showing the submit button directly.
Solution: We recommended trying the solution from this erratum.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing a PHP Fatal Error when trying to save a translated page using WPML with the Avada theme. The error message indicates an 'Uncaught InvalidArgumentException: No translation entry found'.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to
Avada > Library
in your dashboard. 2. Identify the Library Elements designated as Global. 3. Access the translations for these Global Library Elements and ensure they have been translated independently. For guidance on translating items independently, please refer to the following article: Translating Independently.
If the issue persists after following these steps, 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: You are using WP-CLI to list all media IDs in the trash across all languages but the command only returns media IDs for the main language. Solution: We have identified two potential workarounds to include media IDs from all languages: 1) Use the WP-CLI parameter
--suppress_filters=true
which allows the command to work across all languages. 2) Use the parameter
--url="https://yourwebsite.com/en"
to force WP-CLI to work in the language based on the URL.
Additionally, our 2nd Tier Support suggests modifying the code in
function with the following code to include a condition that checks for the 'lang' parameter in the query:
public function posts_where_filter( $where, $query ) {
if ( $query === null || $this->where_filter_active( $query ) === false ) {
return $where;
}
$requested_id = isset( $_REQUEST['attachment_id'] ) && $_REQUEST['attachment_id'] ? $_REQUEST['attachment_id'] : false;
$requested_id = isset( $_REQUEST['post_id'] ) && $_REQUEST['post_id'] ? $_REQUEST['post_id'] : $requested_id;
$requested_id = (int) $requested_id;
$default_language = $this->sitepress->get_default_language();
$post_language = $this->post_translations->get_element_lang_code( $requested_id );
if (isset($query->query["lang"])) {
$post_language = $query->query["lang"];
$requested_id = "1"; //hack needed because then $current_language will not get the $post_language, but will call for get_current_language
}
$current_language = $requested_id && $post_language ? $post_language : $this->sitepress->get_current_language();
$condition = $current_language === 'all' ? $this->all_langs_where() : $this->specific_lang_where( $current_language, $default_language );
$where .= $condition;
return $where;
}
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 these solutions do not resolve your issue, please open a new support ticket at WPML support forum.
Problem: When using WPALLIMPORT & WPML ALL IMPORT to import real estate properties in multilingual websites, if the option 'Search through the Media Library for existing images before importing new images' is checked, the plugin searches the entire media library across all languages instead of just the current language. This results in issues where images imported in a primary language are moved to a secondary language instead of being reimported with a new name and slug for SEO purposes.
Solution: This issue has been escalated to our developers for further investigation and resolution. Since this involves coordination with the All Import plugin and requires extensive testing across various import scenarios, we cannot provide a specific timeline for when a solution will be implemented. We will keep you updated with any new information as it becomes available.
If this solution becomes irrelevant due to updates or does not apply to your case, we recommend opening a new support ticket. We also 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.
