Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Maximum ASP
  Ads  
Aspose - The .NET & Java component publisher
 


  Sponsors  

Meet Our Sponsors

.: CounterSoft :.
telerik
ExactTarget email software solutions
Merak Mail Server
WebSecureStores -- ASP.NET & DotNetNuke Hosting Solutions
FCKeditor Project
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Make it Hot! ( ...  Problem with HouseMenu SkinObject
Previous Previous
 
Next Next
New Post 3/30/2006 3:56 AM
User is offline Phil Biggs
52 posts
10th Ranked


Problem with HouseMenu SkinObject 
Hi,
 
Can anyone shine a light on this?....
 
I've installed Tim Rolands' HouseMenu and the accompanying HouseMenu SkinObject onto DNN 3.2.2. The menu works perfectly as an ordinary Desktop Module but when loading a skin that references the HouseMenu SkinObject then I get the following error (100's of times...it loops in the loading process) :
 
ModuleId: -1
ModuleDefId: -1
FriendlyName:
ModuleControlSource:
AssemblyVersion: 03.02.02
Method: TimRolands.DNN.SkinObjects.HouseMenuSkinObject.HouseMenuSkinObject.Page_Load
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: Mainsite
UserID: 1
UserName: host
ActiveTabID: 35
ActiveTabName: Skins
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://10.0.8.125/Host/Skins/tabid/35/portalid/0/Default.aspx
ExceptionGUID: 93210c1b-6ba5-4338-95bf-935bd4816423
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Object reference not set to an instance of an object.
Message: 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 TimRolands.DNN.SkinObjects.HouseMenuSkinObject.HouseMenuSkinObject.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
StackTrace:
Source:
Server Name: LENNON

The supplied readme file states :
 
"Due to a bug in DNN 3.10, the individual files may be placed in your "DesktopModules" folder rather than the "DesktopFolders\HouseMenuSkinObject" folder. In that case, you would have to copy them manually into the correct folder."
 
Even though I'm using 3.2.2, the HouseMenu SkinObject files are still installed under DesktopModules. I therefore tried moving them to Admin/Skins as per the core skin objects - but the same error occurs. In 3.2.2 I can't find any folder called "DesktopFolders" that Tim's readme referes to.
 
Any help or clues greatly appreciated.
 
Thanks in advance
 
New Post 3/30/2006 4:15 AM
User is offline Lee Sykes
277 posts
www.dnncreative.com
9th Ranked


Re: Problem with HouseMenu SkinObject 
Hello, not too sure what error you are receiving here. I've installed the Skin Object without any problems on 3.2.2. and you don't need to do any special configurations.

This is the method I used:

Go to Host menu / Module Definitions
Upload New Module
Select the HouseMenuSkinObjectPA_01.02.00.zip file
And install

- You can double check it has installed. - Within the module definitions, at the top is Skin Objects, click on the edit pencil icon next to this and in this list you should see HouseMenu.

All you then have to do is install your skin with the HOUSEMENU token.

NOTE: If you have installed your skin first, you will get errors & you will have to uninstall and re-install your skin to get DNN to setup the skin correctly.

Hope this gives you some pointers.

If your looking for some code for setting up the HouseMenu, here you can download a free DotNetNuke skin which uses the HouseMenu.

I also created a video on setting up the HouseMenu, but this is just available to subscribers of the magazine. - Hopefully you will be able to get started with the info above though.

Thanks,

Lee Sykes - DNN Creative Magazine - 356 Video Tutorials, Articles, Interviews - December Issue 39 out now!
DNN Creative Magazine for DotNetNuke

Twitter: www.twitter.com/leesykes

Lee Sykes's Facebook Profile
 
New Post 3/30/2006 4:25 AM
User is offline Phil Biggs
52 posts
10th Ranked


Re: Problem with HouseMenu SkinObject 
Hi Lee,
 
Thanks for the quick reply. I had installed the skinobject before the skin itself and can see the HouseMenu skinobject in the Skin Object listing ... so I'm still a bit non-plussed! Will try uninstalling skins and skin object and then see what gives.
 
WIll also look at the skiin you mentioned.
 
Cheers
 
 
New Post 4/5/2006 11:40 AM
User is offline Tim Rolands
52 posts
www.houseofnuke.com
10th Ranked


Re: Problem with HouseMenu SkinObject 

Sorry I didn't reply earlier, but I'm still working on training myself to come around here for the DNN forum.

Don't know why that happened for you under DNN 3.2.2. It really shouldn't. But there is a bad typo in the readme file: "DesktopFolders" should be "DesktopModules".

Did you get everything working?


--
Tim Rolands
House of Nuke
Where DotNetNuke(R) Lives
 
New Post 4/5/2006 3:43 PM
User is offline Nina Meiers
1720 posts
www.xd.com.au
5th Ranked




Re: Problem with HouseMenu SkinObject 

Things like this are easy to fix.. Just create the folder name and put them in there.. A while ago there was  some change/bug, but I ran into this problem myself with some older versions of different skin objects. There was a change in the name space, where skinobjects were being placed. (That's often what you'll read as a breaking change in dnn.. well one of the problems)  And we resolved it by creating the folder, that is was calling for,  in the right place, and using ftp to move them there and the error disappeared. 

You see, skinobjects from my understanding behave differently to modules - they aren't in the SQL db, but use DNN files, ascx files, images & such and a dll file to run, and while installed using the modules way, they are placed in the host/module definitions/skinobjects section at the top of the module definitions page.

I have been guilty of not installing, but using FTP to place them in the right spot. (I had to do this when I had a couple of sites I was working on and had ftp access, but no host access to add the skinobject.)  And this solved the problem.  Not saying it will solve all, but has solved them in my instances.

Nina Meiers


Nina Meiers - XD Design - Professional, Ethical and passionate about DotNetNuke
Over 50 FREE DotNetNuke Skins

XD Design - xd.com.au by Nina Meiers
 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Make it Hot! ( ...  Problem with HouseMenu SkinObject
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


Expressnet - DotNetNuke Hosting
Expressnet provide premium quality ASP.NET Web Hosting. We specialise in Windows based products including ASP.NET and Microsoft SQL Server. We offer fantastic value packages for DotNetNuke hosting. We also offer free asp.net web hosting
www.expressnet.com.au
Softech Development, Inc.
We help your business work smarter with DotNetNuke. Whether you need a new implementation, a custom module or skin for an existing implementation, or integration with your business processes, Softech has the experience and expertise to make it happen.
www.softechdevelopment.com
Module Development by Engage Software
Specializing in custom module development, training and skinning.
www.engagesoftware.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP