<b>Deprecated</b>: urlencode(): Passing null to parameter #1 ($string) of type string is deprecated in <b>/var/www/csi/html/wp-content/plugins/wp-seo-multilingual/classes/class-wpml-wpseo-filters.php</b> on line <b>131</b>
After adding this code as well i can see above warning on widgets:
Since we are not able to reproduce this on the staging site that we have set up, please provide a staging site where you are able to reproduce the issue. I understand you can't share the theme, but you will need to provide us a way to test the issue since we cannot reproduce it. I have marked the next reply as private so that you can share credentials if needed, or you can use the staging site that we have provided and you can make changes there in order to reproduce the issue that you are experiencing on your site.
As, we are unable to share the theme due to security and confidentiality reasons, we can suggest the following alternatives:
1. Call or Screenshare: If possible, can you arrange a call ? So, we can screenshare to demonstrate the issue directly. This way, you can observe the problem we are facing.
2. Video Recording: Alternatively, we can create a detailed video to show you the issue. Please let us know exactly what you would like to see in the video and steps to follow.
3. Version 4.7 Release date: Could you please confirm the release date for version 4.7 so we can update our client accordingly?
Additionally, please check the attachment for the issue we are facing.
1. We do not offer screensharing or video support.
2. We aren't doubting that the issue exists, the problem is that we need an environment where we can reproduce the issue so that we can try and find the cause as well as a solution. A video recording does not help with that.
3. We do not have an official release date as we are still currently in testing, but it should be very soon. You can also download a copy of the beta version from https://wpml.org/account/downloads/, and test in a staging environment of your own.
As you can see, if the problem is only reproduced with your custom theme, then we would require access to a site with the custom theme in order to further assist you. Aside from having that access, I'm not sure there is much more we can do at this point, since we can't troubleshoot the issue.