Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogSetting up Roles for using BlogSetting up Roles for using Blog
Previous
 
Next
New Post
1/20/2008 12:47 PM
 

Benny_A wrote

 Antonio Chagoury wrote

Hello Folks,

At the moment, the blogs are "personal" which means that only one person can post entries to his/her blog. There is currently no concept of "sharing" - just one of ownership.

We will be working on extending this and allowing multiple users post to the same blog in future versions.

I hope this clears things up.

 

I appreciate the great effort to no end on DNN and the blog module that's been added recently. However, I have qualms with the shortsighted planning on functionality and features of this module. There has hardly EVER been a case in my blogging life where I wanted to be the sole contributor to a blog. And, as my primary reason for using DNN in the first place is to pass websites back to the clients' control, I can't see why there would be a reason to allow for only a sole contributor.

I guess my big question is "when" will this be released in future version(s), and could you please hurry? Right now, I see no reason to use the blog module when I can create a perfectly fine WordPress blog and iFrame it into my DNN module. As you all probably know, WordPress has had multiple contributor functionality for ages.

I'm sorry, I don't mean to flame, and I really appreciate what you folks are doing with DNN--it's helped immensely with my client-side business. I would love to participate in suggestion/feature forums that have to do with the discussion of current/future modules and products.

Regards,

ben 

I COMPLETELY AGREE with Ben. I expect this to be a major issue with our soon to be released DNN blog if we do indeed have a blog...I will end up having to IFrame it like Ben did

Ben, would you be willing to PM me on how you did the IFraming of a WP blog?? We are on a Windows server with PHP installed, I guess I would need an extra mySQL database installed too...

Thank you, Tom

 
New Post
1/20/2008 12:52 PM
 

Benny_A wrote

Right now, I see no reason to use the blog module when I can create a perfectly fine WordPress blog and iFrame it into my DNN module. As you all probably know, WordPress has had multiple contributor functionality for ages.

Regards,

ben

Ben, would you please explain to us about how you IFrame WP into your DNN sites??

I tried to go to your website, but it doesn't work and these forums don't have any PM features like more full-featured forums.

Thank you, Tom

 
New Post
1/24/2008 7:49 PM
 

I installed this this morning and I've already go it working with multiple users.  It's all how you set up the permissions for each of the modules as described in the first post in this forum.  The one additional thing to note is setting the permissions on the "users" blog.  The five modules are listed below and how those permissions should be set.  You should do this logged in as "host", in edit or design view.  Each module has a "settings" link in the lower right hand corner.  Be sure and change the module names so you know which one your are editing (default they all said "blog") with mine.

  • Search: View only, set "View" permissions like for any module.
  • Roll: View only, set "View" permissions like for any module.
  • Calendar: View only, set "View" permissions like for any module.
  • Menu: Edit functions, so set Module "Edit" permissions for any role that should be able to blog.
  • Entry: Edit functions, so set Module "Edit" permissions for any role that should be able to blog.  (I have "view" permissions for "all users" and "edit" for "registered users")

Then, when a user sets up their own blog, they have the option to make it public or private (blog settings in the menu module).  When posting to a blog, make sure they click the "publish" box regardless if it's a public or private blog (or they can't see their own private posts).  Originally I could only view the private blogs with the "host" account.  When I changed the permissions on the entry module, bingo!  Registered users can now view/edit their own public or private blog, comment on other users public blogs but can't read their private blogs.  The host account can read all blogs regardless.

It works fine, just change the permissions.  I haven't messed with syndication yet, but I'm guessing that's the solution to subscribing to another persons blog.

 
New Post
2/3/2008 4:46 AM
 

Hans-Peter Schelian wrote

 z3r0c00l wrote
Is there a way to configure the "Blog" such that each user has their own sepparate blog (e.g. upon login they see thier blog entries and no others, are able to modify their blog entries and point people to their Blog URL.

This is the default:

Each user has their own blog with child blogs and no other is able to modify or add entries.

regards

HP

Hi  HP  or Antonio   --  The problem I have is that although, as HP says  " Each user has their own blog with child blogs and no other is able to modify or add entries " -- they're still able to See them   --   the Default View doesn't allow me to have each user,  upon login ,  see thier blog entries and no others  -- unless I ask them to make their Blog Private   :    I have to give them "View" Permission in order for them to see their own Blog & Edit it --  but this means that they  also see All the Other Blogs in that Module too -- 

Is there some way to restrict them to seeing their Own Blog Only  -- but for Another Different User Group on the site ( with Permission)  to see All those Individual Blogs in the Module when They  log in ?  --  The Catch 22 is that even if I get the First Group to remember to make their Blog Private ( & therefore Viewable Only by them ) ,  the  Second Group that I want to be able to see All Blogs would end up seeing None ( because they're All Private  !  Help !    : )

( I hope I'm not too much of a Newbie, asking an obviously-solvable question, but I've gone through all the Question & Answers in the Forum's Blog Section  & HP's Answer above came closest to adressing my  problem  --  but having to give "View" Permission in order for them to see & Edit their Own   Blog seems to automatically mean they see not just Their Blog, but All  the others in that Module too  --   p.s I'm using  DNN Version 4.5  &  Blog Module Version  3.3.1 ) 

Thanks very much --    whonu  : )

 
New Post
2/4/2008 3:28 PM
 

Hi whonu,

I don't know if this will help solve your problem, because there are some big limitations to the blog module which you may be facing such as the inability for a user to have more than one blog and the inability on a specific tab to allow different groups or users have access to different lists of blogs.

These limitations notwithstanding, I believe you may be able to achieve what you need.  Let's say you want a single user to have their own blog, where all you see on the tab where there blog is included is their blog and any child blogs the user has created.  Here's how you would achieve that using the DNN Blog module:

  • Add blog to tab - Create a tab and add the blog module.  All the blogs will appear initially.
  • Set permissions for user - Set the permissions as DonF mentioned above.
  • Provision new blog - Either have the user log in and create their blog or log in for the user and create the blog. 
  • Restrict blog list to new blog -  After the blog has been created for or by the user, configure the blog to show blog entries for just this blog.  This is achieved by an admin or host clicking on the Module options page of what DonF called the Poll module above.  It's the module which actaully lists the blog entries.  When I privision a blog, I usually create a single test blog entry which makes it easy to see this module.  It's also the top module by default.  Under Module Options, you'll set to the personal blog page to the blog you created.

The one thing I know you won't be able to achieve is to also have a second tab which does not show the personal blog you just configured.  Any blog modules added to tabs where the Personal Blog Page option is not configured will show all public blogs, and as you have mentioned, setting a blog to private just makes the blog invisible to visitors to your site. 

We may add the ability for multiple people to post to a blog module in a product we created called metaPost (you can see our site for details), but I know that digNuke offers a module which provides this functionality today.  One drawback to allow multiple accounts to post to a single blog is that the blog module's data structure doesn't support a way to associate user id's with an entry.  This means that while multiple authors may be able to post to a single blog, the blog will always show the user to which the blog is associated as the author of the blog entry.

Another solution to your problem would be to use the Ventrian News Articles module.  Don't let the name fool you.  The news article supports pingbacks and trackbacks and other features needed when implementing a blog module solution for an organization.  We'll be releasing a provider soon for the News Articles module which will allow you to post to your news articles blogs from Windows Live Writer! 

HTH,

Don



Don Worthley
Software Architect
Element Eleven

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogSetting up Roles for using BlogSetting up Roles for using Blog


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out