Posted by David Latapie on September 14, 2007 at 11:59am
3 followers
Jump to:
| Project: | Documentation |
| Component: | Admin Guide |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
This page sums it up very nicely and I propose to add such a caveat in the description of the blog module:
Note that despite its name the blog module is not necessary for a single-user blog. Blog module is used to create blogs for multiple users.
Then, instructions on how to setup a single-user blog (via the story node, for instance) shall follow.
Comments
#1
I think I misunderstand what you mean when you say a "single-user blog". I think you mean that there is a one-to-one relationship between a user and a blog. Which would make single-user blogs be like the blog module not the story module. The story (or page) module would be more like the multi-user blog.
But then again its not. A story is a story, a page is a page, a blog is a blog. In the end, what's in the name?
On the other hand maybe we should rethink how we are naming these seemingly similar things.
#2
I admit my definition was unclear. I meant that it should be more clear that the blog module is to set up several blogs (which in turn might or might not host several bloggers, but this is another matter). Mentionning something like
When using the blog module, we think “that will make Drupal work like WordPress”, but that is not the case. One has to delve into permissions to forbid other users to open their blog and also has to change the menu to make the blog menu disappear (a category with only one subcategory is disgraceful), plus the matter of activating some code we never actually use (I do invite some writers on my blog, but they all use my blog, not theirs).
#3
I must apologize, I still do not know what you are talking about.
I'm not sure how the methodology for blogs are in other CMSs (like wordpress) but in drupal, when you create blog post you are creating a node (which is a generic kind of post) that inherits the author information of the blog owner. And since it can be categorized a blog post, you can treat it specially. Maybe you want a place on your site where you show the 10 most recent blog posts? Maybe you want a calendar that shows your blog posting over time? Maybe you want to create a view that shows the recent blog posts categoriezed with a specific taxonomy tag? All of that is possible because your post was given a content type of blog post.
Perhaps that block of text doesn't help you with your issue. Maybe this will.
If you don't want your website to have a blog for each user that has an account, then you don't want the blog feature, you want the story feature. Story is sitewide and through permissions you can limit who can post stories. If you are hung up about the name of the node type, you can rename the add story menu item to add blog, but in drupal it will always be considered a story.
The point of all this is this: The name of the content type essentially doesn't matter. Drupal treats them all as nodes. Node is generic content type. With Access Control (Permissions) you can control how users interact with these node types.
Does that help?
#4
Also, considering that this is a documentation issue, it really should be put into the documentation queue.
#5
I think you are both talking about the same thing here. Bottom line is that blog module is confusing to new folks because it makes multi-blog sites and not the more common "this is my blog" site with just one blog. I've updated the blog module page to help clarify this a little and directing folks to the single-user blog recipe if that is what they are after.
#6
Automatically closed -- issue fixed for two weeks with no activity.