Regarding the CRON jobs issue
I checked how CRON jobs are stored, and they are not registered as a post type or taxonomy. They are stored directly as database entries. Because of this, WPML post type settings should not affect them.
After checking further, I found that this is an issue in Action Scheduler itself. Please refer to the following issue for more details: hidden link
Regarding the Yoast issue
Please allow me some more time to debug this issue. I am still investigating it.
The WCFM domain is constantly adding strings
This looks like WPML’s normal behavior. I am running more tests to gather additional details and will update you once I have more information.
The Google crawler is finding some very strange URLs
I noticed that the post type base slug is incorrect in those URLs, while the product slug itself is correct. I checked the original product pages but could not find any 404 URLs on the site.
I am not sure how Google discovered these URLs if they do not exist on the site. Could you please share the sitemap URLs that you have submitted to Google? It is possible that something is wrong in the sitemaps.
Hi Sumit
1) CRON jobs issue
I have forwarded your message to Prakash who will check the github you send.
I noticed that some admin text (e.g. “action created”) has been translated, and that the translations appears to be randomly displayed. See attached screen shot made from the English language. Are you sure this is not causing an issue?
There is no reason to translate all this admin texts. How can we have this fixed?
2) Yoast bread crump issue
I wrote a separate mail to you and Prakash about this. Any news?
It’s important to have this fixed relatively fast on production, as it right now is displaying “Home” in a wrong language.
3) WCFM domain is constantly adding strings
It might easily be that you are right that this is caused by WPML. In that case it would be good if WPML can help contacting them and instruct WCFM how to fix the issue.
4) Google crawler is finding some very strange URLs
I found something that might cause this issue (not 100% sure if this is the reason). I have already described my findings in a mail to Prakash. I will forward this mail to you.
5) Big database tables.
Prakash tried to run the job you suggested, but it did not seam to fix the issue. Please see his mail from 16 Feb.
Best regards
Peter
New threads created by Sumit Singh and linked to this one are listed below:
I am investigating all the issues one by one. Since issues are increasing so I am splitting one issue per ticket, and I will update you on them. This helps us to track things easily and keep records of recurring issues and solutions.
You don't need to open a new ticket for any future issue; you can add it here, and I will split it.
