Problem: The client's development site, "powergate.relevantnettside.no", is not appearing on the WPML account management page for AI credits, and they are unable to add credits. Solution: We recommend unregistering WPML from the production site and removing the site from the WPML.org account. Then, register the development site with a new key. Here are the steps: 1. Go to Plugins -> Add Plugin -> Commercial tab on your website. 2. Click the 'unregister' link to unregister WPML. 3. Visit https://wpml.org/account/sites/ and delete the existing site key. 4. Return to Plugins -> Add Plugin -> Commercial tab on your website. 5. Click the 'register' link to register with a new key.
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 the problem persists, please open a new support ticket at WPML support forum.
Problema: Se stai riscontrando difficoltà nel rilevare e tradurre elementi come header, footer, sidebar del blog e altri elementi del tema in WPML, il problema potrebbe essere dovuto alle impostazioni di traducibilità di questi elementi. Soluzione: Per rendere traducibili header, footer e sidebar, segui questi passaggi: 1. Vai in WPML → Impostazioni → Traduzione tipi di contenuto. 2. Imposta Header, Footer e Side Panel come Traducibili. Questo ti permetterà di tradurre questi elementi senza problemi. Per quanto riguarda la traduzione dei widget, puoi consultare la nostra documentazione qui: https://wpml.org/documentation/getting-started-guide/translating-widgets/
Se la soluzione proposta non risolve il tuo problema o se le informazioni sembrano non aggiornate, ti consigliamo di verificare i problemi noti su https://wpml.org/known-issues/, verificare la versione della correzione permanente e confermare che hai installato le ultime versioni di temi e plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: You are trying to translate an HTML/CSS table using the Advanced Translation Editor, but encounter issues where the CSS styling is lost during the translation process. Previously, the editor only showed the strings of each cell for translation, but now it affects the styling. Solution: The issue arises from the mix of CSS and HTML in the translation process. The Advanced Translation Editor is not designed to handle CSS, JavaScript, or PHP; it strips out HTML markup and merges it again after translating the strings. To resolve this, you should use the field for "Custom CSS" on the advanced tab of the HTML widget.
Alternative:
1. Remove the link tag and the CSS from the HTML you are translating to ensure the translation works as expected. 2. Separate concerns by including the CSS in a "Hello Elementor Child Theme". You can set up the child theme following this guide: Setting up the "Hello Elementor Child Theme" 3. Include the stylesheet in the theme file functions.php:
4. Move your CSS to a file at /css/custom-table.css.
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: The client frequently updates their QA server with data from the production environment, which involves changing URLs and reactivating WPML. This process often results in site keys becoming inactive and a loss of translation credits. The client seeks a way to synchronize the QA and production environments without losing credits and to recover lost credits. Solution: 1. Ensure that the QA domain name remains consistent when reactivating WPML to avoid unnecessary site key changes. 2. Navigate to WPML > Support > Troubleshooting Link and share the Advanced Translation Editor ID for both production and staging sites. 3. We have resolved issues on our translation server that were causing lost credits and multiple activations with the same domain name. This should prevent similar issues in the future. 4. Always generate a new sitekey when activating WPML on a new domain to avoid conflicts.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
