Hi Valerie,

I think the below is a bit hacky but you could always ensure that you have an Umbraco Context in your event:

// Ensure that we have an umbraco context
// See: http://issues.umbraco.org/issue/U4-5445#comment=67-16121
if (UmbracoContext.Current == null)
{
    UmbracoContext.EnsureContext(
        context,
        ApplicationContext.Current,
        new WebSecurity(context, ApplicationContext.Current),
        true);
}

// Create a new helper
var umbracoHelper = new UmbracoHelper(UmbracoContext.Current);

Thanks, Dan.

Hi Dan,

What is "context" in this example? I tried new HttpContextWrapper(HttpContext.Current) but HttpContext.Current is null.

Sorry. I should have mentioned the context variable is the current request.

I think without have HttpContent.Current you are going to struggle getting UmbracoContext to work. I believe UmbracoContext relies on having a request. Also the GatheringNodeData runs on a separate thread, not the main thread so HttpContent.Current will always be null.

I tried looking for a solution and I can't find one I'm afraid.

Thanks, Dan.

Thanks anyway Dan!

As stated by Shannon:

UmbracoContext.Current is set during the init of a web request so if you are running outside of a web request.. like with examine it is probably running async, so it will be null. https://groups.google.com/forum/#!topic/umbraco-dev/-xto6IIPXrA

You can use the Services if you need to look up properties from other nodes:

var contentService = ApplicationContext.Current.Services.ContentService;

Unfortunately the content service returns IContent which yet another different interface :(

I know, but you can do already a lot with it.

Just pay attention because the services are DB lookups and are much more slowly than the IPublishedContent lookups. Because the GatheringNodeData is only triggered when the node is being index, that is probably ok.

I stumbled over the IPublishedContent by doing:

var context = new HttpContext(new HttpRequest("", "http://mysite.local/", ""), new HttpResponse(null));

UmbracoContext.EnsureContext(new HttpContextWrapper(context), ApplicationContext.Current);

var content = new UmbracoHelper(UmbracoContext.Current).TypedContent(e.NodeId);

Will there be negative implications to doing this with a mock httpcontext? It does indeed return the correct IPublishedContent object.

If you are interested, here is the solution for v7.3

        if (UmbracoContext.Current == null)
        {
            var dummyHttpContext = new HttpContextWrapper(new HttpContext(new SimpleWorkerRequest("blah.aspx", "", new StringWriter())));
            UmbracoContext.EnsureContext(
                dummyHttpContext,
                ApplicationContext.Current,
                new WebSecurity(dummyHttpContext, ApplicationContext.Current),
                UmbracoConfig.For.UmbracoSettings(),
                UrlProviderResolver.Current.Providers,
                false);
        }

Hi Valerie,

This link http://staheri.com/my-blog/2015/march/custom-examine-indexing-using-umbraco-cache/ helped me when I had the same requirement.

It works a treat and seriously speeds up my code when setting up data for my custom index.

HTH

Ver

I had problems with the UmbracoContext.Current being null using the solution detailed in the staheri.com link provided by @Veronica, even though that link says it's not an issue for them. Although I did inherit from ApplicationEventHandler rather than IApplicationEventHandler (not sure if that makes much difference).

As a workaround I added the following to the start of the GatheringNodeData event handler (Umbraco 7.2.4, similar to @Lee's v7.3 code, above):

if (UmbracoContext.Current == null)
                {
                    var dummyContext = new HttpContextWrapper(new HttpContext(new SimpleWorkerRequest("/", string.Empty, new StringWriter())));
                    UmbracoContext.EnsureContext(
                        dummyContext,
                        ApplicationContext.Current,
                        new WebSecurity(dummyContext, ApplicationContext.Current),
                        false);
                }

More info here

is working on a reply...