We are opening this new request because we have identified a similar issue across multiple of our websites.
The problem occurs sporadically and without a clear pattern. Previously configured translation users suddenly no longer appear correctly in the Translators section. Upon investigating the database, we found that affected editor users are missing from the option wpml-cache-translators-translate.
As soon as this option is manually deleted, the translators reappear correctly.
Due to the lack of reproducible steps, this is difficult for us to debug on our side. However, the impact is quite significant, as it affects a large number of our sites and, consequently, our clients — preventing proper access to translations.
As a temporary workaround, we have implemented a small helper plugin that deletes this database option once upon activation. However, this is not a sustainable or permanent solution for us.
We would kindly ask you to further investigate this issue and help us identify the root cause, as well as provide a long-term fix.
Thank you very much for your support!
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Madrid (GMT+02:00)
I would like to request temporary access (wp-admin and FTP) to your staging site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
**IMPORTANT**
- Please make a backup of the site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.
The private box looks like this: hidden link
Hi there, unfortunately, we don’t have any specific steps to reliably reproduce the issue. We actually only discovered it by chance.
What we have found so far is that the problem seems to be caused by a corrupted WPML cache. Deleting the wpml-cache-translators-translate option once from the database appears to resolve it, at least temporarily.
Aside from that, we haven’t been able to identify any further details yet.
I’ve checked this internally with our second-tier team, and at the moment we haven’t been able to identify a clear cause for this behavior. Since the issue occurs intermittently and there are no reliable steps to reproduce it, it makes it difficult to properly investigate and determine the root cause.
For now, the recommended workaround is to delete the wpml-cache-translators-translate option from the database, which appears to resolve the issue.
Thanks for getting back to me and for checking this internally, I appreciate the effort.
I understand that the workaround helps for now, but I wanted to ask if the issue is still being actively investigated. While deleting the wpml-cache-translators-translate option does resolve it temporarily, it unfortunately doesn’t address the underlying problem.
My concern is that if the issue occurs again, we’ll still be in the same situation without a reliable way to reproduce it, which makes long-term stability a bit uncertain.
It would be great to know if there are any plans to continue digging into this, or if there’s anything we can do on our side to help capture more useful data when it happens again.
I’ve checked this internally with our second-tier team, and at the moment we don’t have much additional information to share. This behavior has not been reported before and seems to be specific to your site. Also, we currently don’t have clear steps to reliably reproduce the issue.
To better understand it, could you please let me know:
Have you noticed if this happens after a specific action? For example, after adding a new translator, does one of the existing ones disappear?
As a next step, we can perform a more advanced check. We can provide a small code snippet that you can temporarily add to your site. This code will “listen” for changes to the cache option, and when a change occurs, it will log a call stack in the debug.log. This should help us identify what is triggering the change.
Please let me know if you’d be happy to proceed with this, and I’ll prepare the code for you
I will investigate whether this behavior can be linked to a specific action. I will also discuss this with my colleague and give you a feedback by Friday.
Best regards
The topic ‘[Closed] Issue with translators not appearing in Translation Management / WPML cache inconsistency’ is closed to new replies.
