I have installed via nuget into umbraco 7.7.1. Can rebuild index no problem. However when I do backoffice search I get the following error:
)]}',
{"Message":"An error has occurred.","ExceptionMessage":"Could not load type 'Umbraco.Web.Models.ContentEditing.EntityTypeSearchResult' from assembly 'umbraco, Version=1.0.6471.23334, Culture=neutral, PublicKeyToken=null'.","ExceptionType":"System.TypeLoadException","StackTrace":" at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)\r\n at System.Reflection.RuntimeMethodInfo.getReturnType()\r\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.GetReturnType(MethodInfo methodInfo)\r\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.InitializeProperties(MethodInfo methodInfo)\r\n at System.Web.Http.Controllers.ReflectedHttpActionDescriptor..ctor(HttpControllerDescriptor controllerDescriptor, MethodInfo methodInfo)\r\n at System.Web.Http.Controllers.ApiControllerActionSelector.ActionSelectorCacheItem..ctor(HttpControllerDescriptor controllerDescriptor)\r\n at System.Web.Http.Controllers.ApiControllerActionSelector.GetInternalSelector(HttpControllerDescriptor controllerDescriptor)\r\n at System.Web.Http.Controllers.ApiControllerActionSelector.SelectAction(HttpControllerContext controllerContext)\r\n at System.Web.Http.ApiController.ExecuteAsync(HttpControllerContext controllerContext, CancellationToken cancellationToken)\r\n at System.Web.Http.Dispatcher.HttpControllerDispatcher._1.MoveNext()"}
Not sure if this due to this version of umbraco and ISearchableTree swapability?
So further digging it is due to ISearchableTree change. In the azuresearch code you have in BackOfficeAzureSearchApiController Search method that returns
Having same issue on a 7.10.4 site. Are you still maintaining this project? I will try to compile a fix if you are not maintaining.
Did some digging - and it looks like someone removed a type called: EntityTypeSearchResult - causing the compilation error when the service is invoked.
you will notice that the signature for SearchAll has changed (ln 112) from returing IEnumerable<EntityTypeSearchResult> to now to return IDictionary<string, TreeSearchResult>
Do I simply need to provide a new implementation of EntityTypeSearchResult or do I need to reimplement the SearchAll method?
backoffice search error
I have installed via nuget into umbraco 7.7.1. Can rebuild index no problem. However when I do backoffice search I get the following error:
Not sure if this due to this version of umbraco and ISearchableTree swapability?
Regards
Ismail
So further digging it is due to ISearchableTree change. In the azuresearch code you have in BackOfficeAzureSearchApiController Search method that returns
This is no longer there in 7.7.1.
Regards
Ismail
Thanks Ismail - we'll get this update in when we start working on a 7.7 site!
Hi, any update on this issue? I am currently facing the same problem. Thanks.
Having same issue on a 7.10.4 site. Are you still maintaining this project? I will try to compile a fix if you are not maintaining.
Did some digging - and it looks like someone removed a type called:
EntityTypeSearchResult- causing the compilation error when the service is invoked.The source is here: https://github.com/darrenferguson/UmbracoAzureSearch/blob/master/Moriyama.AzureSearch.Umbraco.Application/Controllers/BackOffice/BackOfficeAzureSearchApiController.cs
If you look at Umbracos implementation of the same Controller ( https://github.com/umbraco/Umbraco-CMS/blob/7ee510ed386495120666a78c61497f58ff05de8f/src/Umbraco.Web/Editors/EntityController.cs)
you will notice that the signature for
SearchAllhas changed (ln 112) from returingIEnumerable<EntityTypeSearchResult>to now to returnIDictionary<string, TreeSearchResult>Do I simply need to provide a new implementation of
EntityTypeSearchResultor do I need to reimplement theSearchAllmethod?Anyone have some pointers?
Hi, I'm investigating using this package with a 7.7.4 version site. I am facing the same issue as above.
Is there likely to be an update to this package? Thanks
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.