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 ForumsBlogBlogBlog Error after upgrading from 4.8 to version 5.01.01Blog Error after upgrading from 4.8 to version 5.01.01
Previous
 
Next
New Post
1/25/2010 11:40 AM
 

 can you please tell me the URL of your website did you read my post regarding to updating the dnn4 to dnn5 

 
New Post
1/25/2010 12:04 PM
 

re url www.pchenry.com

re post about dnn 4 to 5 upgrade

No, what's the url for that?

Thanks.

 
New Post
1/26/2010 10:34 PM
 

Hi Rishi, thank you for trying to help me out, but I decided to back out these changes.  If you want more information, I blogged about it.

http://www.pchenry.com/Home/tabid/36/...

 
New Post
2/25/2010 4:55 PM
 

 I am experiencing the same problem when upgrading from DotNetNuke 4.9.4 to 5.2.3. Only the Blog Entries module displays an error:

An error has occurred.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.NavigationControl.SolpartMenuNavigationProvider.Bind(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu() at DotNetNuke.UI.WebControls.SolPartActions.Page_PreRender(Object sender, EventArgs e) --- End of inner exception stack trace ---

No other module on my site displays this error, so this seems like a Blog Entries module problem that broke as part of the upgrade. I am using the latest Blog module (v 3.5.1).

 
New Post
2/25/2010 6:42 PM
 

 Another work-around is to use a container (and optionally a skin) that does not use the SolPartMenu (e.g. the MinimalExtropy title_blue container (and skin)). This avoids the error message, but still has the menu coming up in a strange location (in the upper left corner of the window for me).

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogBlog Error after upgrading from 4.8 to version 5.01.01Blog Error after upgrading from 4.8 to version 5.01.01


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