Problem: If you're experiencing an Error 500 due to reaching the memory limit of 256M on your website with WPML installed, it's essential to identify what is consuming so much memory. Solution: We recommend the following steps to diagnose and potentially resolve the issue: 1. Edit your
wp-config.php
file and insert the following lines just before the /* That's all, stop editing! Happy publishing. */ part:
2. Try to reproduce the issue. 3. Locate the debug log at: /wp-content/debug.log and paste the latest lines here, ensuring you censor any sensitive information. For more details on debugging in WordPress, visit https://codex.wordpress.org/Debugging_in_WordPress. Additionally, obtain the latest server debug logs to pinpoint what exactly consumes as much memory. You may need to contact your hosting support if you are unsure how to locate these logs.
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: Der Kunde hat Probleme mit falschen URL-Pfaden und eingebetteten PDFs in übersetzten Posts. Die URL-Pfade und PDF-Shortcodes ändern sich unerwartet in verschiedenen Sprachversionen. Solution: Wir empfehlen, eine XML-Konfiguration für den PDF-Shortcode zu erstellen, um sicherzustellen, dass diese korrekt übersetzt werden können. Fügen Sie folgende XML-Konfiguration in WPML > Einstellungen unter 'Benutzerdefinierte XML-Konfiguration' ein:
Anschließend sollten Sie den originalen Inhalt bearbeiten, speichern und den Übersetzungseditor öffnen, um die Shortcode-URLs korrekt zu übersetzen. Für die URL-Pfade der Posts empfehlen wir, die Permalink-Slugs direkt im WordPress-Editor für die übersetzten Beiträge anzupassen, basierend auf den aktuellen Einstellungen, die automatisch aus dem Titel generierte URLs verwenden.
Diese Lösung könnte veraltet sein oder nicht auf Ihr spezifisches Problem zutreffen. Wir empfehlen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen.
Problem: The client manually converted an English webpage to German, but the FAQ section accordion did not translate and continued to display English text. Solution: We recommend the following steps to resolve this issue: 1. Add the following XML configuration in the WPML >> Settings > Custom XML Configuration section:
2. Make a minor change in the default language page title to trigger the translation process, then complete the translation in the German language. This should ensure that the FAQ section displays correctly in German on the frontend.
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 have a website built with Gutenberg and Greenshift content builder, and you've created custom XML settings. However, dynamic links are not translating correctly, displaying incorrect dynamic text instead of the expected translation. Solution: If you're experiencing this issue, we recommend the following steps: 1. Navigate to WPML >> Translation Dashboard. 2. Select the "Archief: Use Case" under Site Templates. 3. Send it for translation. This should resolve the issue with incorrect link translations in secondary languages.
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 problem persists, please open a new support ticket.
Problem: Клиент столкнулся с проблемой, что системные поля не отображались и не переводились должным образом. Он вспомнил, что в настройках "Перевод пользовательских полей" все системные поля скрыты, и изменил статус поля et_additional_block с 'Не переводить' на 'Переводить', что решило проблему. Solution: Мы рекомендуем следующие шаги для решения подобных проблем: 1. Перейдите в WPML → Settings → Custom Fields Translation. 2. Активируйте опцию “Show ‘Multilingual Content Setup’ meta box on post edit screen”. 3. Вернитесь к редактированию страницы на языке оригинала. 4. В разделе пользовательских полей нажмите “Show system fields”. 5. Найдите нужное пользовательское поле и установите для него режим Copy. 6. Внесите изменения на странице и сохраните её. Если проблема не решится, мы рекомендуем вам открыть новый тикет поддержки. Также рекомендуем проверить известные проблемы, версию исправления и убедиться, что у вас установлены последние версии тем и плагинов.