That's an automated email that is sent after a few days. As long as you reply to it to keep the thread open, I'll reply mark this as awaiting your reply, and we can keep doing that as long as is needed.
Thanks. So far, I find it hard to conclude anything. I installed a free limited logger. Some logged events match (roughly) with the timestamps of the warning in the WordPress log file.
Here's an example:
9 May 2023 8:45:03.000, System, <IP>, Published the post Günstige Hotels. Post ID: 368298 Post type: page Post status: published
9 May 2023 8:45:03.000, System, <IP>, Created the new custom field rank_math_internal_links_processed in the post Günstige Hotels.
9 May 2023 8:45:03.000, System, <IP>, Created the new custom field content_next_update in the post Günstige Hotels.
I am guessing that might be our remote translator doing work in the WPML Advanced Translation Editor. So, the user is called "System" instead of the name we gave the translator. The IP address is not his but in the USA for the ones I checked (a WPML server perhaps).
We're not getting any errors during our work, apart from the issues with translating links, which are reported in other support tickets.
Did you find anything on your end? If you did not test a remote translator via the Advanced Translation Editor yet, it might be worth a try.
I've gathered together all of the details and escalated this so my colleagues can investigate further, now that we have the steps and conditions to reproduce.
I'll update you when I have some feedback from them.
So I'm pleased to say that the specific cause has been located, and it has been passed to the developers to update our code with a fix.
In the meantime, if you need a workaround you can edit the file plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Relation.php and change line 31 from
return strcmp( $a, $b ) < 0;
to
return (int) (strcmp( $a, $b ) < 0);
I think we can probably close here? The change will be included in an upcoming release. If it doesn't make it into the next version—which is pre-release testing—then you would need to re-apply the change.
