Hi there,
I briefly chatted with Noman about this.
I encountered fatal errors yesterday, after which Andrey advised me to check for updates. That seemed to have solved it, but today, nearly every click ( backend editor ) from one language to another takes an enormous amount of time and creates a "critical error" messages. the site does not crash, but I can't do anything in the backend.
I tried to run a Duplicator backup with WPML activated, but that crashed after 1,5 minutes.
I disabled all WPML and ran a duplicate.
After that I re-activated all WPML and tried clicking on something ( Users in this case ) in the backend and got a fatal error again after 1,5 minutes.
I found out that the problem stems from WPML String Translation. When i deactivate that one, everything works, but when I re-activate it, every click leads to a crash.
We wanted to go live today, but that's not going to work.
Hope you can help! this is getting rather urgent!
thanks,
Bye
Ward
While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps or if I can help with the issue quickly.
Please share WordPress's debug log. Please check this page for instructions.
To enable it, open your wp-config.php file and look for
define('WP_DEBUG', false);
Change it to:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
After this, repeat the action that causes the problem on your site. The errors will be saved to a debug.log log file inside the /wp-content/ directory. Then please share the errors with us.
Hi Itamar,
Good to get your response!
I already enclosed the debug info in my first message, but I'll do that again.
After this, Ill activate String Translation and send you athe debug info again.
Bye
Ward
The debug info that you added initially in this ticket is the WPML debug info. My colleague asked for the WordPress debug information which will let us know exactly what is happening.
Please paste the content 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). Or you can also use a service like Dropbox or Google Drive.
Hi Mihai,
I will do that in a few hours.
I already created an admin account for you in the site, so if you want, i can insert the details here. So you can take a look. I made a duplicate this afternoon.
Bye
Ward
Thank you for the Debug.log information. Just to make sure, this error happens always in the backend when the WPML String Translation plugin is active, am I correct?
Please fill in the private details fields after a full site backup{mandatory}. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information-sharing policies.
Also, please allow me to make a duplicator copy of your site using the Duplicator plugin(https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the bug without affecting your live site.
I can translate the posts and pages in my local copy after the following steps. Please try it after a full site backup{mandatory} and let us know your feedback.
1) Switch to a default WordPress theme like 2023
2) Deactivate all the plugins except WPML
3) Activate WPML String Translation
4) Activate the plugins as a group of three or four
5) Switch back to the default theme of the site
6) Translate the posts and pages
--
Thanks!
Hi Bigul,
Thanks for getting back to me.
I followed your list and after going through points 2, 3 and 4 several times, I can positively tell you that it all goes to plan until I activate WooCommerce.
After activating WooCommerce, waiting times for clicks go through the roof and result in server errors.
So, conclusion; WooCommerce and String Translation don't seem to like each other very much!
Over to you! 🙂
Bye
Ward
Here's the dropbox link to the current debug.log: hidden link
I followed your steps exactly as you set them out in your earlier message.
When I found that things became extremely slow again and failed, after enabling the plugins in groups of three, I disabled them again and started over.
Eventually I found out that everything kept running okay, until I tried to activate WooCommerce, with String Translation activated.
This is becoming a big problem, especially now we passed the go live date twice!!
I've made a complete backup yesterday, so feel free to try your way in the test.russian-socks.com environment yourself! Nothing breaks when you get to the point where things give a server error. You can simply step back in the browser and disable String Translation.
Thank you for the details and Debug log file. The Debug log is showing a lot of DB errors. This requires further debugging.
I would like to know the hidden link is a staging/dev site. Because a clone copy of a live site in a similar environment helps us a lot in debugging. So please confirm.
We would like to make sure the issue is existing in hidden link in a minimal setup or not.
