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 Blogs Like Dotnetnuke.comSetting Up Blogs Like Dotnetnuke.com
Previous
 
Next
New Post
5/2/2006 11:49 AM
 

How was this set up here?  How did we get all the blogs listed like they are on the blogs page here - I cant seem to duplicate it on my site - did I miss something in setting up?

Help please


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
5/4/2006 8:20 AM
 
I am curious about this also! 

As it stands the blog module appears to be quite limited.  Having only one root blog per portal is not a good idea.  I would think that there would be an option to allow a root blog on every page the use places a blog module.  Also have the ability to aggregate in one display a list of root blogs if desired.  The child blog option appears to be simply "categories" of posts.

It would be nice to place a module on one page that has a list of blogs and when you click on one, it takes you to the page with the selected blog.  Then each individual blog can contain categories (child blogs if you desire) for the posts.

Guess I am spoiled with .Text blogs.  I enjoy thier design for multiple blogs on a single site with categories specific to each blog.

Maybe this abiltiy already exits and I am just not finding the solution.  Any help appreciated!
 
New Post
5/4/2006 9:56 AM
 

I was able to kind of get mine like it is here - if you have access to the database simply go in and set the ParentBlogID to -1 for the blogs you want to be 'top-level' in the blog_blogs table

 

I dont know if this may break anything else (I do get an error with the list module but it doesnt affect how it functions) but it seems to work (

More testing should be done on this hack and I too think you should be able to set up blogs on any page and then categories rather than just one blog with a lot of sub blogs


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
5/4/2006 5:20 PM
 
Here are a few things I discovered so far:

If you are working with child blogs, you can place a "/BlogID/x/ParentBlogID/x/ " in the parameter list as would happen if you select a child blog from the blog list.  If however you leave the parentBlogId off, it is mess up the blog roll list (not show the child blog). 

If I set a child blog's ParentBlogId to -1, I receive a SQL server exception in the title of the blog roll list module and the blog management module (the one that says add blog entry, blog settings, view my blog).   The blog roll list actually shows the blogs properly, but still has the error in store procedure's query.  Would also be nice in the blog roll list to have an option which can limit the list to only those of the current root blog.

The blog search module has a list of all the root blogs as would be expected and seems to handle the multiple root blogs, but it would also be nice in that module to have an option to exclude other blogs from being displayed.

One other thing I would like to see is an option for the display of the Blog Author, Title, Description and Created At time.  As it currently is displayed, if you glance at the page, you might confuse the date of the blog creation with the data of the last post and think that the blog has not been updated for some time.  Would be nice to see these fields with display options so that some or all of them can be eliminated.

At this point, it looks like having multiple root blogs on a portal will cause you to lose the functionality of the Blog Roll list module and the blog management module.  The others appear to handle multiple root blogs fine with my limited testing, could still be some issues.  This is a good blog module, but it could be made a little more flexible for multiple blogs as is common in the world today.
 
New Post
5/4/2006 6:02 PM
 
Quick fix..  The SQL server exceptions I received were due to a call to "m_oBlogController.GetBlogByUserID(Me.PortalId, Me.UserId)" checking for edit rights.  The problem is the in the stored procedure GetBlogByUserId.  The sub query in the procedure expects only one root blog with edit rights for the user.  The fix is just to add a "top 1" to the sub query like:

SELECT @BlogID =
(
   SELECT top 1 BlogID
   FROM dbo.Blog_Blogs
   WHERE UserID=@UserID AND
         PortalID=@PortalID AND
         (
             ParentBlogID IS NULL OR
             ParentBlogID=-1
         )
)

This causes a side effect though.  The Action menu on the Blog roll list module and the links in the blog management module (where it has options for blog settings, add entry, view my blog) will not work correctly and will point to the first blog the user has rights to edit.  If you use the action menu on your blog summary module, it will go to the correct blog.

Other than the above though, I did not observe any other problems, however, I only performed a few minutes of testing.

Note: If every user that has the ability to edit a blog only has one root blog, this will not be an issue and the change above should not be required.  This is only required if a given user has more than blog to which they have edit rights.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogSetting Up Blogs Like Dotnetnuke.comSetting Up Blogs Like Dotnetnuke.com


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