Couple of questions ... does upgrading the overall DNN version retain the existing blog items (and other data on the site)? 

Also, I've noticed that "Blog" doesn't show up in the list of modules in the admin header at the top of pages when logged in to DNN, even though it shows up in the list of installed modules in Host | Module Definitions.  How do I get it to show up on the list of modules?

Thanks,

Dan

Yes, everything is supposed to be retained. It's important you spend time sorting out how to backup and restore your portal before attempting upgrades. Also ensure that you set correct permissions and set them again before and after upgrades. DNN needs to be able to alter files as it works and I'm fairly certain that permissions are a cause of a lot of upgrade problems.

Webhosts will often mess up permissions on sites simply by moving accounts around their systems.. and they just ignore any potential issues until someone complains. I religiously reapply permissions every time and have not had a faulty famework upgrade since doing so... at least as far as I can tell... there are always one or two strange things going on.

Dan, about the module not showing on the list... have you set the module as a premium module? Go and edit the module in the host menu, modules section and you'll see the premium settings. If it is premium, then ensure that the portal you want to use it on is in the right hand list in that section.

Rob

hmm I have to say I would have been surprised if the second blog module was pulling in the data from the first module. Modules are generally made so that they can be installed many times independently of each other. There are some modules that have settings for sharing data with other instance, but not the blog so far as I know.

You best solution is to install the blog once on one page, get it up and running as you want, then go to the other page and insert a copy of the module from the first page - use the dnn control bar to do this.. it has the radio buttons top middle for the purpose. Then, if you don't want the source module to be visible on the homepage, simply make it invisible to everyone but admins.

I haven't tried this with the blog, but it should work... let us know in any case.

Rob