author and datetime not displayed on many pages
Sun, 2008-02-03 01:27 — jurjen
| Project: | The Hive project |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | jurjen |
| Status: | closed |
Jump to:
Description
Many pages, like for example http://www.oehive.org/node/947 do not show who the author is and when the page was created. This is probably just some content-type specific configuration setting somewhere...
- Login to post comments
Comments
#1
Displaying author and datetime was disabled for nodes where node.type="page", I have now enabled it.
The reason why it was disabled, was that it look good when author and datetime are hidden on pages like the YellowPages. Pages like that are usually maintained by site administrators.
So this raises a new question: should creating nodes with node.type="page" be allowed for regular users??
#2
I don't see any reason not to restrict node.type="page" strictly for site editors use.
Another option would be to leave "page" as you have it set up now, and create a new node type for use by site editors. We'd set up the new node type so it doesn't show author and datetime.
#3
I would be perfectly happy to keep page the way it was and restrict it to site uses. To me, having both book page and page is confusing to new contributors and it seems like there are many advantages to book page and no real downsides, even if one ends up with a single page contribution.
#4
I see one downside of a "book page": the user has to choose a parent page, else the new page becomes a new top-level book.
Revoking rights for "page" means a possible problem for already existing pages.
We still had one content-type that we never used yet: "story". So what I have done now:
- "page" can be created by every authenticated user, the page shows author and datetime
- "story" can only be created by admins, does not show auhor and datetime
- executed some sql on the database to change some existing pages to stories
There are now 17 "page" nodes left, these could be changed to other nodetypes I think. After that, the "page" rights can be revoked.
#5