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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Module settings unavailable when page link type = URL of page in same portalModule settings unavailable when page link type = URL of page in same portal
Previous
 
Next
New Post
9/24/2007 3:10 PM
 

OK, this subject may sound strange! Why should someone link to a page in the same portal using an URL?

We've built a custom module that requires a parameter in the query string. To achieve this, we've set the link type of the page with this module to "URL", and entered a location like "~/CustomModule/tabid/76/Default.aspx?Param=123".

That works so far, but now we cannot edit the settings of all modules on that page any more. If we try, we get an error message:
"Error: Module is currently unavailable.
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."

The only workaround is to set the link type temporarily back to "None".

Does anyone know the reason for this error?
Or has anyone found another way (without side effects) to pass query string paramaters to modules?

[EDIT] We're using DNN 4.5.5

 
New Post
9/25/2007 3:21 AM
 

this is difficult to diagnose without knowledge of the module. it looks like portal context get lost or sth like this.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/25/2007 4:35 AM
 

Thanks for the answer! Meanwhile I found out that this error has nothing to do with our custom module. It occurs generally with any module type if you set the page link type to "URL", as described above, even if you don't use query string parameters. I could reproduce the error on a default DNN 4.5.5 installation (on Windows Server 2003 with SQL Server 2000) with the follwing steps:

  1. Copy the URL of any DNN page out of the browser's adress bar (e. g. "http://www.domain.com/Home/tabid/58/Default.aspx")
  2. Go to the settings of that page, set the LInk URL Type to "URL" and enter the copied URL as "~/Home/tabid/58/Default.aspx" into the Location input field (you may enter the original URL  "http://www.domain.com/Home/tabid/58/Default.aspx" as well - won't help!), and save.
  3. Try to edit the settings of any module on that page. Result.
    Error: Module is currently unavailable.
    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.

I hesitate to call this a bug because I can understand if you say that linking to pages of the same portal should not be done this way. What's yout opinion?

 

 
New Post
10/2/2007 1:31 PM
 

Any other comments? Can someone reproduce this issue, or is something wrong with my configuration?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Module settings unavailable when page link type = URL of page in same portalModule settings unavailable when page link type = URL of page in same portal


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