Problem: O cliente tem receios de problemas de duplicidade com o Google e SEO ao duplicar conteúdo para diferentes locais de idioma sem alterar nada nos posts. Ele questiona se adicionar um novo idioma Locale padrão en_US hreflang en_us e duplicar os posts de inglês genérico para o en_us idioma personalizado sem traduzir novamente causaria problemas de duplicidade com o Google e SEO. Solution: Nós confirmamos que o setup do cliente é válido e não deve apresentar problemas. O WPML SEO, em conjunto com um plugin de SEO como o Yoast SEO, deve automaticamente reconhecer quando se trata de um conteúdo duplicado e adicionar a informação de conteúdo canônico. Isso permite que o Google entenda que se trata de uma variação local, evitando penalizações por duplicação de conteúdo.
Se esta solução parecer irrelevante ou desatualizada, ou se não resolver o seu problema, recomendamos que abra um novo ticket de suporte. Também sugerimos verificar os problemas conhecidos, confirmar a versão da correção permanente e verificar se você instalou as versões mais recentes de temas e plugins.
Problem: Der Kunde berichtet, dass seit der Installation von WPML alle Seiten im klassischen Editor geöffnet werden, anstatt im WPBakery Backend Editor. Der Parameter &classic-editor wird automatisch zur URL hinzugefügt. Solution: Wir haben festgestellt, dass dieses Verhalten nicht direkt durch WPML verursacht wird, sondern eine Funktion von WPBakery ist, die aktiviert wird, wenn Gutenberg deaktiviert ist. Der Parameter &classic-editor ist Teil des WPBakery Codes und wird hinzugefügt, wenn auf die Bearbeitung von Beiträgen zugegriffen wird. Dieses Verhalten lässt sich auch in einer Sandbox-Umgebung ohne WPML reproduzieren. Weitere Informationen und mögliche Lösungen finden Sie hier: https://wordpress.org/support/topic/how-to-remove-the-classic-editor-from-every-edit-url/.
Falls diese Lösung für Ihr Problem irrelevant erscheint oder veraltet ist, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
Problem: The client was updating WPML to version 4.6.15 and Elementor to version 3.26, following the recommended update procedure. After the update, the Elementor editor stopped loading.
Solution: We recommended enabling debugging on the client's site to identify any errors causing the issue. The debugging process involves: 1. Enabling the WPML debugging feature, as detailed in our documentation: https://wpml.org/documentation/support/debugging-wpml/ 2. Attempting to open the Elementor editor again to ensure that any errors are logged in the debug.log file located in the wp-content directory. 3. Sharing the errors from the debug log with us for further analysis.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to create a new page using the Elementor page builder, but encounter an issue where the screen just spins grey when clicking 'add new page'. The page doesn't load unless the WPML Multilingual CMS plugin is disabled. Solution: If you're experiencing this issue, we recommend following the steps provided in this WPML forum thread: https://wpml.org/forums/topic/fatal-error-uncaught-error-class-elementorcoreschemescolor/. This solution addresses a similar problem where a PHP Fatal error occurs due to a missing class in Elementor when WPML is enabled.
Please note that this solution might be irrelevant if it's 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 at WPML support forum for further assistance.
