Running a personal page is neat. Only problem is that some of my users have complained via email that the don't want to post because EVERYONE who's registered can see thier blog. If I disable blog access to the registered user's, they will no longer be able to view thier own blog even though they can add content to it.

Maybe there should be a way for user's out there to have a blog and choose whether or not other registered users can view them or not without barring themselves from thier own blog.

Just an idea.

Comments

laurion’s picture

Component: Code » blog.module
Priority: Normal » Major

As others have mentioned, I would like to see a private blog implementation. Ideally, by default, all blogs would be private, and the user could check a box to enter it into the submission queue. Further, as is now, administrators should have the right to skip the queue and go straight to front page, or to moderate a post straight to front page. I think administrators should also be allowed to view all posts, purely from a legal necessity in some cases. Perhaps there should be a group of moderators who are able to rate things to the front page, but not see private posts... hmmmm... And as a bonus perk, a person could create a list of 'friends', and then mark a blog entry private, but readable by friends. Now we start getting into advanced permissions, and topic groups etc, etc... a long path to walk down.

I love drupal, and look forward to it evolving. It's proven to be so much easier to use than PostNuke, and with a very responsive community, I am glad I found it.

ax’s picture

Priority: Major » Normal

see also feature request #9: http://drupal.org/node.php?id=9 (let a user specify if her blog entries should be votable)

adrian’s picture

I have written a Buddy List module that implements this.

Similiar to live journal's functionality i believe.
You will be able to add users on the system to your buddy list, and then (using the nodeapi) it allows you to select if only your friends should be allowed to see the blog item, or you can select which of your friends will be able to see the posting.

There is a possibility of adding user levels, but i feel it's going outside of the scope of the module and would best be left to a proper taxo-based group permission system with private taxonomies.

JonBob’s picture

I'm going to mark this as a dup, since it will be solved by the addition of the node-level permissions API.

cog.rusty’s picture

Version: » 6.x-dev
Status: Closed (duplicate) » Active

Was this ever solved? I think the node-level permissions API offers possibilities but stopped short of this one.

I can't find anything either in core or in contrib to control node visibility by "own nodes".

Some have suggested that "own nodes" should become always visible and other users be excluded by setting the nodes to unpublished, but not even this hack is currently available (because unpublished "own nodes" are not visible, they are only editable).

Pasqualle’s picture

Version: 6.x-dev » 7.x-dev
Dave Reid’s picture

Status: Active » Closed (won't fix)

Lots of contrib modules are helpful for exactly this purpose. Content Access can provide per-node access or default-per-node-type access and is widely used. Marking as won't fix for core.

geodaniel’s picture

You may also want to check out the User Relationships modules, in particular User Relationship Node Access which lets you show content only to your friends.

gnot’s picture

Issue summary: View changes

Hmm... Long story why I was thinking of creating a new private or semi-private blog, but this website was recommended as a pretty good place to do so, and so far I can't find a clue. We're talking about being naked, dipped in clue musk, and dropped in a field of clues during clue mating system, and I can't find one yet...

Sort of an interesting website, and it runs well, but I still feel clueless.