I get some strange behaviour after deploying my website.
In VisualStudio everything works fine. When copying the files and the database to my hoster I get MerchelloContext is null on the frontend and the merchello section doesn't work at all and I get error messages.
at Umbraco.Web.Trees.ApplicationTreeExtensions.TryLoadFromControllerTree(ApplicationTree appTree, String id, FormDataCollection formCollection, HttpControllerContext controllerContext)
at Umbraco.Web.Trees.ApplicationTreeController.<GetRootForSingleAppTree>d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Umbraco.Web.Trees.ApplicationTreeController.<GetApplicationTrees>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()
Can you try moving the merchello.config file to /Config and then opening your web.config and changing the configSource for the merchello location and see if that changes anything?
sorry for not pinging on twitter.
Was quite busy.
I have an interesting fact for you.
In my not working solution I first installed merchello from nuget and afterwards the packages (as nuget doesn't setup everything correctly).
Thats the solution which fails after deployment.
Then I made a second solution in which I firstly installed the packages and then the nuget ones. With that solution everything works after deploy.
I see and that makes sense. The NuGet package we have out is really only viable to support libraries as it only contains the dlls and cannot run the package actions to configure Merchello.
I've spent a good deal of time trying to figure out a way to get Merchello to run without Package Actions so we can do this and unfortunately it won't be available until version 3 as it will require some some of the fundamental pieces to be refactored as it depends on quite a few Umbraco internals. The good news is I believe I have a solution to this and have been pecking at it in my spare time and should be there for the Umbraco V8 compatible version =)
merchello not working after deploy
Hi,
I get some strange behaviour after deploying my website. In VisualStudio everything works fine. When copying the files and the database to my hoster I get MerchelloContext is null on the frontend and the merchello section doesn't work at all and I get error messages.
Anyone got that behaviour before?
Regards David
Edit: using Umbraco 7.5.2 and Merchello 2.2.0
Here is the stacktrace of the error I'm getting:
I just saw this issue yesterday http://issues.umbraco.org/issue/U4-8650
Can you try moving the merchello.config file to /Config and then opening your web.config and changing the configSource for the merchello location and see if that changes anything?
Test local first of course =)
Hi Rusty,
tested it but sadly tha doesn't make a difference :(
Regards David
Hey David - would you mind sending me a ping on twitter so we can DM about the deploy process?
Hey Rusty,
sorry for not pinging on twitter. Was quite busy. I have an interesting fact for you.
In my not working solution I first installed merchello from nuget and afterwards the packages (as nuget doesn't setup everything correctly). Thats the solution which fails after deployment.
Then I made a second solution in which I firstly installed the packages and then the nuget ones. With that solution everything works after deploy.
Strange behaviour.
Regards David
I see and that makes sense. The NuGet package we have out is really only viable to support libraries as it only contains the dlls and cannot run the package actions to configure Merchello.
I've spent a good deal of time trying to figure out a way to get Merchello to run without Package Actions so we can do this and unfortunately it won't be available until version 3 as it will require some some of the fundamental pieces to be refactored as it depends on quite a few Umbraco internals. The good news is I believe I have a solution to this and have been pecking at it in my spare time and should be there for the Umbraco V8 compatible version =)
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.