Since there isn't a subforum for skinning, I guess I'll start this here. I installed a clean install on an XP Pro laptop, latest OS updates, MSDE (w/Enterprise Manager), VS.NET 2003, created a default virtual directory 'dotnetnuke' right of the C drive, gave
ASP.NET full control of the folder and subfolders, and a SQLDNNDBO user with DBO rights to the dnn database. I run the app. It looks fine. Login as host,host...and go to a module and change the skin of *that* module (any module) to one of the other default
DNN containers. When I preview or update the module, I get broken images on all corners. Can anyone help me understand why the default container skins do not work on my clean install? Thanks. I can't start 'learning' about skins, until I'm confident that my
environment to build the skins is working correctly... aaava
Hey bobster: Well, this is the problem. Why it happens, or how to fix it, I'm not sure. I look at the properties of the images that are broken (which by the way, the two broken default container skins are the DNN-Connected, and DNN-Standard), and see this:
http://localhost/[dnndirectory]/Portals/0/Containers/DNN/body_corner_right.jpg For some reason, DNN doesn't install any of the skins in the 0 folder, It stores them in the _default folder. So why is my copy of DNN looking in the 0 folder where the default
skins are NOT installed, and not looking in the _default folder where they *ARE* installed? If I can fix and understand why a clean install did this, I think I can start learning how to do a skin. And thanks so much for the idea bobster. *Smacks head* I should
have thought of this, but DNN is still sort of a mysterious black hole for me, so I'm just not thinking logically about it yet. Any detailed explanation would be greatly appreciated... aaava
Few suggestions... 1. Go to Host/File Manager and click on the synchronize database and filesytem link. 2. Go to Admin/File Manager and click on the synchronize database and filesytem link. 3. Perform your skin setting (selection) while login as Admin instead
of Host.
Seems you are getting there aaava, ;) DNN does not install any skin in the 0 folder by default. It uses the skins and containers inside the _defualt folder. I think you probably copied the folders over the wrong folder, but I could be wrong. You can try to
FTP the original skin/container folders from a clean unzipped copy to the apropriate folder in your site. You can also reinstall the skins using the original zips in each of those folders. The Connected container is in the DNN folder inside portals/_default/containers.
If you use Host File Manager to install your skins or containers, DNN will put them in the _default folder and they will be available for all portals. If you use Admin File Manager, it will put them in the folder that corresponds to the portal thus it will
only be available for that portal.
As I stated, this is a *new* install. I *did* not copy *any* folders to anywhere. Just changed the connection string and that's it. I've also already stated that I'm installed on my XP Pro laptop, w/ASP.NET, .NET Framework 1.1, and IIS 5.x....though I don't
think any of these things has anything to do with it. So I'll ask the questin again, and hope that someone can answer it..understannd that as I said, this is a *clean* new install. Could someone explain to me why the *code* for 2.1.2 is looking in the 0 folder
for the default skins instead of the _default folder? Thanks in advance for any detailed answer. aaava
Let me also state, that this was a ONE-TIME install. I didn't install it, then move it, or anything else. I simply got the connection string changed, opened it from the web, and log in as host. That's it. NO OTHER CHANGES. No copying of folders or anything.
aaava
And I guess I have to be clear again. I'm not looking in the 0 folder, the DNN code *is looking* in the 0 folder for the skins. I realize (well, I think, since I see all the skin folders IN the _default folder) that the DNN code *should* be looking in _default,
and should be creating image links based on something somewhere in the skin settings, which I haven't *touched*. But when I click properties on a broken image, the image url is pointing to 0, instead of _default. *Sighs*.
Hey eck: I didn't see your post before. Sorry. I tried what you suggested, and no change. Images still point to 0 intead of _default. I'm at a complete loss about this. It just doesn't make any sense that a clean install with no changes would stop the show,
before I can *DO* a single thing. No one has had this happen to them? I mean, why is this happening to me? Can someone tell me what the POINT is of the 0 folder? Can someone tell me how DNN could possibly be looking in that folder instead of the *folder* it
SHOULD be looking for the dang thing? Another day, another none-more forward. Docs explain absolutely nothing about this, and I don't know of any other forum to ask this question, or I'd be there, done that.
Just did a complete NEW install. Deleted the virtual directory, the databases, the dnn folder, even rebooted the pc. Reinstalled a clean version of 2.1.2, then a new database, then a sql user with DBO rights to the DB, change the web.config file after unzipping
a completely new dnn into a completely newly different named folder after of course as I said delteing the other one. Created a new virtual directory in IIS, then reran. Took 2 minutes, loaded fine. Then I log in as host, go to change the Module Container
of the main content frame using Module Config to DNN-Connected (though NONE OF THE SKINS THAT ARE INSTALLED WORK EXCEPT 'Classic', and again get broken images. The images ALL POINT TO the 0 folder and NOT THE _default folder. This stinks. I don't see how it's
possible that I am the only person this happens to. This is just a simple XP Pro box, with MSDE and Enterprise Manager from my SQL2K disk. Can someone please explain to me why this is happening? Why the code I have not touched is looking in a 0 directory instead
of the _default? Can someone from the core group explain this? I mean, this isn't the way it's supposed to work, right? And I'm doing everything correct per the install procedures in the docs, and the things missing too, like the ASP.NET user rights for the
DNN folder. I have until tomorrow morning to show a client I can use this instead of phpnuke...I'll stay up all night again like last night, but I need someone to give me some answer beside 'I copied folders'... aaava
aaava
Contributor
5654 Points
1170 Posts
Default skins in clean install come up w/broken images...why?
Jul 25, 2004 08:24 PM|LINK
bobster234
Contributor
5195 Points
1039 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 25, 2004 09:35 PM|LINK
TextLayout Module - create multiple column layouts easily
aaava
Contributor
5654 Points
1170 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 25, 2004 09:52 PM|LINK
ecktwo
Contributor
2830 Points
564 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 25, 2004 11:38 PM|LINK
hooligannes9...
All-Star
16504 Points
2917 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 25, 2004 11:57 PM|LINK
aaava
Contributor
5654 Points
1170 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 26, 2004 12:28 AM|LINK
aaava
Contributor
5654 Points
1170 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 26, 2004 12:35 AM|LINK
aaava
Contributor
5654 Points
1170 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 26, 2004 02:04 AM|LINK
aaava
Contributor
5654 Points
1170 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 26, 2004 02:14 AM|LINK
aaava
Contributor
5654 Points
1170 Posts
Re: Default skins in clean install come up w/broken images...why?
Jul 26, 2004 03:05 AM|LINK