Problem: The client reported an issue with the English version of the cart page showing errors and partial information, while the Spanish version worked correctly. The problem persisted even without WP Rocket's cache, indicating it wasn't a caching issue. Solution: We suggested replacing the WooCommerce block with a shortcode to resolve the JavaScript translation file issue. The steps included: 1. Editing the Cart page in WordPress admin. 2. Removing the WooCommerce block. 3. Adding a new 'Shortcode' block. 4. Inserting the shortcode
[woocommerce_cart]
into the new block. 5. Updating the page. When the client faced difficulties with removing the block, we provided alternative steps to add the shortcode without removing the existing block. Eventually, the issue required escalation due to the inability to remove or replace the block, and the client requested to speak with a human agent.
If this solution does not resolve your issue or seems outdated, we 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 open a new support ticket.
Problem: The client was experiencing 404 errors on some translated pages, which seemed to be related to permalink settings or conflicts with other plugins.
Solution: 1. Flush Permalinks: We recommended the client to go to Settings → Permalinks in their WordPress dashboard and click the Save Changes button without making any changes to refresh the URL rewrite rules. 2. Update Affected Pages: We advised the client to make a minor edit and update the original page and its translations to help WPML regenerate translation links. 3. Check for Conflicting Plugins: We suggested reviewing and temporarily deactivating any plugins that might interfere with WPML, such as redirect or URL management plugins. After these steps, we recommended clearing any site and browser caches and retesting the translated pages in an incognito window.
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. If the problem persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing 404 errors on your translated pages while using the Salient Child Theme. Solution: To resolve these 404 errors, we recommend the following steps: 1. Flush Permalinks: This often resolves 404 issues by regenerating WordPress's rewrite rules. * Go to Settings → Permalinks in your WordPress dashboard. * Without making any changes, simply click the Save Changes button.
2. Refresh or Update Translations: Sometimes, re-saving content helps WPML re-establish the correct links and associations for translated pages. * Go to Pages in your WordPress dashboard. * Edit the original (default language) page that is showing a 404 error on its translation. * Make a minor change (e.g., add a space, then remove it) and click Update. * Then, edit the translation for that page (look for the circular arrow icon if prompted to update). * Ensure the translation is marked as 100% complete and save it.
3. Check for Conflicting Plugins: Certain plugins can interfere with WPML's URL handling. * Disable XML-RPC-API Plugin: If you have a plugin named
If these steps do not resolve your 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that some translated pages are not displaying updated content and are causing CSS issues. Solution: 1. We asked the client to confirm which pages and languages are affected and to provide recent examples or URLs. 2. We inquired about any recent changes to the original content, the steps followed in the translation workflow, and whether the site cache or CDN has been cleared. 3. We recommended resaving or retranslating the affected pages and checking for CSS differences between the original and translated pages. 4. We emphasized avoiding generic troubleshooting and focusing on a personalized, step-by-step analysis with clear requests for additional details.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related 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.
Problem: The client is experiencing 404 errors on some translated pages, even after resetting permalinks. Solution: If you're encountering 404 errors on your translated pages, we recommend the following steps: 1. Ensure that the WooCommerce Multilingual & Multicurrency (WCML) plugin is active. 2. Check your WPML and WooCommerce settings for permalink and slug translations. 3. Review and correct the translated product slugs in WCML. 4. Reset your permalinks multiple times if necessary.
If these steps do not resolve the issue, it might be due to a configuration that is either 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where the CSS breaks on translated pages of your website, it might be related to how global sections are rendered within your theme. Specifically, the Code Snippets plugin may not be loading your theme's CSS correctly for the second language. Solution: We recommend using a Child Theme instead of the Code Snippets plugin. You can add the following snippet to the functions.php file of your Child Theme to address some of the CSS issues:
add_action('init', function() {
// Hook location to output the global section
$location_hook = 'nectar_hook_global_section_footer';
add_action($location_hook, function() use ($location_hook) {
// Detect current language
$current_lang = apply_filters( 'wpml_current_language', null );
// Default section ID (Spanish)
$global_section_id = '24759-2';
// Use translated section ID for English
if ( $current_lang === 'en' ) {
$global_section_id = '26378';
}
// Default category ID (Spanish)
$category_id = 47;
// Use translated category ID for English
if ( $current_lang === 'en' ) {
$category_id = 156;
}
// Output the section only if we're on the correct category archive
if ( is_product_category( $category_id ) ) {
Nectar_Global_Sections_Render::get_instance()->output_global_section($global_section_id, $location_hook);
}
});
});
However, if disabling the Code Snippets plugin resolves all issues, we suggest not using it and instead managing code through the Child Theme as shown above.
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 problem persists, please open a new support ticket.
