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.
This topic contains 4 replies, has 2 voices.
Last updated by saeedG-2 1 day, 11 hours ago.
Assisted by: Kor.
Author | Posts |
---|---|
November 14, 2024 at 6:06 am #16400706 | |
saeedG-2 |
Background of the issue: Symptoms: Questions: |
November 14, 2024 at 8:29 am #16401064 | |
Laura Supporter
Languages: English (English ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00) |
Hi, thanks for contacting us. Before we continue debugging your issue, please update WPML to version 4.6.14. The version you're currently using is not compatible with WordPress 6.7 and that may be the cause of your problem. |
November 14, 2024 at 8:53 am #16401260 | |
saeedG-2 |
still the same problem after the update. |
November 14, 2024 at 10:17 am #16401602 | |
Andrey Supporter Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00) |
While one of my teammates takes care of your ticket, I will provide you with the first debugging steps. “500 error” means that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code. First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debug. You can do this by adding a few lines to the site’s wp-config.php file. With error log enabled, you will see what the actual problem is. To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to: define('WP_DEBUG', true); In order to enable the error logging to a file on the server you need to add yet one more similar line: define( 'WP_DEBUG_LOG', true ); In this case, the errors will be saved to a debug.log log file inside the /wp-content/directory. https://wpml.org/documentation/support/debugging-wpml/ Let us know what you see after the debug mode has been enabled. |
November 14, 2024 at 10:40 am #16401704 | |
saeedG-2 |
I mean the menus were fine before so i dont know, it became like this when of your support team (Noman) did something with the premalinks for another issue. |
November 15, 2024 at 4:40 pm #16409400 | |
Kor Supporter
Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00) |
Thanks for your reply. I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified. Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements. Your upcoming reply will be treated with confidentiality and will only be visible to you and me. ✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup. |
November 18, 2024 at 3:33 am #16412640 | |
Kor Supporter
Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00) |
Thanks for your reply. I've tested the navigation menu links here hidden link and I'm not getting any issues. Could you record a short screen recording using this free tool hidden link so that I could see the issue that you're getting? |
November 18, 2024 at 6:04 am #16412832 | |
saeedG-2 |
somehow i think i fixed it. |