Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

Tagged: 

This topic contains 57 replies, has 3 voices.

Last updated by Andreas W. 1 month ago.

Assisted by: Andreas W..

Author Posts
September 19, 2024 at 1:02 pm #16198899

coinQ

Hello Andreas,

Thank you for your response and for the detailed recommendation.

Currently, we are not using any specific templates for categories and tags. We use archive.php as a common template for all the taxonomies on the website. I would like to get your opinion on using a common tag template (tag.php) instead of a "tag-slug.php" template for a specific term. We chose a common archive template because the design is similar for all listing pages.

If you think creating a common tag template (tag.php) for all tags would be beneficial, we are open to proceeding in that direction. However, creating separate tag-archive templates for each individual tag is not feasible since we have more than 500 tags in English alone. Could you please share your thoughts on this approach?

In the meantime, we will look into implementing the tag.php template and observe the results.

Looking forward to your feedback.

Best regards,
Vimal Roy

September 19, 2024 at 11:37 pm #16200932

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello Vimal,

Thank you for your answer!

I believe a common tag template would be ideal for testing. If all templates are identical, then there should be no need to create specific templates for each tag.

I really hope that this suggestion can solve the issue.

Let us know if further assistance is needed.

Best regards
Andreas

September 20, 2024 at 8:48 am #16201679

coinQ

Hello Andreas,

Thank you for your response and for confirming the approach.

We will proceed with implementing a common tag template (`tag.php`) and will monitor the results. I appreciate your suggestions, and I hope this resolves the issue as well.

In addition, I have noticed a 500 response in the access logs, and I investigated the issue further by checking both the Apache error log and Redis errors. Below are the relevant errors for your review:

Access Log:-
162.158.158.236 - - [19/Sep/2024:10:16:22 +0000] "GET /wp-json/wpml/tm/v1/ate/jobs/receive/45677 HTTP/1.1" 500 3243 "-" "rest-client/2.1.0 (linux-gnu x86_64) ruby/2.7.1p83"

Apache Error Log:-
[Thu Sep 19 10:26:24.914289 2024] [proxy_fcgi:error] [pid 3005015:tid 127717406148288] [client 172.70.110.220:27296] AH01071: Got error 'PHP message: PHP Warning: Undefined array key 0 in /var/www/html/wp-content/plugins/wpml-media-translation/classes/class-wpml-media-attachment-by-url-query.php on line 99;

Multiple similar warnings appear regarding undefined array keys in WPML Media Translation.

Additionally, I’ve attached the Redis error logs for your reference.

Could you please confirm if you've had a chance to check the Redis object cache issue that I mentioned earlier? It seems that we are facing problems due to too many requests from the WPML plugin, which is affecting the Redis object cache performance. If you need any further details or additional logs, feel free to let me know.

ISSUES :- hidden link

Best regards,
Vimal Roy

September 24, 2024 at 3:53 am #16212279

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

The debug.log of the provided Staging Site does currently not display such error.

The only significant error I see here is one pointing to Yoast Premium:

PHP Fatal error:  Uncaught TypeError: array_column(): Argument #1 ($array) must be of type array, string given in /var/www/html/wp-content/plugins/wordpress-seo-premium/src/integrations/third-party/wincher-keyphrases.php:83
Stack trace:
#0 /var/www/html/wp-content/plugins/wordpress-seo-premium/src/integrations/third-party/wincher-keyphrases.php(83): array_column()
#1 /var/www/html/wp-includes/class-wp-hook.php(324): Yoast\WP\SEO\Integrations\Third_Party\Wincher_Keyphrases->add_all_additional_keyphrases()
#2 /var/www/html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#3 /var/www/html/wp-content/plugins/wordpress-seo/src/actions/wincher/wincher-keyphrases-action.php(298): apply_filters()
#4 /var/www/html/wp-content/plugins/wordpress-seo/src/actions/wincher/wincher-keyphrases-action.php(192): Yoast\WP\SEO\Actions\Wincher\Wincher_Keyphrases_Action->collect_all_keyphrases()
#5 /var/www/html/wp-content/plugins/wordpress-seo/src/routes/wincher-route.php(262): Yoast\WP\SEO\Actions\Wincher\Wincher_Keyphrases_Action->get_tracked_keyphrases()
#6 /var/www/html/wp-includes/rest-api/class-wp-rest-server.php(1230): Yoast\WP\SEO\Routes\Wincher_Route->get_tracked_keyphrases()
#7 /var/www/html/wp-includes/rest-api/class-wp-rest-server.php(1063): WP_REST_Server->respond_to_request()
#8 /var/www/html/wp-includes/rest-api/class-wp-rest-server.php(439): WP_REST_Server->dispatch()
#9 /var/www/html/wp-includes/rest-api.php(420): WP_REST_Server->serve_request()
#10 /var/www/html/wp-includes/class-wp-hook.php(324): rest_api_loaded()
#11 /var/www/html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#12 /var/www/html/wp-includes/plugin.php(565): WP_Hook->do_action()
#13 /var/www/html/wp-includes/class-wp.php(418): do_action_ref_array()
#14 /var/www/html/wp-includes/class-wp.php(813): WP->parse_request()
#15 /var/www/html/wp-includes/functions.php(1336): WP->main()
#16 /var/www/html/wp-blog-header.php(16): wp()
#17 /var/www/html/index.php(17): require('...')
#18 {main}

Those errors were reported for the live site? If so, I would like to request access to the live site for investigating this further.

The private reply form is enabled.

Best regards
Andreas

September 25, 2024 at 1:44 pm #16220835

coinQ

Hello Andreas,

Thank you for your prompt response.

