Problem: The client is attempting to connect their site using WPML after transferring their domain and is unable to connect to other sites. Solution: 1. If you're trying to register WPML, generate a new WPML key by visiting https://wpml.org/account/sites. Then, navigate to your site's backend, go to Plugins > Add New > Commercial, click on "Register WPML," and enter the key. 2. For migrating your site to a new domain, use the "Duplicator" plugin. Download it from https://wordpress.org/plugins/duplicator/ and refer to the documentation at https://snapcreek.com/duplicator/docs/ and a tutorial at https://www.youtube.com/watch?v=3YDQ3Ey_2wY. 3. After migration, remove your old site/domain from your WPML account and add your new site to receive a new key, which you will enter in your site's backend. 4. If WPML detects that the site has been moved to a different domain, set the new site to "this is a copy of the main site" by following the instructions on this page.
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 you still need help, please open a new support ticket at WPML support forum.
Problem: The client is unable to connect the site with the same payment method for automatic translation, despite following previous support instructions. Solution: We recommend following the steps outlined in our documentation on how to connect your sites for automatic translation. You can find the detailed guide here: Automatic Translation Subscription for Multiple Sites. If you encounter any issues during the process, please provide us with details and screenshots to better assist you.
Please note that this solution might be irrelevant if it's 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, we encourage you to open a new support ticket for further assistance. You can do so here: WPML Support Forum.
Problem: The client needed clarification on their WPML billing method, specifically regarding the Pay-As-You-Go subscription, yearly renewal costs, and the assignment of credits across different sites. Solution: We explained that the WPML account renews automatically each year at a discounted rate. The Pay-As-You-Go subscription for Automatic Translation does not have a monthly fee and charges are based on the translation credits used. The first 2,000 credits each month are free, and additional credits are charged according to the pricing table. Unused credits do not carry over to the next month. Payments are processed via Stripe, and WPML does not store credit card information. For sites not using Pay-As-You-Go, credits can be added and do not expire. If credits are assigned to a site using Pay-As-You-Go, they will be used first.
For the specific issue with siteofwonder.de not connecting with the same payment method, we have created a separate support ticket to gather more information and assist further. You can follow the progress here.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if needed.
Problem: The client wants to hide or remove a category and its products only for the secondary language without affecting other languages. Solution: We recommend disconnecting the product translations from the original product. You can achieve this by editing the product translation in the WordPress editor and selecting "None" in the "This is a translation of" dropdown menu.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client is experiencing an issue where pages are not displaying correctly due to an error with the SSB WooCommerce MultiLanguage Products plugin. The error log shows:
Call to a member function get_cart() on null
at a specific file path. Solution: We recommend deactivating the SSB WooCommerce MultiLanguage Products plugin, reloading the page, and waiting a few seconds. This should allow the translation to be delivered completely to the site. If this solution does not resolve the issue or seems outdated, please check 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 the problem persists, we encourage you to open a new support ticket for further assistance at WPML support forum.
Problem: The client was experiencing an issue where the product prices in EUR were not consistent across the site. Specifically, the prices would change incorrectly when a product was added to the cart by a non-logged-in user and the country was changed at checkout. Additionally, the prices displayed incorrectly for logged-in users.
Solution: We identified that the issue was related to the tax configuration in WooCommerce. The 'Display tax totals' setting was set to 'As a single Total', which caused the total price, inclusive of tax, to only be visible on the checkout page after the address details were added. To resolve this and ensure consistent price display for both logged-in and non-logged-in users, we recommended the following steps:
1. Go to 'WooCommerce > Settings > Tax'. 2. Scroll down to 'Display tax totals' and change the setting to 'Itemized'. 3. Clear the caches from both the site and browser.
We advised the client to review the settings for Taxes and Shipping to ensure the price is displayed correctly for all users.
If this solution does not apply to your situation, or if it seems outdated, 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 the issue persists, please open a new support ticket with us.
