users with negative id numbers

Hi, Antonio. We've survived the move to the new server. I'm now dealing with an issue that I *think* may be older. It is showing up because we rebuilt the moodle side and not all of the users were transferred.

I have a number of users showing in joomdle who are in twice, once in moodle and joomdle with a negative id number, and once in joomla with a regular id number. I know you've seen this before. The Joomla username has a capital letter, the moodle username is all lowercase. Editing the Joomla username to be all lowercase resolves this.

These users do look like they are older. I'm not sure how many of them there are. Do you have any suggestions short of manually going through 4000+ users that will help me find them? Where in the table structure would I find that negative id number entry? I'm thinking if I could at least find them with SQL, I could manually fix the ones needing fixing much quicker. I'm guessing it is about 5% of the total? But that's a guess...

Any ideas?

don't know if this was the right solution, but it should fix it...

The negative numbers were all usernames that were lowercase: alice
Moodle would be using alice
Joomla would be using Alice
Joomdle would show both as if they were two separate users.

Updating the Joomla username would make them magically come into a line with no negative alice.

At first I queried the two databases and just changed the ones that matched. Then I realized that I'd continue to have the problem anytime any of our existing users signed up for a moodle class. So I changed everyone's username to lowercase and put a note on the login page.

I'm sure I have a number of frustrated users, but they should be less frustrated than the people who could not get into classes...

Hi Lisa. Sorry for the slow reply.

As you say, the problem is uppercase in usernames. In Moodle, you cannot use uppercase in username, so it gets converted to lower case.

> Then I realized that I'd continue to have the prooblem anytime any of our existing users signed up for a moodle class. So I changed everyone's username to lowercase and put a note on the login page.

There is a plugin for that: the Joomdle user check plugin will run on user registration, giving an error if you try to register using uppercase in username. You should install it and test it out.

I did find that plugin. I'm counting on it to prevent this from happening in the future.

Our current issue is that randomly it seems that PayPal confirmation is not coming through or is coming through delayed. Sigh. It is always something.

Good, hopefully it will prevent new problems.

As for Paypal: if the order is not being confirmed in shop, the problem is not related to Joomdle, and you will need to check with Paypal/your shop component support, sorry.

Hello Antonio
I have the same problem.
See the screenshot
What is the procedure to repair?
The users joomdle_connector and guest are important ?
beacause they also have the same problem
Thank you for your answer
Good to you
Raymi

Hi Raymi.

The procedure to repair is to change username to lowercase is Joomla backend.

> The users joomdle_connector and guest are important ?
These are not important, as they are not really "joomdle users"

Hello Antonio
When i try to change the username in joomla it puts me:
XML-RPC Error (23000021): Access Control Exception | ERRORCODE: accessexception

I do not understand because lower case names have the same problem.

And I have names in capital letters that go very well.

How to do ?

Thank you

Are you running latest Joomdle in both Joomla and Moodle?
You can enable debugging in Moodle to get more info about the error.

Yes i use joomla, moodle and joomdle.
I go through the joomla admin to try to change the user.
But there is the error message :
XML-RPC Error (23000021): Exception du contrôle d'accès | DEBUG INFO: Access to the function joomdle_change_username() is not allowed. There could be multiple reasons for this: 1. The service linked to the user token does not contain the function. 2. The service is user-restricted and the user is not listed. 3. The service is IP-restricted and the user IP is not listed. 4. The service is time-restricted and the time has expired. 5. The token is time-restricted and the time has expired. 6. The service requires a specific capability which the user does not have. 7. The function is called with username/password (no user token is sent) and none of the services has the function to allow the user. These settings can be found in Administration > Site administration > Plugins > Web services > External services and Manage tokens. | ERRORCODE: accessexception