Wpml creates issue with the php version 8.0 and "Good day, I opened a ticket and am still waiting for the problem to be resolved. I spoke to a technician who had a similar issue, so it seems that I am not the only one facing this problem. Right now, every time I try to modify or delete a product, I encounter a critical error. I have received responses from three different people at WPML, each asking me to provide new information, and I have to start explaining the problem all over again. I would really like to resolve this issue soon and find out why something is not compatible. My client cannot upload any new products, and every technician I have spoken to has told me that it is an issue with your plugin that needs to be resolved. Can we find a faster communication and resolution process for this matter? I am a graphic and web designer, not a coder. I would like to resolve this issue as soon as possible. Could someone please take a look at the problem and let me know how we can fix it? Right now, I feel stuck with no clear solution. I have already translated the entire site into English, which cost me money, and I do not want to switch to another platform I hope to hear from you soon.
I’m sorry that you ran into trouble with this! I’ll need a little more information to see what’s happening here.
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.
God day,I wanted to inform you that I've diligently followed the exact steps recommended by other WPML technicians in order to diagnose the issue. It appears that resolving this problem will necessitate a comprehensive examination of the Metronomie site, starting from the very beginning, and conducting an in-depth troubleshooting process. I've engaged with multiple technicians, and it seems that the issue may be related to your plugin and WooCommerce.
Could we work together to find a mutually agreeable solution and discuss the steps required to rectify this situation? I've provided all the necessary access to the site, and you have all the pertinent information at your disposal. It's been over a week, and we're still no closer to identifying the problem. I've invested a significant amount of money in translating the entire site and utilizing your plugin. It's crucial that we resolve this issue promptly, as the client is understandably dissatisfied with the current situation. thank Stephane
