[Resolved] "wpml_sl_blacklist_requests" filter fails if the URL contains escaped characters that are encoded in Unicode

For some reason, I can't get WPML to substitute links to translated content in the Sandbox (without that, changing functions and trying anything else is pointless). I have created the "Test 7" page. There are three links on it. The first one leads to another page I created in French ("page nᵒ 7). The second one leads to an English translation of this page (" I created the translation"). The third leads to another page in French, "page 7". This page is also translated into English. I have created a translation of the "Test 7" page. I expect that WPML should change the links on the translated "Test 7" page to English ones, i.e. change the links to the French pages (the first and third links) to English ones (since these pages are translated to English). However, WPML does not do this. Translate Link Targets doesn't detect any links that should have been adjusted. I'm probably doing something wrong. Somewhere something is not enabled, not activated.

Nope, I didn't do the translations of the URLs in ATE. For some reason ATE did those translations itself. That is, for some reason it "registered" the URLs as requiring translation and inserted those translations. Yes, that's the real thing. I don't see this behaviour of ATE on my site. As for the page you added, I see that you added it via Gutenber-editor (or what is it called?) in the format href="/?page_id=114. I don't use that format in principle. All my links are full and absolute. And I absolutely do not use Gutenber-editor.

Actually, I was able to get blacklist to work on my site

The problem was caused by the fact that WPML was actually substituting fragments from the old translation into the new translation, which - as it happened - differed only in what the URL was. So it felt like the new translation was being processed incorrectly. When I was able to solve the problem with WPML substituting a fragment from the old translation instead of the new translation, everything was resolved, because the blacklist itself works correctly. In other words, there is a problem, but it's not what this ticket is about. So I'm closing it, thank you!

By the way, I noticed that now WPML on my site has started _in some cases_ registering the URL for mandatory translation (and inserting the translation) if it's a blacklisted URL. This didn't happen before. Now it does. This is some kind of change. However, this is not always the case. I.e. when translating the same page into different languages in ATE, the URL may or may not appear in ATE as a URL to be translated (already automatically substituted into the translation).