We are using Umbraco 9.5 and every thing was running fine for a long time, but starting from today (2022-10-2) we are suffering from a strange error in Backoffice (in local PC only, however it's working fine on the IIS hosting) with the Backoffice API request "umbraco/backoffice/umbracoapi/entity/GetAncestors?id="
Do any one faced an unstable error with endpoint Controllers.EntityController.GetResultForAncestors ?
Exception Details:
System.NotSupportedException, System.Private.CoreLib, Version=5.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e: The Umbraco.Cms.Web.BackOffice.Controllers.EntityController does not currently support data for the type Language
Stacktrace
at Umbraco.Cms.Web.BackOffice.Controllers.EntityController.GetResultForAncestors(Int32 id, UmbracoEntityTypes entityType, FormCollection queryStrings)
at lambdamethod1162(Closure , Object , Object[] )
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.1(ControllerActionInvoker invoker)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.
We have detected the the reason behind our issue, it was the rewriting rules, once we added new rule to neglect BackOffice ULRs, the Backoffice worked fine.
The Umbraco.Cms.Web.BackOffice.Controllers.EntityController does not currently support data for the type Language
Hello All,
We are using Umbraco 9.5 and every thing was running fine for a long time, but starting from today (2022-10-2) we are suffering from a strange error in Backoffice (in local PC only, however it's working fine on the IIS hosting) with the Backoffice API request "umbraco/backoffice/umbracoapi/entity/GetAncestors?id="
Do any one faced an unstable error with endpoint
Controllers.EntityController.GetResultForAncestors?Exception Details:
Stacktrace
We have detected the the reason behind our issue, it was the rewriting rules, once we added new rule to neglect BackOffice ULRs, the Backoffice worked fine.
is working on a reply...