Jon Morrissette
Posts:13
| | 10/27/2003 7:47 PM |
| | It would seem that the Snapsis DNN admin menu seems incompatible with some (not all) modules.
For example, if I insert the "Image Photo Module" available for sale at the Snowcovered.com website unto a page, the Snapsis DNN admin menu will not appear on that page (tab). Instead, a new browswer window gets loaded and a "page not found" error is thrown.
If you would like to experiment with this conflict, I could setup a sample portal directory for you and let you see it first hand. | | | |
|
|
|
David Holt
Posts:4
| | 10/28/2003 9:44 AM |
| | After trying reinstallation of 2.0 version, I get this error:
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Snapsis.DNN.EditModule.Page_Init(Object sender, EventArgs e) +618
System.Web.UI.Control.OnInit(EventArgs e) +67
System.Web.UI.Control.InitRecursive(Control namingContainer) +241
System.Web.UI.Page.ProcessRequestMain() +174
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
Ideas? | |
If you don't know where you are going, then it doesn't matter which road you take, does it?
-- The Cheshire Cat, Alice in Wonderland | |
|
John Mitchell
Posts:355
| | 10/28/2003 11:11 AM |
| Yes,
I had a small bug in one of the zip files that I distributed where the SkinFolder setting was not getting added to the ModuleSettings table.
Here's an SQL statement you can run that should fix it right away:
=========================================================
DECLARE @ModuleID int
DECLARE settings_cursor CURSOR FOR
SELECT ModuleID FROM ModuleSettings
WHERE SettingName = 'container'
OPEN settings_cursor
FETCH NEXT FROM settings_cursor INTO @ModuleID WHILE @@FETCH_STATUS = 0 BEGIN
if not exists (select ModuleID from ModuleSettings Where ModuleId = @ModuleID and SettingName = 'SkinFolder')
BEGIN
Insert Into ModuleSettings (ModuleID,SettingName,SettingValue) Values ( @ModuleId,'SkinFolder','DesktopModules/SnapsisDNN/Skins/AquaBlue/' )
END
FETCH NEXT FROM settings_cursor INTO @ModuleID END
CLOSE settings_cursor
DEALLOCATE settings_cursor
GO
=========================================================== | | | |
|
John Mitchell
Posts:355
| | 10/28/2003 11:19 AM |
| | Sure, I could try it out, but I may know what the problem is.
If the other module is using their own .aspx page and not using DesktopDefault.aspx or EditModule.aspx then you will need a reference to the Snapsis.DNN workspace in the header.
This will be a problem with any module that uses their own pages and does not use the DotNetNuke framework for displaying their module.
| | | |
|
David Holt
Posts:4
| | 10/28/2003 5:56 PM |
| | Eureka!
Thanks, John, for all your help. Everything is working as expected now!
Thanks for the prompt and efficient tech support! I really appreciate it!
| |
If you don't know where you are going, then it doesn't matter which road you take, does it?
-- The Cheshire Cat, Alice in Wonderland | |
|
Nathan Metzger
Posts:25
| | 10/28/2003 8:55 PM |
| | Yes this is the SQL i ran successfully.
Like I said I had a similar problem with the earlier version of this software. | | | |
|
Nathan Metzger
Posts:25
| | 10/29/2003 7:56 AM |
| | More explanation of my error.
I logged in as host.
Uploaded the .zip file.
Selected the SnapsisDNN module installation script.
Clicked Install and got the error above.
The first time I had this problem I think that I manually had to ftp each of the files to the correct directories. Then run the sql scripts, and it started working. One problem I had with the installation is that the Menu Settings in the Admin tab didn't appear on any of my child portals. I had to delete all child portals and rebuild them and then they showed up. | | | |
|
John Mitchell
Posts:355
| | 10/29/2003 8:30 AM |
| Ok, this is starting to make more sense now.
Looking at the error above, I see that it is the DesktopPortalBanner that is getting the error.
The other one was from DesktopDefault not being able to find the SkinFolder.
I'm not sure what the exact error is but, a few details will help to figure it out.
Are you logging into the original host portal when you upload the SnapsisDNN2.0_PA_Install.zip file?
Since te error is in DesktopPortalBanner, it probably has something to do with not being able to find the DesktopPortalBanner.ascx control. If the portal has a skinfolder assigned, and there is not a DesktopPortalBanner.ascx in that folder it will "look up" into the SnapsisDNN folder for the DesktopPortalBanner.ascx control. Are either of thos files there?
The 1.0 version did not attempt to create SnapsisDNN_MenuSettings records for each child portal if it was already there. This was by design to keep from changing the look of all child portals at the same time. This version attempts to leave child portals at their default settings also, but does so by not putting a record in the SnapsisDNN_MenuSettings table until the child portal administrator uses the Menu Settings page to update the portal. If the MenuSettings record is already there from a previous install, then those colors will be used for the Menu, overriding the Skins colors.
You can read more about the Menu styles in this post | | | |
|
Nathan Metzger
Posts:25
| | 10/29/2003 9:57 AM |
| | I didn't log on the host from original portal. I guess I can try that later today.
Any other ideas if that doesn't work? | | | |
|
John Mitchell
Posts:355
| | 10/29/2003 10:46 AM |
| | I sent you the debug version of the DLL, if you put that in your \bin directory we'll be able to tell what is not getting set.
I also created an install checklist Here | | | |
|
Nathan Metzger
Posts:25
| | 10/29/2003 1:35 PM |
| I just tried to install 2.0 from the host account and original portal. No dice.
It isn't copying any of the files to the directories, and not running any of the sql script.
Tried copying the files manually via ftp and running the .sql file in enterprice manager and got an error on line 12 which was a GO statement. I was using a web version of Enterprice manager, so that maybe the cause of the error, not sure yet.
When I get home I'll try Enterprise Manager again and upload the debug .dll. Hopefully that'll get us somewhere. | | | |
|
John Mitchell
Posts:355
| | 10/29/2003 1:53 PM |
| | We may have tracked it down.
It turned out to be kind of obscure in that the bug only happens if a background image is selected in the Site Settings.
I'll make a patch available ASAP. | | | |
|
Nathan Metzger
Posts:25
| | 10/29/2003 2:31 PM |
| | I definitely have a background image selected in the Site Settings.
Hope this fixes it :) | | | |
|
Nathan Metzger
Posts:25
| | 10/29/2003 9:00 PM |
| | Ok. After copying all the old files back to the server I tried the latest PA you send via email.
No Dice.
I copied the debug .dll you sent via email and I think its the same error as before.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Snapsis.DNN.DesktopPortalBanner.Page_Load(Object sender, EventArgs e) +4473
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +29
System.Web.UI.Control.LoadRecursive() +92
System.Web.UI.Control.LoadRecursive() +92
System.Web.UI.Control.LoadRecursive() +92
System.Web.UI.Control.LoadRecursive() +92
System.Web.UI.Page.ProcessRequestMain() +724
Not sure what to try next. | | | |
|
Nathan Metzger
Posts:25
| | 10/29/2003 9:19 PM |
| Ok. I manually copied all files to DesktopModules/SnapsisDNN and copied the DNN.dll to the /bin directory. REFRESHED and it came alive...well kinda :)
I got a new looking skin now but the "Menu Settings" text is in the wrong place. Not sure why. I tried changing the skin to classic DNN and i got an error. Didn't copy that one, so I tried to install the PA again through the host. It got a little further than ussual and may have a valid error.
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: BC30560: 'desktopportalbanner_ascx' is ambiguous in the namespace '_ASP'.
Source File: C:\webhost4life_aspnet\nathan\DesktopModules\SnapsisDNN\Skins\AquaBlue\DesktopDefault.ascx Line: 16
| | | |
|
John Mitchell
Posts:355
| | 10/29/2003 9:51 PM |
| | Looks like this last one may be that the DesktopDefault.aspx & EditModule.aspx files from the zip file still need to be copied to the root folder of the website.
| | | |
|
Rick Chapman
Posts:3
| | 10/29/2003 11:30 PM |
| | Thanks for the reply.
The problem was my previous install of CSS 1.0.10 adds a SnapsisDNN.css into the portal child folder. I had to remove this SnapsisDNN.css file as well as the portalbanner.jpg and portalbannerrepeat.jpg. It was then the Skin folder displayed properly. I know I can then use the portal child .css files to override, but in my case, I just wanted the Skin to display correctly and it did. | | | |
|
Nathan Metzger
Posts:25
| | 10/30/2003 5:50 AM |
| | I just reuploaded both those files and got the same error. I need the latest .zip of 2.0 to bring my site back up to try anything else. I emailed you a different address to send it to. | | | |
|
Craig Despres
Posts:1
| | 11/04/2003 5:11 PM |
| | I am experiencing the same thing, but only on one of my parent portals (Not the root portal). I have tried all the steps in this thread, and still can't solve the issue. The admin of the portal wasn't able to tell me the last step performed before the error, but the skin was working at one time.
Any help would be greatly appreciated.
Craig
| | | |
|
Admin Account
Posts:5
| | 11/06/2003 8:49 PM |
| | Hi Craig,
It turned out that Nate had a mixture of 1.0 and 2.0 in the different directories due to trying to get something to work after the intial bug which happened when a Background Image was selected in the Site Settings table. Version 2.0.1 corrects this. Let me know if you need the latest version. | | | |
|