You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using weboptimizer on the Umbraco CMS to bundle css and js files. On the CMS, the customer can use widgets and can have multiple instances of the same widget on the same page. For exemple he can use 3 instance of an Image Gallery widget.
If we include the bundle in the [Image Gallery] widget view using the tag helper : <link rel="stylesheet" href="/css/bundle.css" />, the tag will be repeated each time the widget is used in the page which seems not optimal.
To avoid this we could integrate all bundles once on the root view but that means there will be potentially a lot of unused css/js on the page.
We also tried to use the method AddFileVersionToPath(string path) to include the bundle by code if required but it seems that this method doesn't work when using the bundle path.
Any hint would be welcome. I have the feeling that we took a wrong turn somewhere.
The text was updated successfully, but these errors were encountered:
We are using weboptimizer on the Umbraco CMS to bundle css and js files. On the CMS, the customer can use widgets and can have multiple instances of the same widget on the same page. For exemple he can use 3 instance of an Image Gallery widget.
If we include the bundle in the [Image Gallery] widget view using the tag helper :
<link rel="stylesheet" href="/css/bundle.css" />
, the tag will be repeated each time the widget is used in the page which seems not optimal.To avoid this we could integrate all bundles once on the root view but that means there will be potentially a lot of unused css/js on the page.
We also tried to use the method AddFileVersionToPath(string path) to include the bundle by code if required but it seems that this method doesn't work when using the bundle path.
Any hint would be welcome. I have the feeling that we took a wrong turn somewhere.
The text was updated successfully, but these errors were encountered: