Problem: You are experiencing an issue where the prepaid credits after purchasing a new license are not reflecting correctly on your account. The expected credit balance was 144990, but it showed only 54990. Solution: We identified that the credits were applied to the wrong ATE ID. We have now moved the credits to the correct ATE ID. To resolve this, please follow these steps: 1. Visit your sitekey dashboard at https://wpml.org/account/sites/. 2. Remove the domain 'kintojoin.io' and then add it again to generate a new sitekey. 3. Update the new sitekey on your website by going to WP > Plugins > Add new > Commercial Tab > Click Unregister sitekey. 4. After updating, please share your new sitekey with us for further verification.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.
Problem: The client was experiencing issues with WPML credits not being visible in the WPML dashboard despite being available on the WordPress side. They were confused about the process of transferring credits between accounts and re-registering WPML with a new key. Solution: We advised the client to follow these steps to resolve the issue: 1. Navigate to https://wpml.org/account and use the 'Add/Remove' button to move the credits back to their WPML.org account. 2. Visit https://wpml.org/account/sites, remove the current WPML key, and generate a new one for the site. 3. In the WordPress backend, go to Plugins > Add New > Commercial, unregister WPML using the old key, and re-register with the new key. 4. Assign the credits back to the site by following the steps at https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is encountering a '403 ERROR' during the WPML setup, which seems to be caused by the hosting firewall blocking external connections required by WPML. Solution: We confirmed that there is no block from our side related to the client's site. To continue the setup without lowering the hosting security measures, we recommend adding the WPML license key directly in the
wp-config.php
file. Detailed instructions can be found here. However, the client will still need to allow at least one connection to our API for the key validation. Once validated, manual translations can be used without further connections. For automatic translations, there are limitations due to the lack of external connections, as explained in this forum post.
