Aktivity „talhazengin“

Hi @liangshiwei,

I sent you a mail. I did a small demo application. Did you get the email?

Thanks.

Nope optimistic concurrency failure again. I tried many usage combination of UOW. Transactional UOW etc. Maybe i need an example project.

Hi @armanozak, I don't know what is the difference.

• ABP Framework version: v2.9.0
• UI type: Angular
• Identity Server Seperated (Angular): yes
• Exception message and stack trace: AbpIdentityResultException, AbpDbConcurrencyException, DbUpdateConcurrencyException
• Steps to reproduce the issue:

Hello,

I am trying to customize IdentityUserManager without success.

I wanted to update my custom User Entity properties after User created.

But that code gives DbConcurrency Errors.

I wanted to handle(EfCore https://docs.microsoft.com/en-us/ef/core/saving/concurrency) the exception but could not catch any exception.

Any advice is helpful, thanks.

What can we say about this error?

• ABP Framework version: v2.9.0
• UI type: Angular
• UI version: v2.9.0
• Identity Server Seperated (Angular): yes
• Steps to reproduce the issue:

If i check "Update Email Enabled" and after click Save. I can't succesfully change my email from Personal Settings page.

But if i don't check it and after click save, i can succesfully change my email from Personal Settings page.

So this settings works reverse and faulty.

• ABP Framework version: v2.9.0
• UI type: Angular
• UI version: v2.9.0
• Identity Server Seperated (Angular): yes
• Steps to reproduce the issue:

Verify gives server error.

• ABP Framework version: v2.9.0
• UI type: Angular
• UI version: v2.9.0
• Identity Server Seperated (Angular): yes
• Steps to reproduce the issue:

SEARCH WORKS IN FIRST PAGE

SEARCH NOT WORKS IN SECOND PAGE

• ABP Framework version: v2.9.0
• UI type: Angular
• UI version: v2.9.0
• Identity Server Seperated (Angular): yes
• Steps to reproduce the issue:

Error or Warning Headers Uses English but Localized Language is Different (Turkish for example).

Yeah, admin needs to have Organization-Units permissions. But how could I have known? Anyway this is fixed.