Käyttäjän "mert.kir" toiminnot

All permissions are active when the DbMigrator project is running

• ABP Framework version: v5.2.2
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Steps to reproduce the issue:

1. Login to the application with one tenant.
2. Go to Administration => Identity Management => Roles page.
3. Some of the permissions of the admin role are removed.
4. Then the DbMigrator project is run.
5. When the permissions are looked again after the project is run, it is seen that all permissions are active.

With the DbMigrator project running, the permissions should remain as they are instead of being active again. How can I solve this problem?

Solution has been merged and will be shipped in v5.2.1 very soon

thanks, is there this improvement in current version 5.2.1? I'm asking because I can't see it in the changelog

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

Hello, I am getting the following error when I inject IGuidGenaretor parameter to the constructor method of the AutoMapperProfile file in the Application layer. how can i solve this problem

Hello,

If you can download the source code, you can implement your fix until you upgrade your packages.

In organization-units.component.ts, after deleting a unit, you need to check if it is the selected unit.

Change

// ... 
.subscribe((status: Confirmation.Status) => { 
        if (status === Confirmation.Status.confirm) { 
          this.service.delete(id).subscribe(() => this.get()); 

to

// ... 
.subscribe((status: Confirmation.Status) => { 
        if (status === Confirmation.Status.confirm) { 
          this.service 
            .delete(id) 
            .pipe( 
              tap(_ => { 
                if (id === this.selectedUnit?.id) { 
                  this.selectedUnit = null; 
                } 
              }), 
            ) 
            .subscribe(() => this.get()); 
        } 
      }); 
 

thanks for the reply

It would be better to write information for those who have this problem under abp 5.0 version. Because after the statement that we will solve the problem, there was no information.

Hello, the question was asked in the support ticket number 2235. However, no information has been given that it has been resolved. Any information on when it will be resolved?

• ABP Framework version: v4.4.3
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: Tenant not found! There is no tenant with the tenant id or name: 00bbbd7e-953d-7c7d-3842-3a01cc9219ec
• Steps to reproduce the issue:" -Login as host and delete one tenant. -When you exit the application, the _tenant value in the cookie is deleted, but since the deleted tenant information is included in the redis, the _tenant information in the cookie takes the id of the deleted tenant. Deleted tenant information should also be deleted from Redis. -Thus, api/abp/application-configuration 500 error code returns. -In order to open the page, the _tenant and .AspNetCore.Identity in the cache, abpsession information in the LocalStorage must be deleted. -Doing it like this is a workaround solution.

The same problem occurs when deleting the database and creating a migration again. Is there a solution for this abp version (v4)?