Any reason you can think of that when doing this, and creating the template in the style that they aren't being callled?
I'm primarily trying to get all the prefix and navigation customizations out into two separate LESS files..
If you don't want to do the extra.less changes for every style, you can create a template modification (will only work in development mode!):
Template extra.less
Search type Regular expression
Search for /$/ (i.e. "append to the end")
Replace with: -> your code here, e.g. {{ include('custom_prefixes.less') }}
Yep... can carry on.. one of the reasons of me wanting to break it out into separate templates is what bit me in the arse.... amazing how two little
Less:
}
}
being out of place can affect you.... and for some reason, at one point it wasn't giving me any errors... finally cut/pasted it enough times and totally removed portions from the main EXTRA.less and the two closing designators showed up as missing.
May try this... but it's not that big of a deal to cut/paste between the two styles (all I use)... and I am making frequent edits to it so bouncing in/out of development model may be more of a hassle than simple cut/paste.
If I was running more than 2 styles, I'd most likely do this.
May try this... but it's not that big of a deal to cut/paste between the two styles (all I use)... and I am making frequent edits to it so bouncing in/out of development model may be more of a hassle than simple cut/paste.
If I was running more than 2 styles, I'd most likely do this.
Just wanted to bring this up as an alternative. But, you would only have to use dev mode once: to create the template modification. Afterwards you could edit the templates that you include with the template modification like normal.