I'm guessing this is the dumbest question in the world for this module, as it seems like this would be a module-killer right out of the gate -- but I can't find the answer through copious searches.
I have RealName installed, and is shows the FirstName LastName values from the User fields I created everywhere I expect it to -- which is great. However, when I go to many of the autocomplete fields to enter a user name, entering a user name automatically pops up a list of the RealNames for the users instead. Then it inserts the RealName I select in the user field (with no username in parentheses). When I click save, it says there is no such user -- since it is just popping in proper nouns that are not the username data.
I have seen this in a number of critical places -- like in the To field of PrivateMsgs and in other user fields I've created for users to assign themselves to events and tasks etc… These are places where regular, non-informed, non-admin users need to enter the info and are completely confused by this and brought to a halt. (At least admins like me can manually enter the real username.)
I have seen a few fields where when you enter the user field, the RealName pops us with the username following it in parentheses. When this version occurs, Drupal accepts the submission and recognizes the user chosen.
How can RealName work if it's going to universally insert itself but not do so universally in a way that sends the correct username data to Drupal?
I hope someone can help soon, b/c this is pissing off our users!
Comments
Comment #1
dave reidAre the times that these fail are they entity or user reference fields? Is there any way you can list the steps to reproduce this error using just core + RealName + minimal other contrib modules?
Comment #2
somatics commentedWell, I can't strip the modules out or create a test instance right now, but here are the additional symptoms I'm seeing so far:
Using PrivateMsg…
...entering the To field and starting to type will pull up a list of users' RealNames, for example "Luke Skywalker". When you select it, it shows "Luke Skywalker" (no quotes) in the To field. If you submit the form, it brings you back to it unsubmitted, with the error message:
And that's as far as you can get with this form.
Using a content type
…entering a field of type User reference with the widget type Autocomplete text field, and starting to typewill pull up a list of users' RealNames. When you select the name, what appears in the field is the username and uid in brackets, e.g., "luke.skywalker [uid:651]".
In this case, when you submit the form, it does save properly, including the user reference. So, this works, even though it behaves differently than the ones that show "RealName (username)".
But what does this mean for the PrivateMsg To field?
Comment #3
dave reidI think the problems all seem to be caused by PrivateMsg then? It looks like there are some existing issues related to user reference and validation:
#1751252: Users with spaces in the username not accepted as valid recipients
#1694558: Autocomplete breaks user names with apostrophes
#1852746: In the field "To" automatically appears [user]
#1903786: Failed to check Unique name when Realname Integration is enabled
The issue with a user reference field not displaying the real name once you've made a selection is a duplicate issue of:
#1194086: Real Name not working for user references
#1885380: Real Realname Support
I would suggest you follow the above issues and potentially help test any patches in those modules to see if they resolve the bug for you.