Regarding the Yoast Premium issue, we had encountered the same problem on our live website, which was resolved by disabling the Wincher integration, following the recommendation from the Yoast plugin support team. I have applied the same fix to the staging site, and I believe this should address the error you highlighted.

However, our primary concern relates to the Redis issues. We are experiencing challenges when using the WPML plugin in combination with the Redis Object Cache plugin. These issues have been affecting performance, and we've raised similar concerns in previous communications.

If further investigation is required, we can provide the latest Apache, Error, and Redis logs from the live website to assist in troubleshooting. Please let us know how you'd like to proceed and if any additional information is needed.

Best regards,
Vimal Roy

September 25, 2024 at 1:55 pm #16221003

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

It would be great to see these logs and I will further take another closer look to the staging site today.

Best regards
Andreas

September 27, 2024 at 5:24 am #16228055

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

My apologies for the delay in answering.

I enabled Redis Cache on the Staging yesterday and I would need some more details about, if you can currently see similar issues on the staging site and if so, where can I see them?

---

Regarding the slow query which we talked about earlier:

IMPORTANT:
I suggest again using a tag.php template and using a simplified query, designed to obtain the posts for each archive instead of a general query located on functions.php that servers for various purposes.

Would you agree if we give this a test on the staging site?

Example:
hidden link

Average Load time 1.0 seconds on first-page load including a slow query from WPML of 0.5 seconds.

This persists when testing only with the Custom Theme, Advanced Ads, ACF PRO and Redis Object Cache, WP Rocket, WPML and String Translation.

I can still confirm this slow query on the original and translated tag archives that sometimes occurs on the first-page load only or can occur persistently.

---

Revising WPML > Taxonomy Translation > Tags shows that not all tags have been translated and the taxonomy base "tag" was not translated. I suggest completing those translations.

I further have a question:
Is there a reason for having for example 1834 Korean tags on the site? Those seem to be original tags and they are not created in the site's default language.

If you create an original post in English, then it will make use of available categories and tags that were created in English. The translations of those posts will then use the translations of the categories and tags.

Or are you trying to use different tags on translated posts and not sync them between the original posts and their translations?

Please revise the list of tags at WPML > Taxonomy Translation > Tags.

Revise between pages 19-50. You will find many tags that are registered in languages other than the site's default language.

I would suggest cleaning those up and only using tags that are registered in the site's default language. The translated posts will use the translations of those tags automatically, once they are translated.

---

After cleaning up, I also suggest going to WPML > Support > Troubleshooting and running all available options to clean up the database and optimize WPML's tables.

September 30, 2024 at 11:50 am #16235981

coinQ

Hello Andreas,

Thank you for your detailed response and suggestions.

We will share the requested logs with you shortly to assist in your further investigation.

In the meantime, we will review and address the recommendations you provided, including the tag translation and cleanup in WPML, as well as testing a simplified query with the tag.php template on the staging site.

We appreciate your continued support and will keep you updated on our progress.

Best regards,
Vimal Roy

October 1, 2024 at 1:38 am #16238102

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Thank you, Vimal - I will be awaiting your feedback.

If you reply within the next 14 days, this ticket will remain open.

October 1, 2024 at 9:54 am #16239288

coinQ

Hello Andreas,

As promised, please find attached the latest Apache, Error, and Redis logs from the live site. These logs should provide more insight into the issues we've been facing with the Redis Object Cache when used alongside the WPML plugin, as well as when WPML is used on its own.

Logs :- hidden link

Please let us know if you need any additional information.

Thank you for your support.

Best regards,
Vimal Roy

October 1, 2024 at 2:26 pm #16241147

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Thank you very much! According to the Apache Error Log this looks like a media sync issue.

Please try to run a test without the plugin WPML Media Translation.

Then, run the dialog WPML > Settings > Media Translation > Start.

After that test again with WPML Media Translation and let me know if the issue persists.

October 8, 2024 at 12:40 pm #16265428

coinQ

Dear Support Team,

I hope this email finds you well. I would like to inform you that we are still working on the issues and appreciate your continued assistance. We are actively monitoring the situation and will update you with further details once we have more information or if we require additional support.

Thank you for your understanding, and we look forward to resolving this soon.

Best regards,
Vimal Roy

October 10, 2024 at 1:32 am #16272734

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hi Vimal,

I am running WPML > Settings > Media Translation > Start which will create the media entries for all the uploaded media. This is necessary to display the original media on all languages.

There are more than 200k entries that needed to be created, which means this could take various hours.

I will contact you tomorrow, once I will be able to continue testing.

Best regards
Andreas

October 11, 2024 at 2:10 am #16277348

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

The media appears to be synced now.

The website has around 30.000 images and 9 active languages. This makes 270.000 entries inside the media library (once for each language).

Could you please run a test on the staging site and let me know if you can still experience the issues regarding slow media queries?

Question:
Is the whole media really used on the website or would you consider to try to clean up the media library and remove media that is not in use on any of the posts or pages?

October 22, 2024 at 1:17 pm #16317607

coinQ

Hello Andreas,

Thank you for your continued testing and the update regarding the media synchronization.

Since we operate a news/blog website, it's common for us to upload images for every article, both as featured images and inline images. However, with 270,000 media entries across 9 languages, we are concerned that this might be an unusually large amount. Could such a large number of images affect website performance, or cause any other issues? We would appreciate your feedback on this.

Additionally, we upload only one image for each article, which is then duplicated across all languages. We don't require different images for each language version of the same article unless there’s a specific need. Is there a way to prevent automatic duplication of images across translations, and only upload different images when necessary? Ideally, we would like the same image used across all languages unless manually specified otherwise. Could you guide us on whether this can be managed through any settings or adjustments?

Looking forward to your feedback.

Best regards,
Vimal Roy

The topic ‘[Closed] Very slow queries’ is closed to new replies.