Unable to open second language on backend

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing an HTTP ERROR 500 when trying to switch to the French language in the Admin dashboard.
Solution:
We identified that the issue was related to a known problem with the Kadence Blocks and Kadence Blocks Pro plugins. We provided a workaround that involves the following steps:
1. Temporarily deactivate the Kadence Blocks and Kadence Blocks Pro plugins.
2. Activate WPML String Translation.
3. Delete the problematic strings as described in the errata page: https://wpml.org/errata/kadence-pro-plugin-sprintf-too-few-arguments/.
After applying this workaround on a staging site, the issue was resolved, and we advised the client to test it on their staging site before applying it to the live site.

Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket in the WPML support forum.

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: Known issue

This topic contains 22 replies, has 2 voices.

Last updated by Lauren 9 months ago.

Assisted by: Lauren.

Author	Posts
March 6, 2024 at 4:37 pm #15380836
michelR-20	Thanks Lauren So I narrowed down the culprits to these plugins: - rename-kadence-blocks - rename-kadence-conversions - rename-kadence-pro - rename-kadence-woo-extras I need the functionality of these plugins for the site. Is there a solution other than turning them off? Strange because I have another site grafikexperts.com with an similar setup and plugins and it is running fine.
March 6, 2024 at 6:03 pm #15381200
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	Okay great, this helped me find the solution. This errata is currently open. I tested the workaround on the staging site we set up and and was able to activate Kadence Blocks and Kadence Blocks Pro, so I believe the issue is resolved. Feel free to test further on the staging site and then copy the workaround from here on your live site: https://wpml.org/errata/kadence-pro-plugin-sprintf-too-few-arguments/ Note: you will need to temporarily deactivate Kadence so that you can activate WPML String Translation and delete the strings. Please let me know if you need any further assistance and I will be happy to help.
March 6, 2024 at 6:41 pm #15381282
michelR-20	When you say "temporarily deactivate Kadence" do you mean the Theme or Any/all Kadence Plugins? - Kadence Blocks - PRO Extension - Select Kadence Blocks – Gutenberg Blocks for Page Builder Features - Kadence Captcha - Kadence Conversions - Popups, slide-ins - Kadence Pro - Premium addon for the Kadence Theme - Kadence Shop Kit - Kadence WooCommerce Email Designer
March 6, 2024 at 6:53 pm #15381290
michelR-20	I can't find the "%TEXTDOMAIN%" text on WPML > String Translation page on the Live site. I did find 3 on the Test site.
March 6, 2024 at 7:00 pm #15381294
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	You just need to deactivate the ones that were causing a conflict so that you can access String Translation. If you can keep them active and access string translation, then you can leave them. Since you are not seeing the text domains on the live site, are you seeing the error still in the debug log? Are you able to switch to French now?
March 6, 2024 at 7:19 pm #15381325
michelR-20	I temporarily deactivated all Kadence plugins. I found and deleted 3 "%TEXTDOMAIN%" texts strings on WPML > String Translation. But still seeing error and unable to switch to French on the live site.
March 6, 2024 at 7:27 pm #15381333
michelR-20	Please disregard previous message. I am NOT getting the error any more. I can switch and view French Content from the backend. Thanks so much!!
March 6, 2024 at 7:27 pm #15381334
Lauren Supporter Languages: English (English ) Timezone: America/New_York (GMT-05:00)	I logged into the live site, found the three strings in String Transltaion under the %textdomain%, deleted those strings, and then was able to load the French backend ( I tested the plugins page). I was also able to load Pages and Posts. Which page are you loading on the backend that is not working for you, so I can double check?