When we implemented WPML back in 2022 the current developer back then unfortunately selected translate all in the believe that this could translated the site correctly. Today we all know that at that time there was many bugs in the software, and that string translation was not at the level where it is today.
We are facing several problems that I am relatively convinced is due to string translation.
1) We have a fundamental problem with cron jobs. Cron Jobs are getting duplicated (sometimes x2 sometimes x15 it appears to be quite random).
2) When we in Yoast SEO run the job called “SEO data optimization” then the wrong translation for English bradcrumb prefixes like eg home is picked.
3) The WCFM domain is constantly adding strings even though the “String auto registration” is disabled. (I’m aware that this can also be due to a bug in WCFM)
4) The Google crawler is finding some very strange urls. It looks like the word “product” is picked randomly from string translation.
I will check with Prakash (developer) what server you can use to investigate the issue. In the mean time please send me one of those messages where i can respond with the credentials.
I checked the internal ticket, but the password is not working. So I am enabling the private reply again. Please share them again. Just do it here and I will let the team know myself, you don't need to send this on every ticket.
Please also dont forget about the problem with the Glossary.
We are facing the issue that some database tables are running very big. According to ChatGPT some of it can be caused by WPML.
Please try and check this: hidden link
I have asked Bhavik to look into why some tables are running that big, but if you already know what can be causing this, then I’m sure he will be very happy to hear from you.
Thanks for the details. Those are working for me. I will now check issues.
About the glossary issue - I have sent you an update on email.
About the huge DB issue - I see Prosenjit's reply and optimization feature can be useful to reduce the size of WPML tables. You can give it a try just make sure you have the backup.
WPML keeps the history of jobs. This is true, optimization removes the history records and leaves only the required details. Please do not run the query ChatGPT suggested this can break things.
However, I wonder why we have wcfm_marketplace_store_taxonomies with 3 GB in size. Maybe you would consider asking this to their support.
Yes, we must do what it takes to solve the issues.
Just make sure that you don’t send mails to vendors or customers when you make a test environment on your local. This can actually be a bit tricky because e.g. payout specifications to vendors are generated by a monthly cron job.
FYI, Prakash know why the table wcfm_marketplace_store_taxonomies is grooving massive in size, and this is most likely not due to WPML.
