Hi
this is an issue we have faced lately, when you use AppUser which is used to add new properties to IdentityUser throws exception in different modules. I suggest you to use IdentityUser instead of AppUser.
I think you need to configure Identity Server for front channel logout. I'll share you a link which is similar to your requirement https://support.aspnetzero.com/QA/Questions/9809/How-do-I-implement-logout-all-client-with-Identity-Server-4#answer-7d351498-32de-92e6-a92b-39f8bf30a871
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
v4.3.2 comes Fiday.
rick it's not supported Blazor. it'll be implemented on v4.4
the application template comes preconfigured to run Identity Server on your local environment. you need to change the local URLs to your production addresses. check the IdentityServerClientRedirectUris
table, you'll see the localhost addresses, replace them with your prod addresses
because making property navigation is not best practise for a module. suite is designed to support both modules and app templates. but easy crm is not a module. if you are not working on a module template, you can change the final output of Suite to support ICollection<OtherEntity> OtherEntities
is it duplicate of https://support.abp.io/QA/Questions/1289/problem-with-navigation-properties-in-abp-suite?
ok. I'll check it again
ICollection<OrderLine> OrderLines
Product Product { get; set; }
these are not navigation properties
There are 2 razor pages used to change the register page.
1- Copy the Register.cshtml to Pages > Account
folder of your web project.
2- Copy the Default.cshtml to Themes > Lepton > Layouts > Account
folder of your web project.
https://gist.github.com/ebicoglu/bb28666a892646b245b2a525d5760bb7