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.
Tagged: Exception
This topic contains 33 replies, has 4 voices.
Last updated by Alejandro 1 year, 10 months ago.
Assisted by: Alejandro.
Author | Posts |
---|---|
August 9, 2023 at 8:47 am #14173709 | |
paolo ursomando |
After updated WPML and then WordPress 6.3 (like you suggested in your latest email) I got error 500 when I try to login to wp admin and it depends on WPML String Translation update. If I disable it, all it's ok...how to fix it? Thank you |
August 9, 2023 at 8:54 am #14173741 | |
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00) |
While one of my teammates takes care of your ticket, I will provide you with the first debugging steps. The blank page means (or “500 error”) 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. |
August 9, 2023 at 9:59 am #14174647 | |
paolo ursomando |
I got it...how to upload the log file? |
August 9, 2023 at 10:02 am #14174679 | |
paolo ursomando |
the file size is increasing fast, it has almost exceeded 700mb |
August 9, 2023 at 10:04 am #14174683 | |
Mihai Apetrei WPML Supporter since 03/2018
Languages: English (English ) Timezone: Europe/Bucharest (GMT+03:00) |
Hi there. You can paste the content (if any) on a site like pastebin.com and then share the link here with us (only you and us will see the URL you are sharing). We will be waiting for your response. Mihai |
August 9, 2023 at 10:11 am #14174729 | |
paolo ursomando |
I uploded it via dropbox: hidden link Thank you |
August 9, 2023 at 5:02 pm #14177647 | |
paolo ursomando |
I created a site in staging where I first upgraded WPML to version 3.6.5 and String translation to 3.2.7 I then upgraded WordPress to version 6.3 and now I cannot access the backend as I am getting HTTP ERROR 500 If I disable the String translation plugin then I can access to the backend, if I enable it the problem occurs again. I have created for you staging site admin access and SFTP accesses: https://pastebin.com/4DXYWXqb Thank you |
August 10, 2023 at 1:06 pm #14182591 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
The problem is due to memory and it's not happening with WPML but with Divi and many plugins (WooCommerce related). The error is happening ebcause these plugins are creating a lot of issues, repeatedly and they end up exhausting the memory. I think that those plugins are not compatible with WP 6.3 then. Regards. |
August 10, 2023 at 1:54 pm #14183185 | |
paolo ursomando |
Hi Alejandro, I have updated WordPress 6.3 and all plugins (including WPML plugins) and the reported issue occurs only if the String translation plugin is active. If you disable your String translation plugin everything works perfectly with no memory issue or other problems. NB: Before your plugin update, everything worked perfectly. Now I disabled your plugin hidden link and all is ok, if you enabled it via SFTP you can check the issue comeback again. Finally there's no memory issue hidden link |
August 11, 2023 at 6:08 am #14185937 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Please watch this video because i can see i didn't explain well enough. I was not saying that you didn't have enough memory, but that basically all your plugins are NOT working correctly because of PHP issues (probably due to php 8.2 which is way too new for WordPress.) and when another plugin comes and touches something that is already not workng correctly, it makes it crash. Right now the errors you're seeing is because your site ends up without memory because of all the issues you have. I suspect that downgrading your PHP version to version 8.0 will at least take care of most of the issues on your site and prevent the memory exhaustion problem. if the problem keeps happening then, we will see different errors on the debug.log that will give us a clue about what's happening. Make sure you keep the debug.log enabled. rename the current file after you have downgraded your PHP version, that way we can have a shorter list of issues which you can send to me again as you did before. Regards. |
August 11, 2023 at 7:43 am #14186403 | |
paolo ursomando |
Hi Alejandro, I can't find any video but I followed your instructions. I renamed the debug log with php 8.2 and then switched to php 8.0, now you can get 2 debug log file: debug_8.2.log (from php 8.2) and debug.log (with php 8.0). I tried to enable your String Translation plugin again but the issue persists. You can check it, now there's php 8.0. PS: The strange fact is that before your update with wordpress 6.3 everything worked perfectly, after the update the problem occurs only if String Translation is enabled. Thank you |
August 11, 2023 at 8:39 am #14186769 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
The video is this one: hidden link, sorry about that! At this point, would it be possible to have access to your site and FTP access as well so i can investigate better what's going on? If the site is a production one, then may i suggest you clone the site to one of our servers so we can work risk-free on your end? i'm saying this because there's a chance i have to enable the String Translations Plugin and it would crash the site. Regards. |
August 11, 2023 at 8:43 am #14186913 | |
paolo ursomando |
Hi Alejandro, maybe you miss my message where I informed you about this: I created a site in staging where I first upgraded WPML to version 3.6.5 and String translation to 3.2.7 I then upgraded WordPress to version 6.3 and now I cannot access the backend as I am getting HTTP ERROR 500 If I disable the String translation plugin then I can access to the backend, if I enable it the problem occurs again. I have created for you staging site admin access and SFTP accesses: https://pastebin.com/4DXYWXqb Thank you |
August 11, 2023 at 8:56 am #14187093 | |
paolo ursomando |
Hi Alejandro, I provided you all accesses to my staging website via pastebin...is it ok? |
August 11, 2023 at 10:25 am #14187807 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Tht pastebin might be private because it doesn't allow me to see it you can add the credentials in the fields i have activated for you in your next reply. |