yes I did, I checked the minified file by clicking on the link to it in the page source, but there I see the error message at the top of the minified file:
/* Minification failed. Returning unminified contents.
(784,65): run-time error CSS1045: Expected term, found $
(784,65): run-time error CSS1019: Unexpected token, found '$'
(784,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$'
(792,65): run-time error CSS1045: Expected term, found $
(792,65): run-time error CSS1019: Unexpected token, found '$'
(792,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$'
(800,65): run-time error CSS1045: Expected term, found $
(800,65): run-time error CSS1019: Unexpected token, found '$'
(800,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$'
(808,65): run-time error CSS1045: Expected term, found $
(808,65): run-time error CSS1019: Unexpected token, found '$'
(808,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$'
(816,65): run-time error CSS1045: Expected term, found $
(816,65): run-time error CSS1019: Unexpected token, found '$'
(816,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$'
Ok, I will see if we can improved the the path parsing when creating a bundle in the template editor.
The minification errors are errors in the CSS, even though it has been compiled by SASS. My process to fix would be to request the SASS files one by one, and check the CSS for parse errors. You can request a SASS file in the browser and it will be compiled to CSS, e.g. http://localhost:9434/css/mysassfile.sass
Your original css errors originate in the source scss files though unless they are being introduced by the compiler (unlikely).
I took a quick look and it seems that all of the issues are coming in from fontawesome. Perhaps try removing fontawesome from the bundle and see if it minifies.
I also tried to csslint the fontawesome css only and and it shows the same error.
Optimus not working in Umbraco 6.1.6
Hi, I just installed Optimus.core (v1.2.1) on my Umbraco 1.6.1 install
I created a bundle (style) but it doesn't seem to work. When viewing de pagesource Optimus has put this link to my style bundle:
Is there anything I'm missing?
my testsite is at:
http://test-armoede-in-belgie.ugent.be
thanks for your help,
Anthony
Hi Anthony,
Could you please post the contents of /App_Plugins/Optimus/Config/Bundles.config? It should help us understand whats going on.
Thanks,
Jeavon
Hi Jeavon, thanks for looking into this:
greetings,
Anthony
I wonder if it's just those two dots, could you try
You will need to restart the application pool if you manually edit the bundles.config for it to take effect
Yeah will probably be the 2 dots, will spotted ;)
@Jeavon,
I just created a new stylebundle and it seems that the bundle gets added to the Bundles.config file like:
I removed the old stylebundle from the Bundle.config file and restarted the webserver and now it works :)
thanks,
Anthony
Cool, did you create the bundle in the template editor?
yes I did, I checked the minified file by clicking on the link to it in the page source, but there I see the error message at the top of the minified file:
/* Minification failed. Returning unminified contents. (784,65): run-time error CSS1045: Expected term, found $ (784,65): run-time error CSS1019: Unexpected token, found '$' (784,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$' (792,65): run-time error CSS1045: Expected term, found $ (792,65): run-time error CSS1019: Unexpected token, found '$' (792,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$' (800,65): run-time error CSS1045: Expected term, found $ (800,65): run-time error CSS1019: Unexpected token, found '$' (800,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$' (808,65): run-time error CSS1045: Expected term, found $ (808,65): run-time error CSS1019: Unexpected token, found '$' (808,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$' (816,65): run-time error CSS1045: Expected term, found $ (816,65): run-time error CSS1019: Unexpected token, found '$' (816,65): run-time error CSS1062: Expected semicolon or closing curly-brace, found '$'
my css file was compiled by Sass
greetings,
Anthony
Ok, I will see if we can improved the the path parsing when creating a bundle in the template editor.
The minification errors are errors in the CSS, even though it has been compiled by SASS. My process to fix would be to request the SASS files one by one, and check the CSS for parse errors. You can request a SASS file in the browser and it will be compiled to CSS, e.g. http://localhost:9434/css/mysassfile.sass
Jeavon
Hi Jeavon,
On the production site I only have a .css file, no .scss
greetings,
Anthony
Hi Anthony,
Your original css errors originate in the source scss files though unless they are being introduced by the compiler (unlikely).
I took a quick look and it seems that all of the issues are coming in from fontawesome. Perhaps try removing fontawesome from the bundle and see if it minifies.
I also tried to csslint the fontawesome css only and and it shows the same error.
Hope that helps you.
Jeavon
Hi Jeavon,
Thanks for looking into this. I'll try to remove fontawesome from the bundle.
greetings,
Anthony
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.