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.
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.
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.
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.
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.
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?
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?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Generally, when using WPML you should not upload images on translations.
WPML will display the original media on all translations and use the same file. To achive this WPML will created database entries to connect the original media with the translated contents.
If you upload media in second languages, then the WPML Media Sync will cause unnecessary DB entries for all languages and you will find duplicated files on the server, as you have uploaded them once for each language.
If you would like to use a different media in a second language, you can upload it at WPML > Media Translation.
As part of our regular process, we typically upload only one featured image along with inline images when creating an article. During translation, we generally only translate the content, and it is rare for us to change the featured or inline images in the translated articles. The same images are typically used across all translations unless there's a specific need to update them.
With that in mind, could you confirm if this process would lead to any unnecessary duplication of images or database entries? We're particularly concerned about whether following this approach might still cause issues with duplicated images across languages. We would appreciate your insights on this.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello Vimal,
Your approach is correct.
Example:
1) Create a post and add media to it
2) Translate the post
WPML by default will create one database entry for each media file in each language. This will create an entry inside the media library for each language.
This means, while on the media library, when changing the admin language inside the top bar, you should see the same amount of images and you should be abl eto edit the meta information in each language.
At the same time, the duplication of media will allow to access the media when editing a post in a second language.
WPML will not duplicate the physical media files, it will only create database entries.
This means, if you have 30.000 images (files) and 9 active languages you will have 270.000 entries inside the media library (once for each language).
I further wanted to ask if you tested to adjust the archive templates by using a post query dedicated for the specific template?
Best regards
Andreas
The topic ‘[Closed] Very slow queries’ is closed to new replies.
