The same problem occurs when deleting the database and creating a migration again. Is there a solution for this abp version (v4)?
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?
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,
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
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
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
All permissions are active when the DbMigrator project is running
Purging cache after deletion a tenant was shipped in v5.2.1.
Hi, I am using abp version 5.2.2 and the error still persists. I am writing steps how to reproduce the error.
Can it be fixed with the first update?
hi
Please custom the
MultiTenancyMiddlewareErrorPageBuilder
ofAbpAspNetCoreMultiTenancyOptions
to delete the cookies.https://github.com/abpframework/abp/pull/13157
Hello, will this development be in the next first version?
It will be available in 6.0. but you can change it by yourself now.
We have overwritten the modified code in the module file. It changes tenant information on the cookie but redirects to "tenant not found" exception page. It should redirect to main login page without any errors.