-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#4852: Wrap IOrchardShellEvents in a work context #5738
#4852: Wrap IOrchardShellEvents in a work context #5738
Conversation
It works perfect, the problems has disappeared. |
I think we should try your change and revert this: ce630f9 And also revert all the other changes related to HttpContext resolution, including the Shape Tracing one in the dev branch. |
@sebastienros is there anything else i need to do, or are you guys going to be doing the reverting ? |
If you want to try to revert all the changes and ensure it still fixes the reported changes then I would be more than happy. On the 1.9.x branch. |
Actually, though, this problem (injecting ContentManager in Migrations) occurs in 1.8 on VS2015 too. My change fixes it on that as well, and since 1.8 obviously doesn't have any of the recent HttpContext changes, I'm pretty sure this is all we need. |
Would you be able to revert all these unnecessary changes then? //cc @jtkech |
I will try to add your change here, and also revert the fixes for the 3 issues you mentioned if I can't repro them. |
…ntext #4852: Wrap IOrchardShellEvents in a work context
This is a fix for #4852
This fixes some of the problems we are seeing relating to being unable to inject HttpContextBase during IOrchardShellEvents.
This has mainly been a problem when attempting to access ContentManager or site settings in Data Migrations, such as seen in #5305 #5490 #5528.
We seem to only be hitting the problem when Orchard is compiled under VS2015, but this is probably the correct behavior even when building under previous environments.