Closed (fixed)
Project:
Drupal core
Version:
5.0-beta1
Component:
node system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
10 Nov 2006 at 10:11 UTC
Updated:
19 Dec 2006 at 06:00 UTC
Jump to comment: Most recent file
Attempt.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | contentname_14.patch | 1.23 KB | pwolanin |
| #10 | contentname2jv.patch | 1.09 KB | jvandyk |
| #8 | contentnamejv.patch | 1.51 KB | jvandyk |
| #6 | node.module_47.patch | 1.59 KB | RobRoy |
| node_wording.patch | 511 bytes | chx |
Comments
Comment #1
pwolanin commented+1 for this- I found the title "posts" for this menu item a jarring change from 4.7.
Comment #2
kbahey commentedSite content is better than posts for sure.
+1
Comment #3
RobRoy commentedI like it. Posts still confuses me even after seeing it a hundred times. +1
Comment #4
RobRoy commentedRTBC'ing this as it's pretty tiny change.
Comment #5
profix898 commentedAnd what is about 'Post settings'? If 'Post' becomes 'Site Content' this also needs some re-wording, I think.
Comment #6
RobRoy commentedAh, I forgot that was in there. I added a few other changes. I don't think we should blindly change all 'post' to 'content', but for the most part we should use 'content' to describe it in a general sense and a few 'post' terms here and there are okay to describe 'pieces of content'. IMHO.
Comment #7
chx commentedWell, I do not agree. I would prefer one word for content.
Comment #8
jvandyk commentedI agree that the current wording is confusing. Here is my proposal.
1. Change "Posts" to "Content". Reasoning: it's under the Content management section, so we use Content for consistency. We developers would like to use "Nodes" but "Content" is friendlier. I don't think of a node as a "Post", I think of it as a piece of content. I reject "Site content" because otherwise we have to say "Site categories" and "Site comments" too.
2. Change "Search posts by keyword" to "Search content by keyword" to be consistent with the above change.
3. Change "Post settings" to "Posting". "Post" is not a good word to use because it can also mean "after". And we're not talking about the post itself, we're talking about the act of posting. And "Posting settings" is confusing because of too many ings. And to be consistent with "RSS publishing" below, we need a similar phrase to be consistent.
Comment #9
drumm'Posting' seems somewhat vague.
Maybe fields can be moved. Two out of three settings go well with content types, because they control how content types work. The third, number of posts on the front page, seems a bit closer to the page with the big list of content.
Maybe the page can be moved. The settings for comments is a local task next to the comment list. The settings for users is a first class admin page. There is a precedent for both.
Comment #10
jvandyk commentedOK, I'm not up for moving stuff around to get the word 'Posting' changed. I'm more concerned with the other two changes.
New patch leaves Posting alone but changes Posts to Content and Search posts by keyword to Search content by keyword.
Comment #11
webchickImpacts string freeze.
Comment #12
pwolanin commentedYes, let's at least revise these most highly offending menu items.
Comment #13
RobRoy commentedStill got a 'title' => t('Search posts'), in that search menu item.
Comment #14
pwolanin commentedOk, a trivial patch. This should be RTBC
Comment #15
RobRoy commentedLooks good to me. Marking RTBC as this is pretty minor and a good start to getting terminology consistent.
Comment #16
dries commentedThanks for the polish. Committed.
Comment #17
(not verified) commented