Freya Fowles
Posts:2
| | 03/14/2005 6:08 AM |
| Hi
I get the following message when I try to install DotNetNuke Skins 3.0 and wondered whether anyone can help me resolve it.
--
Resource Upload Logs
Return
StartJob Starting Installation
StartJob Reading files
Info Loading Snapsis.DNN.Skins.dll
Info File snapsis.dnn.skins.dll read successfully
Info Loading Snapsis.DNN.CSSEditor.dll
Info File snapsis.dnn.csseditor.dll read successfully
Info Loading Snapsis.DNN.NavMenu.dll
Info File snapsis.dnn.navmenu.dll read successfully
Info Loading doublelistbox.dll
Info File doublelistbox.dll read successfully
Info Loading Snapsis.CSS.Skins_3.0.12.dnn
Info File snapsis.css.skins_3.0.12.dnn read successfully
Info Loading Snapsis.CSS.Skins_3.0.12_Resources.zip
Info File snapsis.css.skins_3.0.12_resources.zip read successfully
EndJob Reading files done.
StartJob Reading DNN file
Failure The element 'folder' has invalid child element 'friendlyname'. Expected 'description'. An error occurred at , (6, 14).
Failure The 'friendlyname' element is not declared. An error occurred at , (6, 14).
Failure ExceptionSystem.Exception: Dnn load failed, aborting at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnAdapter_V2.ReadDnn() at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install()
--
Thanks
Freya | | | |
|
|
|
John Mitchell
Posts:355
| | 03/14/2005 7:12 AM |
| Hi Freya, Thanks for purchasing. It appears that you are not running the release version (3.0.12) of DotNetNuke. Please let me know if this is not the case. | | | |
|
Freya Fowles
Posts:2
| | 03/14/2005 10:17 AM |
| You're quite right John - I wasn't running it. Fixed it now and your part works fine now.
Thanks for your help
Freya | | | |
|
John Mitchell
Posts:355
| | 03/24/2005 10:09 PM |
| | One other thing, the AdminMenuContainer classes (3 of them) in the CSS need to be increased in width just a little to adjust for the size of the lables on the control panel for this skin. | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 8:47 AM |
| | I have been forcing myself to use site settings to apply skins, because if you use the main skin selection, it does not set them into the site setting, then if you go to site settings to change something else you loose the skins | | | |
|
John Mitchell
Posts:355
| | 03/25/2005 9:22 AM |
| That's probably a good practice. I know there is a couple of bugs in the DNN core that need to be addressed for this. Were you able to get the SalarO skin to work with the Snapsis Control Panel & CSS Editor? If you wan't I can send you the skin that I modified. | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 3:01 PM |
| I copied the files you sent me into my saloCrystal direcotory, and I still get exactly the same error
Server Error in '/CenterStage' Application.
--------------------------------------------------------------------------------
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested Url: /CenterStage/Default.aspx
| | | |
|
John Mitchell
Posts:355
| | 03/25/2005 3:08 PM |
| Is CenterStage a virtual directory for you DNN application? Are you using Friendly URLs? | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 3:24 PM |
| if you mean, by virtual directory, did I establish a local site using IIS create virtual directory, then answer is yes
freindly URLS is checked | | | |
|
John Mitchell
Posts:355
| | 03/25/2005 3:32 PM |
| When does this error appear? Right after you apply the skin on the Site Settings page? If your virtual directory is CenterStage, then there should be a Default.aspx at the root, so I'm not sure why it is getting a 404. Try turning off Friendy Urls and see if it works. The skin uploader may have cause problems if you used it, so try just unzipping the contents of the zip straight into the skin folder. | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 3:53 PM |
| yes of course there is a default.aspx, it's a red hering message, the missing resource is somewhere else...
All I have to do is delete the controls directory and I am back in business.
I can try a few steps, what exactly would you like me to do..
EG
1/ delete snapsysmodule
2/ change skin to something else...
3/ delete salocrystal dir
4/ make salocrystal dir with the files you sent...
then ????? | | | |
|
John Mitchell
Posts:355
| | 03/25/2005 4:10 PM |
| No need to delete the snapsis module. You can always get working again no matter what skin you are using by renaming the skin folder (this works with normal DNN skins too). Another general tip to determine if the Snapsis Engine is causing a problem is to change that very top line in your skin back to DotNetNuke.UI.Skins.Skin instead of Snapsis.DNN.Skins.Skin which will disable the Snapsis code, but still use the skin. You have already got past that by finding out that deleting the controls folder makes it work, so it must be something in the IconBar (control panel) Try deleting just that file and see if it works and we'll know for sure. Also try unzipping the skin directly instead of using the uploader to see if the parser messed something up. Before doing all this you can zip up the skin that is giving you the error and send it back to me. I'll probably be able to determine what is wrong if I have it local. | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 4:35 PM |
| I did unzip the skins directory you gave me and simply copied it to the skins folder, so we know that the parser is not the problem. And I don't see the point in sending back you what you sent me, unless I miss understood
Isn't deleting the controls directory the same as deleting the IconBar file (as all the other files are used by it. If not I can try that if it will help... | | | |
|
John Mitchell
Posts:355
| | 03/25/2005 9:48 PM |
| Right, if nothing is changed then no need to send it back to me. If it had been uploaded through the parser then it might have had something done to it that was causing the missing resource. Still, you are getting the error and I'm not so we need to figure out what the difference is. If you can get to the IIS logs they might tell you what is actually giving you the 404, or you can look in the IconBar.ascx file at the paths to see if you can spot it that way. There are sometimes more files in the controls directory so I was trying to narrow down specifically which one was causing the error. | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 10:35 PM |
| here is a copy of the log, not much help
#Software: Microsoft Internet Information Services 5.1
#Version: 1.0
#Date: 2005-03-26 04:32:02
#Fields: time c-ip cs-method cs-uri-stem sc-status
04:32:02 192.168.0.4 GET /CenterStage/images/spacer.gif 200
04:32:02 192.168.0.4 GET /CenterStage/Portals/_default/Skins/SalarOCrystal/mbmenu.gif 304
04:32:02 192.168.0.4 GET /CenterStage/Portals/_default/Skins/SalarOCrystal/mbmenu.gif 304
04:32:02 192.168.0.4 GET /CenterStage/Portals/_default/Skins/SalarOCrystal/mbmenu.gif 304
04:32:02 192.168.0.4 GET /CenterStage/Portals/_default/Skins/SalarOCrystal/mbmenu.gif 304
04:32:19 192.168.0.4 GET /centerstage/Default.aspx 302
04:32:19 192.168.0.4 GET /CenterStage/Default.aspx 404 | | | |
|
Keith Thompson
Posts:12
| | 03/25/2005 10:40 PM |
| | confirmed, if I delete the controls/iconbar.ascx file I don't get the error | | | |
|
John Mitchell
Posts:355
| | 03/26/2005 7:29 AM |
| Interesting that there was a 302 (re-direct) right before the 404. Are you logged in as host? If not try that as the host user can see more detail when errors are happening and sometimes the processing of the error is handled differently. Another thing to try. Copy the IconBar.ascx file from the <dnnroot>/admin/controlpanel folder into the controls folder of the skin. The only real difference between that one and one modified for CSS Skins is that it needs to be modified to have a container around it and some CSS to make it float. | | | |
|