Problem: After updating WPML, you can't use the translation dashboard due to PTC activation and WPML requesting context settings. Attempts to save context settings show as saved but without actual changes. Additionally, you encounter an 'ApiAuthenticationError::InvalidSignature' and error 403 when making requests to specific WPML API URLs. You also face issues disabling PTC and have tried unregistering and re-registering the site multiple times without success. Solution: The issue stems from the site key being incorrect because the website URL is registered under a different active WPML user. To resolve this, the site needs to be unregistered from the other user's account before you can register it under yours. If the other user is part of your organization, coordinate with them to manage the registration. The username associated with the other account is 'riina'. If you're unsure who this might be or need further assistance, we recommend contacting us directly through our contact form.
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 issue persists, please open a new support ticket.
Problem: You are trying to install the WPML plugin using the OTGS Installer, but it is not working across multiple websites. Solution: If you're experiencing this issue, we recommend following these steps to resolve it: 1) Visit https://wpml.org/account/websites/ 2) If the site URL is already registered, delete it from the list. 3) Re-enter the site URL to create a new site key. 4) Click "Show key" and copy it. 5) Go to Plugins > Install > Commercial (tab) on your WordPress dashboard and enter the key to re-register WPML. If WPML is still registered there, de-register it first.
This solution might be irrelevant if it's outdated or not applicable 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 you still need help, please open a new support ticket at WPML support forum.
Problem:
The user was managing credits on their website using WPML and encountered discrepancies. They paid a EUR4000 invoice, assuming it was for prepaid credits. However, the 'Manage Credits' section and the website's front-end display did not align: WPML marked the site as inactive and showed 'Pay as You Go' instead of 'Prepaid'.
Solution:
The payment made was not for prepaid credits but was a 'One-time safety limit payment' under the Pay-As-You-Go model. This model allows credits to be used first, with payment due the following month. The site had consumed a large number of credits, triggering a security limit that required payment before continuing. After the subscription was canceled, the site reverted to using pre-purchased credits.
If this solution does not resolve the issue or seems outdated, it is recommended to check the related known issues, verify the version of the permanent fix, and confirm that the latest versions of themes and plugins are installed. If further assistance is needed, please open a new support ticket.
Problem: If you're encountering an error message 'Change the field group translation setting', seeing a lock icon when trying to update content, or having issues updating the WPML plugin, here are the steps to resolve these issues. Solution: 1) For the error message 'Change the field group translation setting', it's actually a warning indicating a needed adjustment. Set the ACF Field Group to 'Do not translate'. More details can be found here: https://wpml.org/errata/advanced-custom-fields-field-group-should-be-set-as-not-translatable/ 2) If the WPML plugin won't update, it might be due to the site still being registered under an old domain. To fix this, go to WPML → Plugins → All Plugins, open the Commercial tab, click 'Unregister' at the top right, and then add the new site key from your WPML account: https://wpml.org/account/sites/ 3) If you encounter a lock icon when updating content, this is expected unless translation preferences are configured. Set your preferred translation option as explained here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-the-acf-options-page-custom-fields-with-wpml/#translating-options-page-custom-fields If these solutions do not resolve your issues or seem 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
The client is experiencing an issue where the WPML site key is not working, and there is a message in WP Admin indicating an inability to connect to wpml.org. Despite trying to re-register with both an existing and a new key, the issue persists.
Solution:
We recommend following the steps outlined in a similar case to determine if the same bug is affecting your site. Please visit the following link to try the suggested workaround:
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are unable to find the invoice for a transaction made on 3/7 this year with WPML. Solution: We have sent the requested invoice to your email. If you're experiencing this issue and have not received the invoice, or if you have further questions, we recommend you contact our accounts team directly at hello@wpml.org.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 issue persists, please open a new support ticket.
Problem: The client needed help reconnecting staging to production's credits for translating pages that were updated in staging but displayed untranslated content. Solution: We recommended re-registering both the staging and production websites to resolve the issue. Here are the steps we suggested: 1. Visit https://wpml.org/account/sites and remove the website from the list. 2. Add it again and copy the newly generated key. 3. In your website's admin panel, go to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". 4. Register the website again using the key copied in step #2. After completing these steps, re-assign the credits and connect the websites again by following the instructions here: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-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. Should you need further assistance, please open a new support ticket at WPML support forum.
