أنشطة "gilina.mcbride"

This work around solved the issue. Thank you!

I sent a zipped folder through wetransfer. It wouldn't upload a non zipped one. Hopefully you'll be able to open. I have also included information two comments above if that would help any.

I've emailed a few things in the hopes one of them works. I have also attached two screenshots of how we've structured our dtos that are causing the issue, and a gif so you can see that when I create or edit a contact that includes the nested dto the nested items aren't included in the audit log, the only change that shows is the one made to email which is on the contactdto not the paymentsettingsdto. The others aren't included in the log which is the issue were trying to solve for.

Dtos:

gif:

Ok I sent a shared link, hopefully you can open that one. Thanks!

I just sent you an example to your email. Thank you!

Thank you!

• ABP Framework version: v7.3.0
• UI Type: MVC
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Problem:

We have a few entities that have nested objects. For example Processing Configuration entity has Payment settings object: public PaymentSettings PaymentSettings { get; set; } = new PaymentSettings(); However these are not separate tables in the database. The properties are on the processing configuration table as processingConfiguration.paymentSettings.FieldName. The issue we're having is that when we do audit logging for the entity, if we change a property that is in a nested object it isn't logging properly (see screenshot). It sees there is a change/update, but not what property has been changed or any other information. Is there a work around for this issue?

• ABP Framework version: v8.1.1 tested - using 7.3.0 for application
• UI Type: MVC
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Issue:
  • If a user is marked to force password change on the next log in when they log in even if the wrong password is entered it still takes them to the password change page rather than saying their username or password is incorrect first.
• Steps to reproduce the issue:
  • Mark user as force password change and then log out. Log in as that user with the incorrect password and you will still be taken to the change password page. This is happening in our application and a new abp app I created from scratch with the latest version to test. See gif attached logging in with an incorrect password.