Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.
Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.
Before this ticket gets assigned to one of my colleagues, I will try to help.
I'm not sure what is stopping the plugin from being disabled when you disable it manually from the backend, and it would require a bit more investigation to find that out.
But there's a quick solution that should help you get it deactivated.
Log into the backend of the site (SFTP/FTP/"File manager" app if you have access to it from the hosting backend) > wp-content > plugins > find the "wp-seo-multilingual" folder and rename it to whatever you want (you can add "1" at the end).
That should instantly deactivate the plugin from the WordPress backend.
I hope that you will find this information helpful.
I don't believe there is a significant issue with the site. It seems that something outside of WPML is interfering with the deactivation process.
If this is not a priority for you and you prefer not to disable the plugin, I wouldn't worry too much about it.
It's also good to know that there is always a quick solution to force-disable that plugin (or any other plugin, whether WPML or not) if you ever need to do so.
