Problem: The client is experiencing a repetitive internal server error (error 500) that occurs frequently. Disabling the WPML plugin or resubmitting the permalink of the homepage temporarily resolves the issue, but it persists and affects the website's functionality. Solution: We have identified that the Object Cache is causing the issue. To resolve this, follow these steps: 1. Navigate to the WordPress Dashboard. 2. Go to Settings > Object Cache. 3. Click the disable button for the Object Cache. After performing these steps, the pages should work without issues, even with all WPML plugins active.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client has translated the user biography using String Translation following the instructions from a WPML forum article. However, the translation does not appear on the front page when using the Elementor "Author box widget" which is supposed to fetch the translated "user bio" string. Solution: We recommend translating the Author's bio using the "String Translation" as outlined in our documentation on Translating User Meta Information with WPML. When using the Author box widget, the translated template should display the text in the correct language. If you previously used a manual translation method for the template, we suggest switching to the WPML's Advanced Translation Editor (ATE) for translating this widget.
If this solution does not seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: The client has translated headers and footers from Hebrew to English using Elementor. Despite following a tutorial, the original Hebrew headers and footers are still displayed on the English version of the site. The client suspects a conflict between the Hebrew and English templates and is also seeking advice on the compatible MariaDB version for the plugin. Solution: We reviewed the client's site and identified that the header for the English version had not been translated. We recommend translating the header at this link and checking if that resolves the issue. Regarding the MariaDB version, we advise consulting with the plugin support for the exact version required.
Problem:
From some reason I can't delete the selected strings, please refer the image I've provided.
Let me stress that there are quite a lot to delete (6,2821 records). The string were created accidently and I don't need them there.
Solution:
To delete all the strings belonging to a certain domain:
- scroll down to Remove strings by domain and click Remove strings
- select the domains of strings you don’t need anymore and click Remove
The untranslated strings in these domains will no longer appear on the String Translation module. Here it goes a screenshot describing this process: https://snipboard.io/9rMaS4.jpg
نستخدم ملفات تعريف الارتباط لتحسين موقعنا الإلكتروني وخدماتنا.
تسمح لنا موافقتك بمعالجة بيانات مثل سلوك التصفح.
قد يؤثر عدم الموافقة على بعض الميزات.
وظيفي
نشط دائماً
مطلوب لكي يعمل موقعنا الإلكتروني ويتواصل بشكل صحيح.
التفضيلات
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
الإحصائيات
نستخدمها لتحليل إحصائيات موقعنا.
المعلومات التي يتم جمعها مجهولة الهوية تماماً. التخزين الفني أو الوصول الذي يتم استخدامه حصريًا لأغراض إحصائية مجهولة الهوية. بدون أمر قضائي، أو الامتثال الطوعي من قبل مزود خدمة الإنترنت الخاص بك، أو سجلات إضافية من طرف ثالث، لا يمكن عادةً استخدام المعلومات المخزنة أو المسترجعة لهذا الغرض بمفردها لتحديد هويتك.
التسويق
تقوم ملفات تعريف الارتباط هذه بتتبع تصفحك لتقديم إعلانات ذات صلة بك.
