porting site - need 2 blogs for one author
avibodha - October 28, 2009 - 07:06
Hi, I'm porting over a site to Drupal 6 and I need to have 2 blogs on the site. They have different content and audiences and one will actually be role-protected.
What's the best way to build two full blogs - with RSS, categories, archives etc?
I looked at the Blog module but it looks like I'd need to create two users for the main author and have him login to post for each...a little annoying...
What would you recommend? Any advice on building out these full blogs?
thanks for any advice
_
Probably the simplest way is to use 2 different content types (one for each blog), and then use something like view_own, simple_access, or node_privacy_byrole to protect one of them.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
I see
Or would it be better to use the blog_entry added by blog module and just add a checkbox for which blog it goes in?
and then views that filter on those checkboxes?
would it be harder to do the archives that way? (I also need to read how the RSS gets generated too to make sure that will work for each)
thanks
_
You can certainly do it that way as well, I was just suggesting the simplest method. However, if you go your route you'll need to put some sort of real access control in place for the protected blog-- not appearing in a view does not mean the nodes are view restricted.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
thanks, didn't realize that
thanks, I like your first method too...I was thinking that I could re-use something by keeping the same content type for both....maybe that doesn't make sense for drupal?
but couldn't I restrict content type (blog1,blog2) by role and wouldn't that do the protection automatically?
thanks for taking the time to explain
=-=
the problem is that viewing content is a single permission by role. if you disable viewing content, they won't see the blog you don't want them to see but they won't see anything without the aid of another access module. content_access for example. Or you can use taxonomy access and create a private taxonomy, then use a single blog contnet type and those marked with the private taxononmy shouldn't be seen.