About: terimbo

Hi Bruce,

Yes, I’m aware of how to do it — if you’ve had a look, you’ll know that the post I mentioned and the post you mentioned are talking about the exact same technique.

However, what I am saying is that it appears that the relevant bits of JavaScript responsible for the “oops” message are not being translated at all.

In case you still don’t believe me, let me spell it out further…

The relevant JavaScript for the user profile form is delivered by /s2member/s2member-o.php. Visit the user profile page, look in the page headers, and grab the exact URL being used to retrieve the JS via s2member-o.php for that specific page. (There are two references to that file, one for CSS and one for JS; you want the JS.) Paste that URL into your browser’s address bar and look at the code which is returned: “oops” is everywhere. Now if you think that the filtering technique is doing anything whatsoever when this JS is being retrieved, just place a big fat die() right at the start of the function you’re doing the gettext_with_context filtering with: that will stop WordPress dead in its tracks the moment it reaches that code. But guess what? WordPress does not stop dead in its tracks, because the relevant code is never being executed.

Note that when s2member-o.php is called directly, no WordPress code is even executing; there are no filters, no plugins, no nothing, because WordPress is not running. The file s2member-o.php chooses which bits of WordPress to fire up when it starts executing.

So, as I said in the original post, it appears that the relevant bits of JavaScript responsible for the “oops” message are not being translated at all.

• This reply was modified 3 years, 11 months ago by  terimbo.