Activities of "christophe.baille"

1- run the application

2- Click login button

3- Change language, nothing happens

It still doesn't work:

I login in english, then go to MVC blogging view --> I reach blogging view in english: OK, it works now, it was not before

I login in Finnish, then go to MVC blogging view --> I reach blogging view in Finnish: OK, it works now, it was not before

I login in english, I then change language to finnish after login from my Angular UI, then go to MVC blogging view --> I reach blogging view in english: KO, shoud be in Finnish

I login in Finnish, I then change language to english after login from Angular UI, then go to MVC blogging view --> I reach blogging view in english: KO, shoud be in english

I just tried with a new solution 4.4, the issue is still here

No,

I am trying on the project I am developing on, but it should work after updating no?

I just updated to the version 4.4 but it still exactly the same, it doesn't work

Thanks, I will try it then

Thanks I did notice that. However I saw a warning about having some errors using ABP Suite code generation, asking to wait next version. I asked, which version we need to wait?

Hi upgraded to version 4.4 and still have to delete this line manually to make my solution working after regenerating my entity.

b.HasOne<AppUser>().WithMany().HasForeignKey(x => x.AppUserId);

Any plan/schedule to fix this issue from ABP Framework?

• ABP Framework version: v4.4
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:"

When I generate and entity with a navigation property required (as below). Units tests are not working anymore, I did investigate and it seems it is a bug from ABP when generate Unit tests. Data for the mandatory field are not provided.

To solve the issue I added manually this mandatory data on both files DataSeedContributor and ApplicationTests. ABP suite should fill this value when generate entity.

The error I made was to have missed the s on Layouts folder name, no worth a ticket...