There is a site where only the users in the editor or admin role can post new content. I have a registration (xy user) which is in the editor role, but I usually write posts logged in as uid 1 (the superuser), and change the author name to "xy user" - my other registration. The result: xy user is displayed as "not authorized" author.
I think it is OK when unregistered visitor who can post content signed as "not authorized", but I think author name, modified by uid 1 should not be signed as "not authorized".
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | realname-466764-8.patch | 1.41 KB | gapple |
| #8 | realname-466764-8.patch | 1.45 KB | gapple |
Comments
Comment #1
thamasIt must be the problem of the theme, 'cause I have no this problem when I use an other theme...
Comment #2
tobedeleted commentedI'm seeing a similar issue. I have a block created via Views that displays a username (and a photo and post title). When I'm logged in the username displays fine, when I'm not logged in the username displays with "(not verified)" immediately after it. Not sure what this is about. The user is clearly a registered site user so why does it suggest that the user is in some way not verified?
Comment #3
thamas(Corrected my wrong translation of my problem in the title. Sorry for the mistake!)
Hmm, now I think it is not a problem of the theme. I use RealName which have an option »Show "Not verified" for anonymous users«. Maybe I misunderstanded the use of it and checked. Removeing the check from this option solved my problem.
Comment #4
thamasComment #6
jmlane commentedReopening this issue as I have just reproduced it in 6.x-1.3. Changing issue title to something a bit more clear and descriptive of the issue at hand.
Going to check out latest development release shortly to see if the bug still exists in there.
Comment #7
nancydru"Not verified" is something core does. RealName, trying to be nice to core, does the same by default. However, if you go to the settings page, you can un-check the box to use that feature.
Comment #8
gappleSteps to reproduce:
1. Grant 'use realname' permission to only authenticated users
2. Create a node as an authenticated user
3. view node as authenticated user: Realname is displayed if available, or username if not
4. view node as anonymous user: username is displayed, with "(not verified)" appended
The logic flow in core is
- If the themed object has a uid and a name, output the name
- If no uid but has a name, output name with "(not verified)" appended
- If no uid or name, output "anonymous"
The current logic in realname is
- If a uid and realname is available, output the realname
- If a name is available, output with '(not verified)' appended
- If no uid or name, output 'anonymous'
The realname property is only added to the object passed to the
realname_username()function if the user has the 'use realname' permission, and it seems that most always the realname property is not already present in the object. As a result, when the viewing user doesn't have the 'use realname' permission the code execution falls through to the second condition intended for theming anonymous visitor's names and appends '(not verified)' when it shouldn't.The attached patch more closely matches the core logic for theming, attempting to use the realname if the user has the correct permission and safely falling back to the username.
Comment #9
deepakgoyal commentedyup it does solve my problem .. i had problem with realname
Comment #11
gappleHere's a UNIX line ending patch for testbot.
@deepakgoyal
Is that a vote for RTBC status then?
Comment #13
gappleIt looks like this issue was fixed as part of http://drupal.org/cvs?commit=444240, though not indicated in the commit message.
Seems to work correctly on my system.