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 ForumsForumForumcannot get to the Forum Configuration after upgarde to 3.10.04cannot get to the Forum Configuration after upgarde to 3.10.04
Previous
 
Next
New Post
9/12/2005 11:49 AM
 
to be exact... i have 5 xml files in /desktopmodules/forum/resources:
_forumemail.xml, _forummedia.xml, _forummenu.xml, _forumskin.xml and _forumwhatsnew.xml....
 
More info:
 
dnn version: 3.1.1. (upgraded from 3.1.0, 3.0.13 and 3.0.12)
forums version:  3.10.04, upgrade from 3.10.01
 
cheers,
 
erik

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
9/12/2005 12:23 PM
 
I installed a fresh forum in a fresh dnn 3.1.1 to compare the differences. I found a few, for instance the missing blog files... maybe its a good idea to post which files can be deleted with no harm... for now i deleted everything with "Blog" in its name...
 
furthermore, i checked to see if there were any differences in the database. The structure was exactly the same, but the settings where quite different... especially when it comes to the skinsettings. I used the DotNetNuke Silver skin (i believe an early version by Nina), but that skin name is not available in the new version. So i edited the module settings table to point to the default DotNetNuke skin (especially the ForumSkin setting, but also the template settings).
 
That seems to have taken care of almost all of the problems (after a emptying the dnn cache of course)... however, the image path for the solpart menu points to .../forum/themes/[old skin name]/images/. I emptied the cache several times, but no success... where might that path be saved?
 
cheers,
 
erik

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
9/12/2005 12:42 PM
 
I solved my last remaining problem as well. Apparently the solpart menu uses a lot of caching... this is what i did:
 
* problem: image directory of forum solpart menu pointing to old skin name (namely dotnenukeSilver) in new themes folder
* set the forum skin to Dotnetnuke
* copied the dnnsilver dir to dotnetnukesilver
* refreshed page... et voila: image dir of solpart image dir points to dotnetnuke now
* deleted dotnetnukeSilver dir
* changed forum skin to dnnsilver
* solpart image dir still points to dotnetnuke.... is this a caching problem of some sort?
 
cheers,
 
erik

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
9/12/2005 1:06 PM
 
I have the same issue, and in the Resource Directory:

_forumemail.xml
_forummedia.xml
_forummenu.xml
_forumskin.xml
_forumwhatsnew.xml


 
New Post
9/12/2005 2:01 PM
 

I'm getting the same problem.  I upgraded my 3.01.01 forum today.

 

Eric, did you actually fix an upgraded forum.  Or were those fixes for the new forum you created?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForumForumcannot get to the Forum Configuration after upgarde to 3.10.04cannot get to the Forum Configuration after upgarde to 3.10.04


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