Problem: The client is trying to understand the translation credit usage report for their website and has concerns about missing permalinks in some rows of the report, interpreting the report, checking when credits were assigned, and discrepancies in credit totals. Solution: If you're experiencing missing permalinks in your credit report, this usually occurs with translations applied to non-page-specific elements like widgets or menus. We are working on improving the clarity of these reports. Each row in the credit report represents a translation task and shows how each credit was used, including the type of content translated and the date it was done. To check when credits were assigned to your site, you can view this in the 'Billing' section of your WPML account, which includes a history of all credit allocations and usages. Regarding the discrepancy in credit totals, it appears that although a large number of credits were initially assigned to the site, a significant portion was later moved back to the WPML.org account.
If this solution does not resolve your issue or 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 was unable to display translated regions, countries, and ports on their website using the Elementor Custom HTML widget. Solution: We recommended using the wpml_object_id filter hook to fetch translated post IDs in the current language. Detailed guidance on this hook is available at WPML documentation. For Ajax-loaded data, we advised passing the current language to the callback function. Instructions for handling Ajax requests can be found at WPML documentation. Additionally, we provided custom code examples to localize scripts and modify Ajax requests to ensure the correct language is used:
// Get the current WPML language
$current_language = apply_filters( 'wpml_current_language', null );
// Localize the script with the current language
wp_localize_script( 'common-js', 'wpmlData', array(
'currentLanguage' => $current_language,
));
lang: wpmlData.currentLanguage
These changes were implemented on the client's staging site. If further customization is needed, we recommended contacting a certified WPML contractor from this list.
Please note that the solution provided 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.
Problem: You are trying to translate the page 'Find your local offices' using WPML and encounter several issues: 'Unable to retrieve job details' error, 'File Size Limit exceeded' message, and Custom Posts for countries and cities/ports not displaying after translation. Solution: If you're experiencing these issues, we recommend removing the HTML widget that contains the SVG image from your Elementor page. This issue often occurs when the translation job exceeds 1MB of text due to the SVG image in the HTML widget. After removing the widget, save the page and attempt to re-translate it. This should resolve the error messages and display issues with the Custom Posts.
If this solution does not apply to your case, or if it seems outdated, please check the 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. If issues persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
