Jay,

yes the blog is a portal wide module and not a page wide module, so the entries of a blog will not be deleted if you delete the module from the page.

You can delete the blog from the blog settings. Enter the blog settings and click the delete link.

And now to your rss feed problem. I have tested it on your site, and I'm now able to reproduce the problem.

The problem occurs only if you try to access the rss feed for which a user account is needed. That means it works without any problems if the blog has public access.

I will have a look what can I do, to solve that problem.

regards

HP

Jay,

I have investigated the problem now more in detail.

The problem is that the rss feed of the blog module is much more complex as the rss feed of the most other modules. That is the reason why I couldn't use the default rss mechanism of DNN to create the rss feed.

Therefore the rss feed will be created in a dedicated ascx.control of the blog module, and this presupposes that the user must have access to the page and the module without any additional logon information.

The only idea I have at the moment is the following:

You can place an additional blog module on a second page with public access, and then you can setup in page settings the hidden attribute to the page.

Now you can create a rss link list on your normal blog page which points to the rss urls of the blog module on the hidden page.

There is no easy way to solve that problem in case of the architecture of DNN. I will have a look that we can solve that problem in a future version.

regards

HP

Jay,

the dnn search is always a problem. But I have found a trick how you can re build very easy.

Log on as host. Enter the sql menu in host settings, paste the following code into the sql window and execute this as script.

======= Start copy after this line ========

delete SearchItem

go

delete SearchWord

go

======= Stop copy before this line =====

The best is now to wait for the next scheduled rebuild of the dnn search, if you don't like to wait you can manually enter the search admin, and rebuild the index manually from there.

regards

HP