X-Cart forums

[stevekem]

Hello all,

I'm having a skin designed by company for x-cart 4.4 and noticed during preview that the main.css is still being called as well as the altskin.css.

I've been having an issue with the light and lucid skin briefly appearing during page loads throughout site and after using firebug it appears it's being called from main.css.

1. Should the designer be combining these 2 "main" stylesheets together so only 1 "main" one is used for site for better site load time and easier editing?

2. Is there any drawback in combining these 2 stylesheets together such as upgrade issues within branch (4.4.1 / 4.4.2 / etc)?

[balinor]

I actually remove altskin.css all together and make all the edits to main.css.

[stevekem]

After looking at more and more sites based on 4.4, it appears that's the method I have seen as well, alot even have there main .css down to 1,000 - 2,000 lines.

It appears the designer made most (if not all) of the edits, as well as adding the new elements to altskin.css so now I have 10,000 lines (with both) of .css plus all the module .css of course.

Any idea on the easiest way to combine the 2?

Originally Posted by balinor

I actually remove altskin.css all together and make all the edits to main.css.

[balinor]

Bummer. I have never used alt - I just customized main and cut the size down by about 50%. Guess you are just going to have to combine the two and go in and look for duplicates

[ozchris]

I found altskin useful when swapping skins.
We have a Halloween, Christmas, Bookweek and regular skin.
So the major structure was in common/main.css and the variations were in the different altskins.
That way the static content doesn't need to get swapped over each time.
Or was that the wrong approach?

[stevekem]

That sounds like the right approach. That's how I thought my designer would be creating our site like, but instead they made all edits to the altskin.css, so now the main.css is conflicting with the changes in altskin.css and leaving site with thousands of lines of unused elements and a pain to update.

Originally Posted by ozchris

I found altskin useful when swapping skins.
We have a Halloween, Christmas, Bookweek and regular skin.
So the major structure was in common/main.css and the variations were in the different altskins.
That way the static content doesn't need to get swapped over each time.
Or was that the wrong approach?