PHP Fatal error: Uncaught InvalidArgumentException

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

Problem:
The client is experiencing a PHP Fatal Error when trying to save a translated page using WPML with the Avada theme. The error message indicates an 'Uncaught InvalidArgumentException: No translation entry found'.

Solution:
We recommend the following steps to resolve the issue:
1. Navigate to

Avada > Library

in your dashboard.
2. Identify the Library Elements designated as Global.
3. Access the translations for these Global Library Elements and ensure they have been translated independently. For guidance on translating items independently, please refer to the following article: Translating Independently.

If the issue persists after following these steps, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at 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: Exception

This topic contains 1 reply, has 0 voices.

Last updated by Dimitri 4 months, 3 weeks ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
November 28, 2024 at 4:47 pm #16456430
Dimitri	Background of the issue: I am trying to save a translated page using WPML. PHP Fatal error: Uncaught InvalidArgumentException occurred during this process. Symptoms: PHP Fatal error: Uncaught InvalidArgumentException: No translation entry found for query: s:34:" trid = %d AND language_code = %s ";a:2:{i:0;s:4:"8457";i:1;s:2:"es";} in /public/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php:193nStack trace:n#0 /public/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php(65): WPML_TM_ICL_Translations->select_translation_id()n#1 /public/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php(43): WPML_TM_ICL_Translations->build_from_trid()n#2 /public/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-records.php(155): WPML_TM_ICL_Translations->__construct()n#3 /public/wp-content/plugins/sitepress-multilingual-cms/inc/actions/wpml-tm-post-actions.class.php(67): WPML_TM_Records->icl_translations_by_trid_and_lang()n#4 /public/wp-content/plugins/sitepress-multilingual-cms/inc/functions-load-tm.php(947): WPML_TM_Post_Actions->save_post_actions()n#5 /public/wp-includes/class-wp-hook.php(324): wpml_tm_save_post()n#6 /public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()n#7 /public/wp-includes/plugin.php(517): WP_Hook->do_action()n#8 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-translation.class.php(213): do_action()n#9 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-admin-post-actions.class.php(123): WPML_Post_Translation->after_save_post()n#10 /public/wp-includes/class-wp-hook.php(326): WPML_Admin_Post_Actions->save_post_actions()n#11 /public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()n#12 /public/wp-includes/plugin.php(517): WP_Hook->do_action()n#13 /public/wp-includes/post.php(5060): do_action()n#14 /public/wp-includes/post.php(5162): wp_insert_post()n#15 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-create-post-helper.class.php(42): wp_update_post()n#16 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-duplication.class.php(190): WPML_Create_Post_Helper->insert_post()n#17 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-duplication.class.php(91): WPML_Post_Duplication->save_duplicate()n#18 /public/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php(4554): WPML_Post_Duplication->make_duplicate()n#19 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-synchronization.class.php(94): SitePress->make_duplicate()n#20 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-translation.class.php(207): WPML_Post_Synchronization->sync_with_duplicates()n#21 /public/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-admin-post-actions.class.php(123): WPML_Post_Translation->after_save_post()n#22 /public/wp-includes/class-wp-hook.php(326): WPML_Admin_Post_Actions->save_post_actions()n#23 /public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()n#24 /public/wp-includes/plugin.php(517): WP_Hook->do_action()n#25 /public/wp-includes/post.php(5060): do_action()n#26 /public/wp-includes/post.php(5162): wp_insert_post()n#27 /public/wp-content/plugins/fusion-builder/shortcodes/fusion-global.php(209): wp_update_post()n#28 /public/wp-includes/class-wp-hook.php(324): FusionSC_Global->update_global_elements()n#29 /public/wp-includes/plugin.php(205): WP_Hook->apply_filters()n#30 /public/wp-includes/post.php(3052): apply_filters()n#31 /public/wp-includes/post.php(2845): sanitize_post_field()n#32 /public/wp-includes/post.php(4416): sanitize_post()n#33 /public/wp-includes/post.php(5162): wp_insert_post()n#34 /public/wp-admin/includes/post.php(453): wp_update_post()n#35 /public/wp-admin/post.php(227): edit_post()n#36 {main}n thrown in /public/wp-content/plugins/sitepress-multilingual-cms/classes/records/class-wpml-tm-icl-translations.php on line 193 Questions: Why am I getting a PHP Fatal error when trying to save a translated page? How can I resolve the 'No translation entry found' error?
November 29, 2024 at 11:30 am #16459114
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hi, Thank you for contacting the support. From the error log, I'd like to inform you that a similar issue has been reported previously and in that case, the issue was happening due to Creating the Translation of Global Avada Library Element by Duplicating it. From the WPML Debug Information, I found that you're using the Avada theme as well. Consequently, the underlying cause of your issue may be the same. Could you please try the steps below and see if they resolve the issue? - Navigate to "Avada > Library" in your dashboard. - Identify the Library Elements designated as Global. - Access the translations for these Global Library Elements and ensure they have been translated independently. For guidance on translating items independently, please refer to the following article: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/#:~:text=Translate%20independently. By following these instructions, you may be able to rectify the issue. But, if the issue persists, please let me know the steps to recreate the issue. I will check accordingly and let you know what to do next. Regards.
December 5, 2024 at 9:27 am #16480421
Dimitri	I've translated the global elements in Avada and it solved my issue. Thank you