Error when upgrading to umbraco 7.2.2 and other issues
We have just tried to upgrade to Umbraco 7.2.2 right from 7.2.1 (not a big jump, though).
Optimus 1.2.1 was running just fine for the 7.2.1 version.
During the upgrade process, right after all manual file copies and merges of .config files, when browsing the site for the first time in order to finish the update, the process stalled. We could not get further than the page /umbraco/AuthorizeUpgrade?redir=%2finstall%2f%3fredir%3dtrue%26url%3dhttp...
The page AuthorizeUpgrade innerly requested the file /DependencyHandler.axd?s= which was throwing HTTP 500 Internal Server Errors. In ~/app_data/logs/UmbracoTraceLog.txt we could see errors like the following each time we tried to refresh the page:
2015-02-20 13:16:33,984 [46] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 48] An unhandled exception occurred System.InvalidOperationException: Esta operación no se admite en un URI relativo. en System.Uri.get_PathAndQuery() en ClientDependency.Core.CompositeFiles.Providers.BaseCompositeFileProcessingProvider.WritePathToStream(ClientDependencyType type, String path, HttpContextBase context, StreamWriter sw) en ClientDependency.Core.CompositeFiles.Providers.CompositeFileProcessingProvider.<>c__DisplayClass3.<CombineFiles>b__0(String s) en System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext() en System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext() en System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) en System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) en ClientDependency.Core.CompositeFiles.Providers.CompositeFileProcessingProvider.CombineFiles(String[] filePaths, HttpContextBase context, ClientDependencyType type, List`1& fileDefs) en ClientDependency.Core.CompositeFiles.CompositeDependencyHandler.ProcessRequestInternal(HttpContextBase context, String fileset, ClientDependencyType type, Int32 version, Byte[] outputBytes, OutputCachedPage page) en ClientDependency.Core.CompositeFiles.CompositeDependencyHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context) en System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() en System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
The only workaround we found to finish the upgrade to 7.2.2 was to disable the optimisations (setting debug="true" in web.config). After this change the upgrade was able to finish. However...
When we tried to set debug="false" back in web.config Umbraco backend stopped working again (the site contents were served, but the backend was not available because of this error). So we are running it now in debug="true" mode.
Another weird thing that happens when debug is enabled, that might help pinpoint the source of the error (or errors) are the following:
A. If, from the backend, we browse to Settings->Bundling->Scripts and click on any of the existing bundles, the background request to /App_Plugins/Optimus/Index?virtualPath=... fails with an HTTP 401 You must login to view this resource.
B. If we try to créate a new bundle, right clicking on Scripts (for instance, it fails for Styles too), and select + Create, the inner request made to /umbraco/create.aspx?nodeId=1&nodeType=scriptBundle&nodeName... returns with HTTP 500 Internal Server Error.
In this latter case, the error logged in UmbracoTraceLog.txt was:
2015-02-20 14:22:54,987 [30] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 57] An unhandled exception occurred System.Web.HttpUnhandledException (0x80004005): Se produjo una excepción de tipo 'System.Web.HttpUnhandledException'. ---> System.ArgumentException: The create dialog for "scriptBundle" does not match anything defined in the "~/umbraco/config/create/UI.xml". This could mean an incorrectly installed package or a corrupt UI file en umbraco.cms.presentation.Create.OnLoad(EventArgs e) en System.Web.UI.Control.LoadRecursive() en System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) en System.Web.UI.Page.HandleError(Exception e) en System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) en System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) en System.Web.UI.Page.ProcessRequest() en System.Web.UI.Page.ProcessRequest(HttpContext context) en ASP.umbraco_create_aspx.ProcessRequest(HttpContext context) en c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\6ffd8b37\ea6ae51a\App_Web_create.aspx.5f2dec3.lfwndyig.0.cs:línea 0 en System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() en System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Since this is not the default Umbraco installation config, have tried to change it back to use the default Umbraco UsersMembershipProvider so that instead of logging in with an Active Directory user, we login with a regular Umbraco user.
It does not make any difference. The errors still persist.
I hope you (or any other developer) could have a look into it and fix this issue.
Hi have the same issue on a fresh install of Optimus 1.2.1 AFTER upgrading Umbraco 7.2.1 to 7.2.2...
Any workaround so far ?
I Know for sure that the bundling works with Umbraco 7.2.1, but as soon as i install it a fresh new instance of Umbraco 7.2.2, it's broken... if that info can help :)
I also have this error "401 You must login to view this resource." with Umbraco 7.2.2 and Optimus 1.2.1.
When i just updated my Umbraco 7.2.0 to 7.2.2 Optimus (that was installed before update) was working well - i have edited my css bundle, saved, changes applied. But, after some time, Optimus became unusable - i can't open bundles and see this error in server answer.
I also would like to know how to repair, if somebody knows.
I don't have Optimus, but the same thing happened to me while doing a manual update from 7.1.8 to 7.2.2. I changed the web.config to debug=true so the upgrade would work. Once the upgrade was completed, I set debug=false and got the following error in the developer console (Chrome) and the backend wouldn't load:
Uncaught ReferenceError: UmbClientMgr is not defined
I too am experiencing a similar issue as Søren, as in my bundle returns a 404 status, and I notice the bundle isn't getting the querystring parameter added.
Umbraco 7.2.4 installed via NuGet
Using Optimus core and providers version 1.3.0 as I downloaded yesterday
Tried both with and without suggested Stackoverflow BundleModule
Yes, there is something. This is what is in the log following i) stop and start the app pool; and ii) visit the page that should have the bundle on:
2015-03-27 13:10:36,606 [7] INFO Umbraco.Core.UmbracoApplicationBase - [Thread 10] Application shutdown. Reason: HostingEnvironment
2015-03-27 13:11:06,018 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Determining hash of code files on disk
2015-03-27 13:11:06,047 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Hash determined (took 16ms)
2015-03-27 13:11:06,060 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of umbraco.interfaces.IApplicationStartupHandler
2015-03-27 13:11:06,095 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of umbraco.interfaces.IApplicationStartupHandler, found 43 (took 33ms)
2015-03-27 13:11:06,243 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter
2015-03-27 13:11:06,246 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter, found 0 (took 2ms)
2015-03-27 13:11:06,246 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of Umbraco.Core.PropertyEditors.IPropertyValueConverter
2015-03-27 13:11:06,248 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.PropertyEditors.IPropertyValueConverter, found 19 (took 1ms)
2015-03-27 13:11:06,284 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of Umbraco.Web.Mvc.SurfaceController
2015-03-27 13:11:06,284 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Web.Mvc.SurfaceController, found 4 (took 0ms)
2015-03-27 13:11:06,285 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of Umbraco.Web.WebApi.UmbracoApiController
2015-03-27 13:11:06,289 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Web.WebApi.UmbracoApiController, found 45 (took 3ms)
2015-03-27 13:11:06,361 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of Umbraco.Core.Media.IThumbnailProvider
2015-03-27 13:11:06,362 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.Media.IThumbnailProvider, found 3 (took 0ms)
2015-03-27 13:11:06,362 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Starting resolution types of Umbraco.Core.Media.IImageUrlProvider
2015-03-27 13:11:06,363 [7] INFO Umbraco.Core.PluginManager - [Thread 1] Completed resolution of types of Umbraco.Core.Media.IImageUrlProvider, found 1 (took 0ms)
2015-03-27 13:11:07,865 [7] INFO Umbraco.Web.Search.ExamineEvents - [Thread 1] Initializing Examine and binding to business logic events
2015-03-27 13:11:08,079 [7] INFO Umbraco.Web.Search.ExamineEvents - [Thread 1] Adding examine event handlers for index providers: 3
2015-03-27 13:11:08,168 [7] ERROR System.Web.Optimization.BundleCollection - [Thread 1] Error adding bundles: System.IO.FileLoadException: Could not load file or assembly 'JavaScriptEngineSwitcher.Core, Version=1.2.0.0, Culture=neutral, PublicKeyToken=c608b2a8cc9e4472' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'JavaScriptEngineSwitcher.Core, Version=1.2.0.0, Culture=neutral, PublicKeyToken=c608b2a8cc9e4472'
at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
at System.Reflection.RuntimeConstructorInfo.get_Signature()
at System.Reflection.RuntimeConstructorInfo.GetParametersNoCopy()
at System.RuntimeType.FilterApplyMethodBase(MethodBase methodBase, BindingFlags methodFlags, BindingFlags bindingFlags, CallingConventions callConv, Type[] argumentTypes)
at System.RuntimeType.FilterApplyConstructorInfo(RuntimeConstructorInfo constructor, BindingFlags bindingFlags, CallingConventions callConv, Type[] argumentTypes)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at BundleTransformer.Core.Utilities.Utils.CreateInstanceByFullTypeName[T](String fullTypeName)
at BundleTransformer.Core.Assets.AssetContextBase.GetTranslatorInstance(String translatorName)
at BundleTransformer.Core.Assets.AssetContextBase.GetDefaultTranslatorInstances()
at BundleTransformer.Core.Transformers.StyleTransformer..ctor(IMinifier minifier, IList`1 translators, IList`1 postProcessors, String[] ignorePatterns, CoreSettings coreConfig)
at BundleTransformer.Core.Transformers.StyleTransformer..ctor(IMinifier minifier, IList`1 translators, IList`1 postProcessors, String[] ignorePatterns)
at BundleTransformer.Core.Transformers.StyleTransformer..ctor()
at Optimus.BundleConfig.RegisterBundles(BundleCollection bundles)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
System.IO.FileLoadException: Could not load file or assembly 'JavaScriptEngineSwitcher.Core, Version=1.2.0.0, Culture=neutral, PublicKeyToken=c608b2a8cc9e4472' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'JavaScriptEngineSwitcher.Core, Version=1.2.0.0, Culture=neutral, PublicKeyToken=c608b2a8cc9e4472'
at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
at System.Reflection.RuntimeConstructorInfo.get_Signature()
at System.Reflection.RuntimeConstructorInfo.GetParametersNoCopy()
at System.RuntimeType.FilterApplyMethodBase(MethodBase methodBase, BindingFlags methodFlags, BindingFlags bindingFlags, CallingConventions callConv, Type[] argumentTypes)
at System.RuntimeType.FilterApplyConstructorInfo(RuntimeConstructorInfo constructor, BindingFlags bindingFlags, CallingConventions callConv, Type[] argumentTypes)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at BundleTransformer.Core.Utilities.Utils.CreateInstanceByFullTypeName[T](String fullTypeName)
at BundleTransformer.Core.Assets.AssetContextBase.GetTranslatorInstance(String translatorName)
at BundleTransformer.Core.Assets.AssetContextBase.GetDefaultTranslatorInstances()
at BundleTransformer.Core.Transformers.StyleTransformer..ctor(IMinifier minifier, IList`1 translators, IList`1 postProcessors, String[] ignorePatterns, CoreSettings coreConfig)
at BundleTransformer.Core.Transformers.StyleTransformer..ctor(IMinifier minifier, IList`1 translators, IList`1 postProcessors, String[] ignorePatterns)
at BundleTransformer.Core.Transformers.StyleTransformer..ctor()
at Optimus.BundleConfig.RegisterBundles(BundleCollection bundles)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
2015-03-27 13:11:08,745 [7] INFO Umbraco.Web.UmbracoModule - [Thread 8] Setting OriginalRequestUrl: test.local:80/umbraco
2015-03-27 13:11:08,838 [7] INFO umbraco.content - [Thread 8] Loading content from disk cache...
2015-03-27 13:11:08,971 [7] INFO Umbraco.Core.PluginManager - [Thread 8] Starting resolution types of Umbraco.Core.Persistence.Mappers.BaseMapper
2015-03-27 13:11:08,972 [7] INFO Umbraco.Core.PluginManager - [Thread 8] Completed resolution of types of Umbraco.Core.Persistence.Mappers.BaseMapper, found 23 (took 0ms)
2015-03-27 13:11:09,695 [7] INFO Umbraco.Core.PluginManager - [Thread 8] Starting resolution types of Umbraco.Core.PropertyEditors.IParameterEditor
2015-03-27 13:11:09,697 [7] INFO Umbraco.Core.PluginManager - [Thread 8] Completed resolution of types of Umbraco.Core.PropertyEditors.IParameterEditor, found 75 (took 1ms)
Ok that was the same error I was having :) could you check if you have JavaScriptEngineSwitcher.Core.dll in the bin directory and which version it is (you can see the version when you check the properties of the assembly)
I've tried setting this up again, so I have both a VS2013 ASP.NET Web Application Empty, and a VS2013 with a VS2012 empty MVC4, and both are experiencing this issue. What VS project template are you using Tim?
well create a couple of css files and see if you can bundle and output the bundle now (if you have the started kit installed you can just bundle the ones from the starter kit)
I'm so happy I could swear... yep, that works in both versions of the site.
So to recap... we need to ensure we install Optimus.Core v1.3.0, and ensure the assembly binding redirect, and the BundleModule are in place in web.config.
I'm going to work through this again just to make sure. Give me ten min or so...
Error when upgrading to umbraco 7.2.2 and other issues
We have just tried to upgrade to Umbraco 7.2.2 right from 7.2.1 (not a big jump, though).
Optimus 1.2.1 was running just fine for the 7.2.1 version.
During the upgrade process, right after all manual file copies and merges of .config files, when browsing the site for the first time in order to finish the update, the process stalled. We could not get further than the page /umbraco/AuthorizeUpgrade?redir=%2finstall%2f%3fredir%3dtrue%26url%3dhttp...
The page AuthorizeUpgrade innerly requested the file /DependencyHandler.axd?s= which was throwing HTTP 500 Internal Server Errors. In ~/app_data/logs/UmbracoTraceLog.txt we could see errors like the following each time we tried to refresh the page:
The only workaround we found to finish the upgrade to 7.2.2 was to disable the optimisations (setting debug="true" in web.config). After this change the upgrade was able to finish. However...
When we tried to set debug="false" back in web.config Umbraco backend stopped working again (the site contents were served, but the backend was not available because of this error). So we are running it now in debug="true" mode.
Another weird thing that happens when debug is enabled, that might help pinpoint the source of the error (or errors) are the following:
A. If, from the backend, we browse to Settings->Bundling->Scripts and click on any of the existing bundles, the background request to /App_Plugins/Optimus/Index?virtualPath=... fails with an HTTP 401 You must login to view this resource.
B. If we try to créate a new bundle, right clicking on Scripts (for instance, it fails for Styles too), and select + Create, the inner request made to /umbraco/create.aspx?nodeId=1&nodeType=scriptBundle&nodeName... returns with HTTP 500 Internal Server Error.
In this latter case, the error logged in UmbracoTraceLog.txt was:
I just installed a brand new 7.2.2. site, and added Optimus.
When creating a new bundle i get the 401.0
You must login to view this resource.
:-(
Posted about it here:
http://www.nibble.be/?p=237
Looks like the 401 is due to this error https://our.umbraco.org/forum/umbraco-7/developing-umbraco-7-packages/55676-Securing-a-back-office-MVC-controller?p=0#comment208937 in 7.2.2 you get this when there is no member logged in so probably missing something
Just for testing and for adding a little more information about this issue:
We are using ADUsersMembershipProvider as DefaultBackofficeProvider (see https://our.umbraco.org/wiki/how-tos/membership-providers/active-directory-membership-provider ).
Since this is not the default Umbraco installation config, have tried to change it back to use the default Umbraco UsersMembershipProvider so that instead of logging in with an Active Directory user, we login with a regular Umbraco user.
It does not make any difference. The errors still persist.
I hope you (or any other developer) could have a look into it and fix this issue.
Thanks for you support.
Hi have the same issue on a fresh install of Optimus 1.2.1 AFTER upgrading Umbraco 7.2.1 to 7.2.2...
Any workaround so far ?
I Know for sure that the bundling works with Umbraco 7.2.1, but as soon as i install it a fresh new instance of Umbraco 7.2.2, it's broken... if that info can help :)
I also have this error "401 You must login to view this resource." with Umbraco 7.2.2 and Optimus 1.2.1.
When i just updated my Umbraco 7.2.0 to 7.2.2 Optimus (that was installed before update) was working well - i have edited my css bundle, saved, changes applied. But, after some time, Optimus became unusable - i can't open bundles and see this error in server answer.
I also would like to know how to repair, if somebody knows.
Seems like this has to change , so umbraco knows it's a backoffice route
https://github.com/TimGeyssens/BundlingAndMinificationForTheMasses/blob/master/BundlingAndMinificationForTheMasses/App_Start/RouteConfig.cs
So it needs to live in /umbraco/backoffice instead of app_plugins
I don't have Optimus, but the same thing happened to me while doing a manual update from 7.1.8 to 7.2.2. I changed the web.config to debug=true so the upgrade would work. Once the upgrade was completed, I set debug=false and got the following error in the developer console (Chrome) and the backend wouldn't load:
Uncaught ReferenceError: UmbClientMgr is not defined
Will there be an update for this awesome package soon? Would like to upgrade to 7.2.X. Thanks anyway!
Yeah new version will be out this month, staring the necessary work today
That is awesome Tim. This package really rocks! Thanks!
New version is out https://our.umbraco.org/projects/developer-tools/optimus :)
Might have found anoher issue, when your bundles throw a 404, then just do the following update to your web.config
http://stackoverflow.com/a/25565327
That was quick! Thanks Tim. H5YR!
I am running a fresh install of Umbraco 7.1.4 and a fresh install of the latest Optimus package, but I still get the 404 errors on the bundles.
I have tried adding code from the example on Stackoverflow:
This didn't work though. What can I try next?
I too am experiencing a similar issue as Søren, as in my bundle returns a 404 status, and I notice the bundle isn't getting the querystring parameter added.
In my case this did the trick
But sounds like yuo already tried that, I am running from webmatrix, will give it a go from vs
Hi Tim,
Thanks for the quick response!
Yeah, I've tried both with and without the BundleModule code. I forgot to mention it is a fresh install with the following NuGet packages:
although I've tried without these packages and I get the same result.
Cheers,
Chris
@chris thanks for the extra details, also mind sharing how you called your bundle? Then I can setup the same environment
Hmm made it work by copying over the web.config from my webmatrix instance, doing a diff now to see what was missing
Hi Tim,
I added my bundle to
App_Plugins\Optimus\Config\bundles.config
using:and I use
@Styles.Render("~/bundles/siteCss")
in my template to call it./css/less/bwt-site.less
currently contains:Cheers,
Chris
Ok found the fix, in the web.config find
<dependentAssembly>
<assemblyIdentityname="JavaScriptEngineSwitcher.Core" publicKeyToken="c608b2a8cc9e4472" culture="neutral" />
<bindingRedirectoldVersion="0.0.0.0-1.1.3.0" newVersion="1.1.3.0" />
</dependentAssembly>
and change to
<dependentAssembly>
<assemblyIdentityname="JavaScriptEngineSwitcher.Core" publicKeyToken="c608b2a8cc9e4472" culture="neutral" />
<bindingRedirectoldVersion="0.0.0.0-1.2.4.0" newVersion="1.2.4.0" />
</dependentAssembly>
please let me know if that fixes the issue
Hi Tim,
I've changed:
to:
and I still get they same error. I've tried restarting the app pool and rebuilding.
Anything in the umbraco logs?
Hi Tim,
Yes, there is something. This is what is in the log following i) stop and start the app pool; and ii) visit the page that should have the bundle on:
Ok that was the same error I was having :) could you check if you have JavaScriptEngineSwitcher.Core.dll in the bin directory and which version it is (you can see the version when you check the properties of the assembly)
Hi Tim – I can see the JavaScriptEngineSwitcher.Core.dll in the bin directory, and right clicking > properties shows its version to be 1.2.4.0.
Well in that case the assembly redirect should do the trick... not sure why it's not kicking in in your case
I've tried setting this up again, so I have both a VS2013 ASP.NET Web Application Empty, and a VS2013 with a VS2012 empty MVC4, and both are experiencing this issue. What VS project template are you using Tim?
Could you try optimus without installing any additional providers and then adding
<removename="BundleModule"/>
<addname="BundleModule" type="System.Web.Optimization.BundleModule"/>
to your web.config (system.webServer/modules)
and see how that behaves (so no less for the time being)
Sure. Fresh install, this is what I've done:
<remove name="BundleModule" /><add name="BundleModule" List itemtype="System.Web.Optimization.BundleModule" />
to web.configWhat would you like be to try?
well create a couple of css files and see if you can bundle and output the bundle now (if you have the started kit installed you can just bundle the ones from the starter kit)
Created a bundle with:
Called bundle with
@Styles.Render("~/bundles/siteCss")
Content of
/css/less/bwt-TEST.css
is:Resulting page has a red background, so it looks like the css bundling is working.
Ok so now try to install the less provider https://our.umbraco.org/FileDownload?id=14464 and update the assembly redirect
Installed the Less provider you linked to, and added the assembly redirect:
bundles.config
now looks like this:In my template I call the CSS bundle (not the less one) with:
When I view the page the CSS bundle fails with a 404 error.
and I guess you have the same error in the log again?
Yes, same error.
Yeah in that case the assembly redirect would fix it, mind sharing your web.config
Here it comes:
seems like you have a duplicate oldversion
so this
I'm so happy I could swear... yep, that works in both versions of the site.
So to recap... we need to ensure we install Optimus.Core v1.3.0, and ensure the assembly binding redirect, and the BundleModule are in place in web.config.
I'm going to work through this again just to make sure. Give me ten min or so...
Yup, we'll release a 1.3.1 shortly where the installer takes care of this so no more manual steps are needed but for now those are the steps needed
That all worked a treat.
Thanks for all your help today Tim, you're a star. I owe you a pint for today's efforts.
h5yr
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.