Skip Navigation

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

Problem:
The client was experiencing 404 errors on the .de domain for pages that should have been German translations, an error message within the WPML plugin dashboard, and slow site performance. Additionally, there was an issue with the WPML Translation Editor where some products did not automatically update and required manual updating.

Solution:
1. For the 404 errors, we found that the shop base was incorrectly set. We corrected it by setting the shop base to "storede/%product_cat%" in WooCommerce > WooCommerce Multilingual > Store URLs -> product base.

2. To address the fatal error, we requested the complete error log from the client. Upon review, we identified incorrect records in the "icl_string_packages" table and a missing Auto-Increment setting for the ID column. We fixed these issues by removing the faulty entries and enabling Auto-Increment for the ID column.

3. Regarding the Translation Editor issue, we discovered that the WPML setting "When you publish the original post" under "Translated Documents Option" was set to "Do not publish the post translations". We advised the client to change this setting to "Publish the post translations" to ensure that translated products are published automatically.

If these solutions do not resolve your issues or if they seem outdated or irrelevant to your case, we recommend opening a new support ticket. We also highly recommend checking related 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.

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: 

This topic contains 9 replies, has 3 voices.

Last updated by Prosenjit Barman 1 year, 4 months ago.

Assisted by: Prosenjit Barman.

Author Posts
February 23, 2024 at 2:04 pm #15338164

ninaK-13

Dear WPML Support Team,

again problems with WPML - i hope soon we resolve it because i can't work normaly 🙁

I am submitting this task report to address critical issues we're experiencing with our website, specifically related to the WPML plugin and the performance on our .de domain, which is designated for German translations. The core problems include widespread 404 errors for translated pages and significantly slow site loading times, presumably due to the system attempting to access the aforementioned unavailable pages.

hidden link
hidden link (this is translated but nothing- have many, many like this)

Issue Summary:

404 Errors on .de Domain: All pages intended to be German translations on the .de domain are currently returning 404 errors. This issue suggests a malfunction in the language translation delivery or URL rewriting mechanism, preventing users from accessing the German version of the site.

WPML Plugin Error Message: We are consistently receiving an error message within the WPML plugin dashboard stating, "WPML can't run normally. There is an installation or server configuration problem," accompanied by "AJAX Error: error [503]." This error points towards a potential problem with the WPML installation or a conflict with our server configuration.

Slow Site Performance: The site's performance, particularly the initial loading time, has degraded significantly. It appears the system is persistently trying to load the inaccessible translated pages on the .de domain, contributing to the slowdown. i buyed the best hosting solution with purchase WPML..

all wordpress work very slow 🙁

Thank you for your cooperation and support.

February 24, 2024 at 11:02 am #15340205

ninaK-13

hidden link
#23 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php(1316): TranslationManagement->send_jobs()
#24 /home/selenafa/public_html/wp-includes/class-wp-hook.php(324): TranslationManagement->action_send_jobs()
#25 /home/selenafa/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#26 /home/selenafa/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#27 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/API/Batch.php(40): do_action()
#28 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/API/Batch.php(56): WPML\TM\API\Batch::WPML\TM\API\{closure}()
#29 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/API/Batch.php(44): WPML\TM\API\Batch::send()
#30 [internal function]: WPML\TM\API\Batch::sendPosts()
#31 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php(100): call_user_func_array()
#32 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/translation-jobs/Dispatch/Elements.php(49): WPML\FP\{closure}()
#33 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/translation-jobs/Dispatch/Posts.php(19): WPML\TM\Jobs\Dispatch\Elements::dispatch()
#34 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php(498): WPML\TM\Jobs\Dispatch\Posts::dispatch()
#35 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php(295): TranslationManagement->process_request()
#36 /home/selenafa/public_html/wp-includes/class-wp-hook.php(324): TranslationManagement->wp_loaded()
#37 /home/selenafa/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#38 /home/selenafa/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#39 /home/selenafa/public_html/wp-settings.php(665): do_action()
#40 /home/selenafa/public_html/wp-config.php(101): require_once('/home/selenafa/...')
#41 /home/selenafa/public_html/wp-load.php(50): require_once('/home/selenafa/...')
#42 /home/selenafa/public_html/wp-admin/admin.php(34): require_once('/home/selenafa/...')
#43 {main}
thrown

February 26, 2024 at 7:33 am #15342435

George Botsev
WPML Supporter since 02/2014

Languages: English (English )

Timezone: Europe/Sofia (GMT+03:00)

Hello and thank you for contacting us.
I am sorry that you are experiencing problems with our plugin.
It appears that the error stack trace that you provided is cut short and cannot help us entirely to determine the cause of the issue.

Could you please provide a more complete error trace?
You can use a service like pastebin to provide a secured (password protected if you wish) pastebin so that we can check it more completely.

Additionally, it would help if we have a temporary access to your site.

February 26, 2024 at 8:25 am #15342651

George Botsev
WPML Supporter since 02/2014

Languages: English (English )

Timezone: Europe/Sofia (GMT+03:00)

About the 404 error, I see that you've set the shop base as "porachka/%product_cat%" while you translated it to German as "storede" and this is the issue. It should be set to "storede/%product_cat%" (This is done in WooCommerce > WooCommerce Multilingual > Store URLS -> product base )
I fixed that for you.

I am not entirely sure how to reproduce the issue that lead you to the fatal error.
Can you provide the error log in its entirety, please?

February 26, 2024 at 8:50 am #15342767

ninaK-13

Thank you - i hope soon i can work normal

WordPress версия 6.4.3
Текуща тема: Woodmart Child (версия 1.0.0)
Текущо разширение: WPML Multilingual CMS (версия 4.6.9)
PHP версия 8.0.24

this is where the fatal errors:
this happens when a page/post translation is set from the plus

Първо посетете уебсайта си (hidden link) и проверете за видими проблеми. След това посетете страницата, където е открита грешката (hidden link), и проверете за видими проблеми.

Данни за грешката
================================
Грешка от вид E_ERROR беше причинена от ред 156 от файла /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Fns.php. Грешка: Uncaught InvalidArgumentException: target should be an object with map method or an array in /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Fns.php:156
Stack trace:
#0 [internal function]: WPML\FP\Fns::WPML\FP\{closure}()
#1 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php(154): call_user_func_array()
#2 [internal function]: WPML\FP\Fns::WPML\FP\{closure}()
#3 /home/selenafa/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/colle ct/src/Illuminate/Support/ Traits/Macroable.php(56): call_user_func_array()
#4 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms /vendor/wpml/fp/ core/Lst.php(104): WPML\FP\Fns::__callStatic()
#5 [вътрешна функция]: WPML\FP\Lst::WPML\FP\{closure} ()
# 6 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/vendor/wpml/fp/ core/functions.php(154): call_user_func_array()
#7 [вътрешна функция]: WPML\FP\ {closure}()
#8 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/vendor/wpml/fp/ core/functions.php(50): call_user_func_array()
#9 [вътрешна функция ]: WPML\FP\{closure}()
#10 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/vendor/wpml/fp/ core/Fns.php(164): array_map( )
#11 [вътрешна функция]: WPML\FP\Fns::WPML\FP\{closure} ()
#12 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/vendor/wpml/ fp/ core/functions.php(154): call_user_func_array()
#13 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/vendor/wpml/fp/ core/Maybe.php(106) : WPML\FP\{closure}()
#14 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/addons/wpml-page- builders/classes/Shared/AutoUp date/Hooks.php (82): WPML\FP\Just->map() #
15 /home/selenafa/public_html/wp-includes/class-wp-hook.php(324 ): WPML\PB\AutoUpdate\Hooks->getM d5ContentFromPackageStrings( ) #16 /home/selenafa/public_html/wp-includes/plugin.php(205 ): WP_Hook->apply_filters() #17 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/inc /actions/wpml- tm-action-helper.class.php(60) : apply_filters() #18 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/inc/wpml-private- филтри .php(11): WPML_TM_Action_Helper->post_md 5() #19 /home/selenafa/public_html/wp-includes/class-wp-hook.php(324) : wpml_tm_element_md5() #20 /home/selenafa/public_html/wp - включва/plugin.php(205): WP_Hook->apply_filters() #21 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/inc/translation- management/translation- management.class. php(1068): apply_filters() #22 /home/selenafa/public_html/wp-

