Console error saving resctrictions for single users
I found an issue when applying restriction for a single member to media.
When I click on save, this cause a console error:
angular.js:15635 Possibly unhandled rejection: {"data":{"ExceptionMessage":"Object reference not set to an instance of an object.","ExceptionType":"System.NullReferenceException, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e","StackTrace":" at MediaProtect.Web.Controllers.MediaProtectDialogApiController.Validate(DialogModel model)\r\n at lambda_method2463(Closure , Object , Object[] )\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()\r\n--- End of stack trace from previous location ---\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()\r\n--- End of stack trace from previous location ---\r\n at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker."}
Console error saving resctrictions for single users
I found an issue when applying restriction for a single member to media. When I click on save, this cause a console error:
How can I resolve?
Hi,
What version of Media protect and Umbraco are you using?
MediaProtect 9.0 Umbraco 9.2
I also have the same problem (same versions)
Hi,
Sorry for the delay. This was indeed a bug and should be fixed in the 9.0.1 release I just uploaded.
Hope this helps,
Richard
is working on a reply...