Disabling Workflow Module Causes Error


I was getting a weird issue with a new workflow I created using a prior custom form/rule combination to send e-mails. I will file a separate issue for that. However, what I thought to do was a) disable custom forms (to re-enable it) and b) disable workflows (to re-enable it). When I got to disabling the workflow module I got an error (shown below). This was brought up in this discussion. I didn't see that the OP filed an issue. Sorry if I missed it and this is a duplicate.

This error is mentioned in the post and looks like the one I experienced:
None of the constructors found with 'Orchard.Environment.AutofacUtil.DynamicProxy2.ConstructorFinderWrapper' on type 'Orchard.Security.Authorizer' can be invoked with the available services and parameters:
Cannot resolve parameter 'Orchard.Security.IAuthorizationService authorizationService' of constructor 'Void .ctor(Orchard.Security.IAuthorizationService, Orchard.UI.Notify.INotifier, Orchard.IWorkContextAccessor)'.


remesq wrote Nov 4, 2013 at 1:49 AM

I neglected to mention that this error caused a total site failure - I got the error on the front-end and in the admin section. I tried toying around with the DB to re-enable the workflow module but I just wound up rolling back to a backup of the site I had.

brporter wrote Nov 4, 2013 at 4:15 AM

This is impacting me. Has taken my entire site offline. Trying to desperately figure out what I must do to save several years worth of blog posts.

Does anyone have a workaround, of ANY kind?

remesq wrote Nov 4, 2013 at 12:59 PM

My workaround consisted of rolling back to a saved version of the database - I lost about an hour of work. Your situation may be different. I saw a post about modifying the SettingsShellStateRecord, etc. but can't find it right now. Try searching the discussions for that. I tried that fix but may have gotten it wrong (I have multi-tenants), so it didn't work for me. If you try it just backup before you do.

trentonadams wrote Nov 8, 2013 at 6:53 PM

Here is the related issue from the other thread: https://orchard.codeplex.com/workitem/20198

It's easy to reproduce from a clean install of 1.7.1 After initial setup, enable custom forms. Then disable Orchard.Forms. This will cause the error. I have not found a way to recover from this, other than rolling back the database and cleaning out the cache files.

I tried the SettingsShellStateRecord fix, basically setting the forms module and dependencies to "Up" but that didn't work.

sebastienros wrote Nov 8, 2013 at 8:42 PM

Fixed in changeset 322c433351dcedbc41aef8e7e83726f877b77537

sebastienros wrote Nov 8, 2013 at 8:43 PM

The issue was that Roles had a dependency on Workflows. I have refactored the module to move the Roles Activities into a different features, such that disabling Workflows won't disable Roles. I did the same with Comments.

2LM wrote Sep 6, 2014 at 12:50 PM

Is there also a fix for those that suffer from this bug and can't roll back to a backup?

sebastienros wrote Sep 8, 2014 at 6:15 PM

you can use the console app to re-enable the feature. In /bin start orchard.exe then type "feature enable Orchard.Workflows"