Background of the issue:
I am trying to edit the translation of the posts in the CPT called 'Nemovitost'. You can see the issue at this link: hidden link.
Symptoms:
When I click on the translation icon, I only get information about a critical error. The error message is:
Fatal error: Uncaught TypeError: array_walk(): Argument #1 ($array) must be of type array, string given in /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Engine/native.php:44 Stack trace: #0 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Engine/native.php(44): array_walk() #1 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff.php(55): Text_Diff_Engine_native->diff() #2 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Renderer/inline.php(167): Text_Diff->__construct() #3 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Renderer.php(170): Text_Diff_Renderer_inline->_changed() #4 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Renderer.php(143): Text_Diff_Renderer->_block() #5 /www/hosting/till6.dev/fkr/wp-includes/class-wp-text-diff-renderer-table.php(310): Text_Diff_Renderer->render() #6 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Renderer.php(170): WP_Text_Diff_Renderer_Table->_changed() #7 /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Renderer.php(143): Text_Diff_Renderer->_block() #8 /www/hosting/till6.dev/fkr/wp-includes/pluggable.php(3302): Text_Diff_Renderer->render() #9 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/translation-jobs/class-wpml-tm-field-content-action.php(111): wp_text_diff() #10 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/translation-jobs/class-wpml-tm-field-content-action.php(79): WPML_TM_Field_Content_Action->get_diff() #11 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/translation-jobs/class-wpml-tm-field-content-action.php(42): WPML_TM_Field_Content_Action->content_from_elements() #12 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/menu/translation-editor/class-wpml-translation-editor-ui.php(176): WPML_TM_Field_Content_Action->run() #13 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/menu/translation-editor/class-wpml-translation-editor-ui.php(91): WPML_Translation_Editor_UI->output_model() #14 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/menu/translation-queue/class-wpml-translations-queue.php(92): WPML_Translation_Editor_UI->render() #15 /www/hosting/till6.dev/fkr/wp-content/plugins/sitepress-multilingual-cms/classes/class-wpml-translation-management.php(342): WPML_Translations_Queue->display() #16 /www/hosting/till6.dev/fkr/wp-includes/class-wp-hook.php(324): WPML_Translation_Management->translation_queue_page() #17 /www/hosting/till6.dev/fkr/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #18 /www/hosting/till6.dev/fkr/wp-includes/plugin.php(517): WP_Hook->do_action() #19 /www/hosting/till6.dev/fkr/wp-admin/admin.php(260): do_action() #20 {main} thrown in /www/hosting/till6.dev/fkr/wp-includes/Text/Diff/Engine/native.php on line 44
Questions:
Why am I encountering a fatal error when trying to edit translations?
How can I resolve this?
We suspect a collision with another plugin might cause this problem. If possible, get your site down to a minimum environment, with no plugins activated except WPML, Strings Translation, and JetElements. Then, please check if the problem persists. If it does not continue, start by activating the plugins individually and checking when the issue comes back, then report to me which plugin was the culprit.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
*** If your site is live, you might want to try those procedures in a staging environment or a snapshot of your site on your local server or another server. ***
it is most likely not a conflict with another plugin. I deactivated all plugins and left only WPML and Strings Translation. I then tested the translations on the WP pages. The fatal error is no longer displayed, but I still see meaningless characters instead of text in the editor. This is actually the same situation we encountered during our initial chat.
Since this is a staging website, you can test these attempts yourself and don't have to wait for me. I just need to know how to solve the problem on the production website. You have access to the administration. I would appreciate it if this could be resolved very quickly, as the client is currently unable to translate anything on the production website.
Moreover, I am obviously not the only one dealing with this problem. I heard from a colleague that he has the same problem on another website (see https://wpml.org/forums/topic/broken-characters-like-xz/).
Indeed, it seems to be the same issue as your colleague is experiencing. Our second-tier supporter has debugged the issue. He prepared a fix for this issue but encountered a server issue when applying it. We are currently waiting for you or your colleague to inform us when the gzuncompress function is active on the server. You can read Kor, my colleague's reply here: https://wpml.org/forums/topic/broken-characters-like-xz/?paged=3#post-17612878
I assume that both sites are hosted on the same server.
Can you please confirm this?
We need a copy of your site to investigate this issue further. Please allow me to take a copy of your site. For this, I must install a plugin like Duplicator or All-in-One Migration. Please let me know if you agree.
Our second-tier supporter has prepared a custom plugin to fix the problem on your site. That plugin is similar to what our second-tier supporter tier has successfully used on your colleague's site on the same server. However, there is an error that our second-tier supporter can't see when he tried to use this plugin on your site. This error prevents applying the fix. Our second-tier supporter says that the WordPress debug.log is missing. Can you please check the debug.log and share the error with us?
I added the dbug.log file, but I don't see any errors. Try what you need to try. If any errors appear, I'll let you know. At the same time, I enabled the gzuncompress function in the PHP settings. It was disabled by default, but a colleague with whom you discussed a similar problem said that it was necessary to activate this function.
Thanks for enabling the gzuncompress function in the PHP settings. This, probably in combination with the fix our second-tier supporter has applied, has fixed the problem. Now, when I check a page and a post that once had this problem, there are no meaningless characters. Please see the attached screenshots.
For old translations that were sent for translation before the fix, please go to WPML -> Translation Dashboard -> Translation Jobs, select those jobs, and cancel them.
Can you please confirm that this problem is fixed now?
In addition to the above, our second-tier supporter explains the following.
It looks like the issue was resolved simply by enabling gz compression on the server. This means the underlying problem was not related to WPML itself, but to gz compression being disabled earlier. You can safely remove the temporary fix plugin that was provided. No further action is required, as long as gz compression remains enabled on the server. Also, just as a note: in the next WPML update, there will be a built-in warning to alert users if gz compression was previously available but becomes disabled again.
I accessed your site and removed the ICL Translate Field Data Fix.
Hello, I'm afraid the problem has not been solved. I still see those characters in the translation from Czech to English for the first two properties. Could you take a look at it, or send me a link to your ICL Translate Field Data Fix?
I could see this problem only for the Vila ZARA property. So I canceled the translation of this property that was in progress. I then deleted it, and now you can translate it normally. Please see the attached screenshot.
