Problem: The client experienced issues with their QA site (qa.instron.com) displaying the same credit balance as the production site after cloning and attempting to manage sitekeys and credits through WPML. Despite unregistering and re-registering the sitekey for the QA site, the credit balance remained unchanged, and the QA site disappeared from the WPML account's manage credits page. Solution: We recommended a complete refresh of the registration process to ensure proper synchronization between the QA site and the WPML account. The steps included: 1. Removing any existing QA site registrations from the WPML account. 2. Unregistering WPML from the QA site via the WordPress dashboard. 3. Generating a new site key for the QA site and registering it without assigning specific credits. 4. Verifying the credit display and site listing on the WPML account. Despite these steps, the issue persisted, indicating a deeper synchronization problem possibly related to how WPML handled the site as a 'copy' during the registration process. We then explored details of the migration wizard settings used during the process.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please also 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. For further assistance, you can contact us directly at the WPML support forum.
Problem: You are trying to use credits purchased for WPML, but you cannot because the WPML dashboard indicates that your website is inactive, even though the plugin on your website shows it is registered. Solution: We have resolved this issue from our end. You should now be able to use your credits. Please verify by checking if the WPML dashboard now reflects the active status of your website.
If this solution does not resolve your issue or seems outdated, we recommend checking the 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 problem persists, please open a new support ticket.
Problem: The client purchased a WPML subscription but was unable to implement it on their WordPress admin page. They also could not find the OTGS Installer plugin in WordPress. Solution: We advised the client to ensure that WPML is registered with a valid license key. Here are the steps we recommended: 1. Log in to your WPML.org account and navigate to the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key by clicking the trash icon. 3. Log in to your WordPress site, go to Dashboard >> Plugins >> Add new >> Commercial tab and click the Unregister WPML from this site link. 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy and paste the new key into the input box and press the Register button. After these steps, you should be able to download the OTGS installer plugin from: https://wpml.org/download/otgs-installer/ Note: The OTGS installer plugin is only necessary for installing the WPML Multilingual CMS and other WPML add-ons. If WPML Multilingual CMS is already installed and activated, you do not need the OTGS installer plugin.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problema: Stai cercando di attivare WPML sul tuo sito, ma quando inserisci la chiave di licenza ricevi un errore: 'Unable to parse data from service response'. Dopo aver verificato la connessione con i server WPML tramite un file curl-test.php, ricevi un messaggio di errore che indica 'Unknown or Unsupported API Call: repository_error'. Il server API non funziona e restituisce un codice errore 403. Soluzione: Abbiamo contattato il nostro team di sistemi che ha confermato che il tuo sito era stato bloccato dal nostro firewall. Abbiamo rimosso l'URL del tuo sito dalla lista dei blocchi, quindi ora dovresti poter registrare correttamente la chiave di licenza. Abbiamo verificato e la registrazione ora funziona.
Se la soluzione proposta non risolve il problema o se sembra non essere più attuale, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti per verificare la versione della correzione permanente e confermare che hai installato le ultime versioni di temi e plugin. Per ulteriore assistenza, visita il forum di supporto WPML.
