caroig
 Advanced Member Posts:15
 | | 11/05/2007 8:39 AM |
Alert | Hi, Now that we can finally use doctypes easily in DNN, you need to update your skin samples. After installing the latest version, none of the Aggregator skins would work for me. The case of the skin names does not match the case in the css file - works fine in quirks mode, but not with a valid doctype. I thought it was a more serious problem at first, but after wasting a bit of time diagnosing it, it was just a question of updating the stylesheets. | | | |
|
dnnstuffadmin DNNStuff Founder
 Site Member Posts:1264

 | | 11/06/2007 4:42 AM |
Alert | Hi caroig,
I agree with you. I'll have to review the naming conventions. I'm putting together a new version that changes some of the base html that is generated and will also allow the user to define their own html templates for rendering. This is going to allow a lot of freedom as it won't be necessary to have the source to make changes in compliance etc.
I took a quick look at the css files and they seem to be matching the skin name cases in my test environment. Is there a specific skin that you've found that doesn't match?
| | Richard Edwards DNNStuff Founder | |
|
caroig
 Advanced Member Posts:15
 | | 11/07/2007 2:17 AM |
Alert | Great. I'm looking forward to the html templates.
I've just had a check back at the install pack for Aggregator and yes all the skin names and styles sheets match. The problem is on my server (crystaltech hosted) all the directory names are in lower case aside from a few I've changed. I don't really understand why. Do they get overwritten in each install? Both my FTP and servers seem quite happy with capitalised foldernames. So I'm not quite sure where the problem arose from. | | | |
|
dnnstuffadmin DNNStuff Founder
 Site Member Posts:1264

 | | 11/07/2007 5:04 AM |
Alert | That's odd. I thought maybe my first release that included skins had the casing wrong but it's fine as well. The skins are included in the resources file. For a test, take the resources.zip file out of the install zip and then use the DNN file manager to upload it to an empty test directory under portals/0 and check off the option to unzip. Then take a look at the directory structure that is created and see if it's changed when uploading.
| | Richard Edwards DNNStuff Founder | |
|
caroig
 Advanced Member Posts:15
 | | 11/07/2007 5:24 AM |
Alert | I'll have a look when I have a moment.
Thanks | | | |
|
rodneyjoyce
 Advanced Member Posts:14
 | | 07/07/2008 6:03 AM |
Alert | Hi Richard,
I have recently implemented the XHTML Transitional Doctype in my skin and all my tabs have disappeared. I use a custom template on Agg. 5.0 - is it a case of updating it?
You can see it on my test site here - http://test.pokerdiy.com/Leagues/PokerLeagues/tabid/435/Default.aspx (near the bottom- "New Poker Leagues")
Thanks Rodney www.smart-thinker.com www.pokerdiy.com | | | |
|
dnnstuffadmin DNNStuff Founder
 Site Member Posts:1264

 | | 07/07/2008 10:24 AM |
Alert | Hi Rodney,
Have you tried any of the standard tab skins to see if they work?
Send me a zip of your custom template, your site skin and dnn version information to support at dnnstuff.com and I'll mock something up and take a look at it.
The current version of Aggregator isn't strict xhtml yet although it's getting closer. | | Richard Edwards DNNStuff Founder | |
|
rodneyjoyce
 Advanced Member Posts:14
 | | 07/23/2008 8:17 PM |
Alert | Hi Richard,
Sorry, I got sidetracked with other issues. Ok, your standard styles work fine. The odd thing with mine is that if I run this page (where the problem exists and the tabs are not visible): http://test.pokerdiy.com/Leagues/PokerLeagues/tabid/435/Default.aspx through the CSS Validator - http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Ftest.pokerdiy.com%2FLeagues%2FPokerLeagues%2Ftabid%2F435%2FDefault.aspx&profile=css21&usermedium=all&warning=1&lang=en it says that it cannot find the styles.css file (Bad Request) - but it clearly exists when you navigate to that URL directly (http://test.pokerdiy.com/DesktopModules/DNNStuff - Aggregator/Skins/PokerDIY/Top/styles.css).
If I use the Web Developer Toolkit in FF3 I can see the styles.css file fine, but I am not convinced that the module is picking up the CSS. There are no images in my template, only the single css file.
I copied the Apple Template over my Style.css and renamed the elements to begin with my template name (PokerDIY) and the styles showed up, so it is finding the .css file. I'll send the zipped template to you know - thanks for your help. | | | |
|
rodneyjoyce
 Advanced Member Posts:14
 | | 07/23/2008 8:55 PM |
Alert | | Ok nevermind, I figured it out - my elements were called ".PokerDIY_TOP_xyz" instead of ".PokerDIY_Top_xyz". I change the word TOP to Top and now it works ok thanks. Any idea why that might be? | | | |
|
dnnstuffadmin DNNStuff Founder
 Site Member Posts:1264

 | | 07/24/2008 6:37 AM |
Alert | Hi Rodney,
I always thought that css wasn't case sensitive but I just found this faq (http://webdesign.about.com/od/css/f/blcssfaqcase.htm) that mentions in XHTML sites, some browsers consider it case sensitive.
| | Richard Edwards DNNStuff Founder | |
|