www programming

Yes, I agree with you, it seems to me that this is the only way to solve this problem

The unique (not unique in true) way to resolve this, is to add the user into wordpress, if it contain unwanted chars, purged of these chars.
All will work as ever. Anyway, it need to be considered several problems running integration like these (with usernames not matching):
a purged user in Wp, could match an existent username. Rare? Could happen.
It can be not very hard to be resolved, providing just a switch to add random chars where the username already exist in wp.

By the way, think in 2.4.5:
all the part about user's transfer and check will be rewrite from scratch. It work, but is a big mess i want to see perfect instead (also the logic and code within is crazy, even if it work) and useful for anyone to get a general idea of the user's state, so to fix problems in short and with easy.

into 2.4.4 i've found several fixes to apply and parts of not useful code have been removed.

So i will try to rewrite the entire plugin from scratch quite soon!
As ready, we'll jump to 3.0.0!

I don't understand what the problem is, everything works fine for me

So i just installed a multisite test and try to register an user, where users can register a new username account, but also a site.
I can confirm that the WP answer is this if i try to register an username like test . me
the answer is:

Usernames can only contain lowercase letters (a-z) and numbers.

and this is it for any setup, that can be into a wp multisite:

Registration is disabled
User accounts may be registered
Logged in users may register new sites
Both sites and user accounts can be registered

then i assume the code behavior is correct this way.

But since the integration works by email now, we can easily switch the code to be added as
testme
when it is
test . me in phpBB and wp is a multisite install.
2.4.5 is coming

Hello guys, as said into previous post i'm over for the 2.4.5 release.
Just installed a test wp mums, so that this issue will be soon fixed (or almost we'll go to see what was going wrong about this).

I've successfully applied patch as described above.