[Resolved] the Arabic V. shows website under maintenance
This thread is resolved. Here is a description of the problem and solution.
Problem: The Arabic version of your website was displaying a maintenance page instead of the expected content. This issue was due to incorrect settings in the Strings Translation for the Tutor Maintenance Mode. Solution: We resolved the issue by adjusting the Strings Translation settings. Specifically, the value for the string named
[tutor_option]enable_tutor_maintenance_mode
was incorrectly translated from 'off' in English to 'على' in Arabic. We corrected this by removing the incorrect translation and copying 'off' into the Arabic translation. This change fixed the problem, and the Arabic homepage should now display correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to view the Arabic version of my website, but it shows the website under maintenance. The issue can be seen at the following link: hidden link.
Symptoms:
The Arabic version of the website displays a maintenance page instead of the expected content.
Questions:
Why does the Arabic version of my website show a maintenance page?
How can I resolve the maintenance page issue on the Arabic version?
This ticket has been inactive for quite a while. I didn't get a reply from you. So, I've transformed this chat into a support ticket because you may still need our help. If you do, please reply to this ticket, and one of our supporters will continue helping you.
We suspect a collision with the theme or another plugin might cause this problem. If possible, get your site into a minimum environment, switching to a default WordPress theme like TwentyTwenty-Four and activating only WPML.
First, check whether the problem persists when only the theme is switched to TwentyTwenty-Four (for example). If it persists, deactivate all plugins except WPML and its add-ons. Then, please check if the problem persists. If it does not continue, start by activating the plugins individually and checking when the issue comes back, then report to me which plugin was the culprit.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
*** If your site is live, you might want to try those procedures in a staging environment or a snapshot of your site on your local server or another server. ***
Additionally, I could also see many custom directives in your .htaccess file. Please check if one of those directives causes this problem.
I deleted all directives in .htaccess file , switched to TwentyTwenty-Four , and deactivate all plugins except WPML and its add-ons. And still have the same error.
Please allow me to take a copy of your site. For this, I must install a plugin like Duplicator or All-in-One Migration. Please let me know if you agree.
Hello again,
To let you know, the issue is in wpml string plugin, so I deactivated it until we find the issue.
and I have added the All-in-One Migration plugin,
I fixed this issue on your site. Now the Arabic homepage is showing correctly even when the Strings Translation add-on is active. The problem was that the Tutor Maintenance Mode was not set to OFF for Arabic. This happened because in Strings Translation, the value of the string named [tutor_option]enable_tutor_maintenance_mode was translated from 'off' in English into 'على' in Arabic. Please see the attached screenshot. I removed the value and copied 'off' to Arabic. Please see the attached screenshot. This corrected the problem.
Can you please confirm that it is solved now and mark this ticket as resolved?
