Posted by coltrane on March 7, 2009 at 8:03pm
| Project: | Drupal core |
| Version: | 7.x-dev |
| Component: | node system |
| Category: | task |
| Priority: | normal |
| Assigned: | cwgordon7 |
| Status: | closed (fixed) |
| Issue tags: | Needs text review, UBUserTesting2009, ui-text, Usability |
Issue Summary
Identified at UB Usability Testing: http://www.drupalusability.org/node/115
On admin/content/node when there are no nodes "No posts availiable" is displayed. "posts" in this context is ambiguous.
Comments
#1
#361277: Remove the 'post settings' admin screen and relocate contents relates
#2
Maybe this would be a good place to put a link to Create Content as well. "There is no content available. Create content"
#3
tagging
#4
Patch and screenshot attached. :)
#5
Cross-posted, sorry.
#6
So what is the situation, when there is content? Does this function disappear? Although it sounds obvious to add a create content link here, we probably need to do it somewhere else then in that table. Just re-roll it with just the "content" tweak and focus on the other overlaying issue (expecting to create content in /admmin/content/node) in a different issue.
http://drupal.org/node/394702
#7
Here's a patch with just the text changes.
#8
Patch is good, tests pass, rtbc.
#9
Hm. Looks like everywhere else we do "No X available":
No books available.
No comments available.
No terms available.
No vocabularies available.
So probably just "No content available."
#10
Well, that was the problem in the first place - why isn't any content available?!? It's not available because it hasn't been created yet, and that's the message we need to convey. "No content available" isn't really much better than the ambiguous "No posts available."
#11
re-rolled.
#12
I think the issue was more that the user is on the Content admin screen under the Content management section and the term "posts" isn't consistent with how we're referring to...uhhhh...content everywhere else...
At least that was my impression when I saw the issue. I think the whole "Create Content" mystery is being taken care of in another issue.
#13
Simple change, fixes the issue of posts not being used elsewhere in the interface. RTBCing assuming test bot doesn't complain.
#14
I confirmed with beeradb (who was there during the testing this report comes from) that the problem was with the word "posts" in the interface. There are probably other problems as well, but this at least gives us consistency. :)
Committed to HEAD. Thanks, folks!
#15
Automatically closed -- issue fixed for 2 weeks with no activity.