content/plugins/sitepress-mult ilingual-cms/inc/translation- management/translation- management.class.php(1362): TranslationManagement->post_md 5()
#23 /home/selenafa/public_html/wp- content/plugins/ sitepress-multi ilingual-cms/classes/class- wpml-translation-job-factory. php(112): TranslationManagement->send_jo bs()
#24 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/classes/jobs/Manu al.php(164): WPML_Translation_Job_Factory-> create_local_job ()
#25 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/classes/jobs/Manu al.php(43): WPML\TM\Jobs\Manual->createLoc alJob()
# 26 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/vendor/wpml/fp/ core/Either.php(207): WPML\TM\Jobs\Manual->createOrR euse()
# 27 /home/selenafa/public_html/wp- content/plugins/sitepress-mult ilingual-cms/classes/editor/ Editor.php(92): WPML\FP\Right->map()
#28 /home/selenafa/public_html /wp- content/plugins/sitepress-mult ilingual-cms/classes/menu/translation -queue/class-wpml-translations -queue.php(52): WPML\TM\Editor\Editor->open()
# 29 /home/selenafa/public_html/wp-includes/class-wp-hook.php(324 ): WPML_Translations_Queue->load( ) # 30 /home/selenafa/public_html/wp-includes/class-wp-hook.php ( 348 Серия _ _ _ _ class-wp-screen .php(424): do_action() #33 /home/selenafa/public_html/wp- admin/includes/screen.php(243) : WP_Screen->set_current_screen( ) #34 /home/selenafa/public_html /wp- admin/admin.php(212): set_current_screen() #35 {main} хвърлен

February 26, 2024 at 9:17 am #15342925

George Botsev
WPML Supporter since 02/2014

Languages: English (English )

Timezone: Europe/Sofia (GMT+03:00)

I just tried to click on the plus, for one of the products that you attempted to translate, and it seems to have correctly opened the Advanced Translation Editor for me with no error.

Perhaps I am missing a step on the way of how this could be properly reproduced?
Could you perhaps record a screencast showing the issue on your end?

One of my colleagues will continue with you.

February 26, 2024 at 9:43 am #15343221

ninaK-13

sure
hidden link

February 27, 2024 at 10:13 am #15348356

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hello There,
I hope you're doing well. I've taken over this ticket and would be happy to assist you further in this matter.

The Drive link you've shared is protected. Therefore, I couldn't check the steps you've shared.

However, by examining the debug log, which included the link where the Fatal error occurred, I was able to pinpoint the root cause. The issue stemmed from incorrect records in the "icl_string_packages" table of the Database, as well as the Auto-Increment setting for the ID column that was missing in that table. By removing the faulty entries and enabling Auto-Increment for the ID column, I successfully resolved the problem.

The Fatal error mainly occurred at the time of translating the "Custom-404" page into English. Now, the Editor loaded properly(Screenshot: hidden link) when I tried to add an English translation, and hopefully, the Fatal error will not occur again.

If there is anything else if you need help with, please let me know. I will be happy to help.

Best regards,
Prosenjit

February 27, 2024 at 3:10 pm #15349693

ninaK-13

Hello,

Thank you for your prompt response and support. I hope I won't have a reason to create more tickets in the future. However, I've encountered an issue with the WPML Translation Editor. It seems that some of the products do not automatically update through the editor and require manual updating. Here is an example of a specific product:

Original product: hidden link

Translated product: hidden link
hidden link

I hope that once we translate the majority of the content, it will start to perform faster and will not search for missing pages.

Could you please provide a solution for this issue or direct me to the appropriate resources for resolving the product update problem?

Thank you in advance for your help.

February 28, 2024 at 5:01 am #15351798

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hello There,
Thank you for the feedback.

I've checked and understood that the translated products are not being published automatically. While checking the WPML Settings, I found that the option "When you publish the original post" found under "Translated Documents Option" is configured as "Do not publish the post translations"(Screenshot: hidden link). This is why, the Translated posts/products aren't getting published accordingly.

To automatically publish the translated post along with the product, please set the setting to "Publish the post translations". Next time, the automatically translated product will be published automatically.

Please let me know if that helps or if you need further assistance in this matter. I will be happy to help.

Best regards,
Prosenjit

February 28, 2024 at 5:32 am #15351808

ninaK-13

Dear Support Team,

I want to extend my heartfelt thanks for the exceptional support you've provided. Your prompt and effective responses have not only resolved my issues but also significantly improved my experience.

I sincerely hope that the need for opening new tickets will be minimal moving forward, thanks to the solutions and guidance you've offered. Your dedication to resolving my concerns has been truly appreciated.

Thank you once again for your outstanding support.