hi
You can check this https://abp.io/support/questions/9777/AccountLogout-400-response-code---After-upgrading-from-822-to-911#answer-3a1bd776-69af-aee5-4dd0-b040e3923d16
Thanks.
Thank you for your solution. 👍
hi
What error/exception did you get now?
Thanks.
hi
We need the entity tracking feature when we update an entity. see https://learn.microsoft.com/en-us/ef/core/change-tracking/
You can try to disable it in MyEfCoreIdentityUserRepository.cs when querying entities.
The solution is:
So you can either prevent assigning too many organzation to a user or modify the Identity module code to avoid loading all navigation entities explicitly. Then, query all entities at once as needed and tell EF Core not to track them.
https://abp.io/docs/latest/framework/architecture/domain-driven-design/repositories#read-only-repositories https://abp.io/docs/latest/framework/architecture/domain-driven-design/repositories#read-only-repositories-behavior-in-entity-framework-core
hi
Could you please share the steps to reproduce the issue in a new template project?
Thanks.
hi
The shared file and screenshot contain client-identifying information (namespaces in code, name in screenshot) and I ask you to please edit your post and remove those.
Removed.
Can you help me understand why this edit is necessary? Since this is an override, I would expect the base class to already handle this.
Because you use the new keyword to override thePostInput, the base class can't access your new variable.
Thanks.