I could not find this MinifyCss() method in nop 4.6 develop version. is there any simple setting that is coming up in nop 4.6 version? What lines of code , I need to comment in nop 4.6 develop version? Due to this error , debugging is very difficult.
I could not find this MinifyCss() method in nop 4.6 develop version. is there any simple setting that is coming up in nop 4.6 version? What lines of code , I need to comment in nop 4.6 develop version? Due to this error , debugging is very difficult.
Thanks , Sateesh
Now, you can avoid a calling of the Uglify.Css method here: https://github.com/nopSolutions/nopCommerce/blob/develop/src/Presentation/Nop.Web.Framework/WebOptimizer/Processors/NopCssMinifier.cs#L37
Another to your issue is to not rely on nopCommerces minification. Instead, use your own bundler and place your static javascript in your theme, and have your own build step for those files. This way you can use webpack or a similar tool and let that handle your minification/bundling process, in my opinion it's much more flexible and gives better results. You can also do other stuff like brotli compression in webpack which would require a plugin in nopcommerce.
Didn't work for me on version 4.5.. This property "Processors" seems to not exist, and the property "_assetPipeline.Assets" is readonly... I'm still trying to get those javascripts not minified to debug a javascript behavior of onepagecheckout step, duplicating my script if I hit back button and then next button a couple times...
Didn't work for me on version 4.5.. This property "Processors" seems to not exist, and the property "_assetPipeline.Assets" is readonly... I'm still trying to get those javascripts not minified to debug a javascript behavior of onepagecheckout step, duplicating my script if I hit back button and then next button a couple times...
Hi chashikNop, thanks for your reply! Unfortunatelly this didn't help me either. All JS files are still requested and loaded minified. I also believe this issue deserves more attention from the nopCommerce team regardless of whether the workaround works.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.