@Brett, I am coming from elgg v1.0. so will there be a solution for old elggers like us also regarding the dots in username?

@Tom -- Sorry...misread.  I'm not comfortable with rewriting the data on the fly and I don't think many Elgg administrators would be because it takes control from the admin running a single command to an unknown number of possibly anonymous users running an unknown number of commands.  The difference is that anonymous users won't realize there is an upgrade happening and might cancel or restart the request halfway through....Bad stuff...

@prem -- Looking at the old releases of Elgg is one of the things that made me think we should push the fix into 1.7.  The resolution will make it not matter what the login name is (though it will be restricted to alpha-numerics).

We still have this issue. Was thinking, would it be possible to execute this script one by one by just selecting a user? In that way it does not run for long time over the database. We simply enter a user name and the script moves the data of that user only. One by one, we can check if it works... You think we could rewrite the script if it cant do it now?

@Brett, I am coming from elgg v1.0. so will there be a solution for old elggers like us also regarding the dots in username?

@Tom -- Sorry...misread.  I'm not comfortable with rewriting the data on the fly and I don't think many Elgg administrators would be because it takes control from the admin running a single command to an unknown number of possibly anonymous users running an unknown number of commands.  The difference is that anonymous users won't realize there is an upgrade happening and might cancel or restart the request halfway through....Bad stuff...

@prem -- Looking at the old releases of Elgg is one of the things that made me think we should push the fix into 1.7.  The resolution will make it not matter what the login name is (though it will be restricted to alpha-numerics).

We still have this issue. Was thinking, would it be possible to execute this script one by one by just selecting a user? In that way it does not run for long time over the database. We simply enter a user name and the script moves the data of that user only. One by one, we can check if it works... You think we could rewrite the script if it cant do it now?