Quote:
|
Originally Posted by Triple A Racing
....We'll apply lots of mods to the Custom White Skin view...
|
These have all worked perfectly at the first attempt. That is, until we got to applying changes to this file:
/skins/crisp_white/customer/css/style.less This has been done like all the others, by copying and editing the file, then re-presenting the customised file like this
/skins/*new_directory*/customer/css/style.less which in turn, is then activated by the Custom Module and should produce the desired results. The same method is applied for all the other desired changes and even to this file, which is right next to the previous .less file!
/skins/crisp_white/customer/css/style.css and of course, all other changes work.
With this file, once the system reads the .less file provided by the Custom Module, the public side of the dev store simply looses all the normal view and becomes just a list of links...Remove the customised file, re-deploy and we're back to normal again.
We're guessing that it's to do with the logic route involved, as we can modify .less files elsewhere e.g. within
/skins/common without any issues or failures like this one. This is a little different, as we applying a change via the Custom Module to a Module that's already applying changes to the default skin
however, it's only this file that has this failure (so far)... The irony is that we can apply the desired change easily by Custom CSS, so that's why we are assuming it's just the logic route that's causing the issue when using the Custom Module?
