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: The client is experiencing issues with translating products on their WordPress site using WPML. The translations are stuck at 'in progress', and products are not being translated as expected. Solution: We have confirmed that all systems, including the Advanced Translation Editor (ATE), are now functioning correctly. There may be a short delay as the system processes a backlog of jobs. We recommend trying the translation process again and checking if the issue persists.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and confirm that you have installed the latest versions of themes and plugins. If the problem continues, we highly recommend opening a new support ticket for further assistance at our support forum.
Problem: You are trying to access the Translation Management Dashboard to manage translations for various post types, but the page is continuously loading with an error message stating 'MariaDB can only access 61 joint tables'. Solution: This issue is likely related to a known problem with WPML where too many database tables are being accessed simultaneously. We recommend checking the WPML errata page for this specific issue at https://wpml.org/errata/errata-wpml-4-7-1-wordpress-database-error-too-many-tables/. Please ensure that you have updated to the latest version of WPML, as version 4.7.2 addresses this issue. If the problem persists after updating, or if this solution does not apply to your case because it might be 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 you need further assistance, please open a new support ticket at WPML support forum.
**Problem:**
The user (cristianS-23) reported that WPML displayed a notification indicating "90 translations waiting for review," but no translations were found in the queue under Posts, Pages, Products, or Knowledge Base sections. The user wanted to resolve this issue and ensure it does not recur.
**Solution:**
1. **Investigation:**
- Confirmed no translations were marked as "waiting for review" in the interface.
- Identified that the issue likely stemmed from incorrect entries in the `icl_translation_status` database table.
2. **Fix:**
- Suggested editing the database to update the `review_status` column in the `icl_translation_status` table to `'ACCEPTED'`.
- Clarified that this might fix the immediate issue but noted the root cause could be related to plugin or theme conflicts.
3. **Implementation:**
- User manually applied the suggested database change, which resolved the issue.
4. **Preventive Action:**
- Advised disabling the review feature if not required to prevent similar issues.
- Provided steps to disable the feature:
- Navigate to **WPML > Settings**.
- Under **Automatic translation**, select **"Publish right away without reviewing"** and save the settings.
**Outcome:**
The issue was resolved, and the user chose to mark translations as accepted before disabling the review feature. Additional support was offered but not required.
