Hi There,
Thanks for contacting WPML Support. I would be happy to assist you in this matter.
From the Error message you've shared, the issue seems to be related to taxonomy terms. However, to understand the root cause of this issue, we need to check by doing a plugin conflict test. Please follow the steps mentioned below. Make sure to take a full backup prior to that.
- Kindly change your theme to ‘twenty-twentyone’ and deactivate all plugins except for WPML and its extensions. Verify if the error persists.
- If this resolves the problem, begin reactivating the plugins one at a time, and the theme at last. After each activation, check for any errors. This will enable you to identify the plugin/theme responsible for the issue.
Please let me know how it goes. I will be happy to assist you further.
Hi There,
Thank you for taking the time to identify the plugin and theme that are causing the problem.
After searching our directory of compatible plugins and themes, I found that WPML compatibility with the Jumpstart theme has been tested up to version 2.1. No compatibility information is available for the later versions of the theme. However, there is no record found regarding the compatibility of WPML with the plugin you mentioned. So the problem on your site might be happening due to a lack of compatibility.
Would you kindly try to replicate the issue on our sandbox environment? I would like to see what happens in a minimal and fresh environment.
- hidden link
If the issue is replicated successfully, we will also check if we have anything to do on our end.
In the meantime, you could also reach out to the theme author and consult with them regarding this matter. I hope they will share some guidance in this matter.
I replicated it in the environment provided. It is currently using a child theme of "Jump Start", and it is also replicable with the "Jump Start" theme.
Thank you Prosenjit
Hi There,
I hope you're doing well. Sorry for the delay in getting back to you due to the Weekend.
I appreciate your effort in reproducing the problem in our test environment. I have checked and found that the error goes away by disabling the “Theme Blvd Widget Pack” plugin. However, I also noticed that the parent version of the theme is outdated, which also might be a reason behind the issue.
Another issue that worries me is the lack of updates for the theme and plugin in the past few years. On the plugin page of WordPress(https://wordpress.org/plugins/theme-blvd-widget-pack/), you'll see that the plugin was last updated five years ago. Please check the links below to know more about the latest updates and versions.
- Theme: hidden link
- Plugin: hidden link
So, what you need to do is outlined below.
- Update the Theme to its latest version keeping the "Theme Blvd Widget Pack" enabled.
- If that solves the issue, continue using it.
- If the issue persists, you need to reach out to the support team of "Theme Blvd Widget Pack" and request their assistance in this matter. The compatibility of WPML needs to be added to that plugin so that it works properly in a multilingual environment.
You can also request them to join the Go Global Program of WPML. More information about this program is included in the link below.
Thank you for your assistance and looking into the sandbox environment. Regarding the theme, it seems like it is no longer being maintained by the developer and we are unable to change theme for the website at the moment as it will result with a through website redesign. The option that you suggest- to disable the “Theme Blvd Widget Pack” is not viable for us because this plugin is needed for our website to function.
However, the error clearly originates from WPML plugin, as you can see from the logs, so the question of the other plugin or theme are irrelevant. Suggesting to me to disable another plugin does not fix the problem that originates from WPML, not from the Widget pack.
Can you please send a ticket to the WPML developers to look into why this error is created from within WPML, instead of directing me to a different plugin’s developers which are not the source of the error.
I completely can understand your point. I agree that traces of WPML plugin is showing in the Error log, but if you check the error log closely, you'll see that one of the function in WPML plugin is not getting the expected arguments which is mainly causing the issue.
However after a thorough investigation, we have been able to detect he root cause of the issue. The arguments are'nt declare correctly in 2 places within the "Theme Blvd Widget pack" plugin, which mainly caused the fatal error. The issue gets fixed after adding the missing arguments within the plugin, and now the customizer panel loads fine.
Please check this video to understand where and what changes are made: hidden link
By following the video, please make the adjustments accordingly on your end and hope it will help. Feel free to let me know if you need further assistance. I will be happy to help.
