Käyttäjän "uyarbtrlp" toiminnot

• ABP Framework version: v8.1.3
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Module project (Separated Deployment & Databases Scenario): yes

Hello,

I have an aggregate root - value object relationship on my module. As you can see there are profile aggregate root and edge definition value object Relationship has been described in EFCore like this. I use owns many relationship between Profile and EdgeDefinition. I have a method that creates multiple profiles according to input that is sent in ProfileAppService. When I create two profiles, two entitites, I see that only one edge information on my local db and it is assigned to latest profile. So I examine the EF core logs it seems that InsertMany create a single edge definition and updates the FK with the latest one. It is a really strange behavior because I expect that it should create single value object for each profile. To give an example. I sent two ids for profile and it creates two profiles, but I can only see the latest one on edge definition table. Since it is a long log file I could not send it. But you can see that it changes the ProfileId value while inserting it. 2024-06-05 12:03:44.113 +03:00 [DBG] The foreign key property 'EdgeDefinition.ProfileId' was detected as changed from '"dd9c0686-7486-c122-0940-3a12f9cb4247"' to '"273b1940-0173-8d1d-3bc0-3a12f9d07589"' for entity with key '{Id: 372}'. I just want to see that if it works InsertAsync method with autosave but there is same issue. It seems it could not save the transaction. The only thing works when we create a new unit of work. It basically creates edge definition for each profile. It seems it is a really strange problem even though we want to save it with autosave. I just want to use InsertMany method but it does not work. Do you have any idea why it happens?

Okay, it works. Thank you

I've sent it

• ABP Framework version: v8.1.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC): yes

Hi all,

We've followed your documentation when we integrated it in our module. We use the FileSystem option. After upgrading the solution 7.3 to 8.1, we have an exception on docs module. So we've created application template solution from scratch to see whether we have the same case.

1. Create a solution on abp suite
2. Installing docs module packages and adding the dependencies on each layer (both web and admin packages)
3. Insert the documentation on SQL INSERT [dbo].[DocsProjects] ([Id], [Name], [ShortName], [Format], [DefaultDocumentName], [NavigationDocumentName], [MinimumVersion], [DocumentStoreType], [ExtraProperties], [MainWebsiteUrl], [LatestVersionBranchName], [ParametersDocumentName], [ConcurrencyStamp]) VALUES (N'12321123-e08e-4f15-bedb-ae0b2d939659', N'ABP framework (FileSystem)', N'abp', N'md', N'Index', N'docs-nav.json', NULL, N'FileSystem', N'{"Path":"C:\\Github\\abp\\docs"}', N'/', NULL, N'', N'2f836e13a2084c3fb720a4d586a11f9a')
4. Navigate the https://localhost/Documents
5. Get the exception
6. I am able to see admin pages. There are no issues.

How to solve that issue on v8.1.1?

It appears that it is a problem with the newest version. We haven't experienced such an issue so far. Btw, I've tried the code above and it works. If I understand correctly, we MUST enable the redis with tiered applications after v8.0, right?

I am running AuthServer, HttpApi.Host and Web.Host

I've sent it

• ABP Framework version: v8.1.1
• UI Type: MVC
• Database System: EF Core
• Module project (Separated Deployment & Databases Scenario): yes

Hello, After we upgraded ABP v8.1.1, we got "Tenant not found! There is no tenant with the tenant id or name: a3e378cf-c315-7b7e-da30-3a12881a6c2a" exception while trying to login the application via Web.Host project. We've been using the application without redis so we've disabled it.

  "Redis": {
    "IsEnabled": "false",
    "Configuration": "127.0.0.1"
  },

When we enable the redis, there is no problem. We are able to login. So I've decided creating a new module project on abp suite to test the same thing.

1. Create a module project on abp suite
2. Update the databases to create the tables
3. Disable the redis on appsettings.json
4. I've changed the TestApplicationNet8SampleIdentityDataSeeder on AuthServer project to seed the users when the tenant is created
5. 
6. Create a tenant
7. Login with this tenant and get the exception

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello, We want to change "entityTypeFullName" property on entity changes in audit logging module. I assume that it is retrieved from the namespace. We don't want to change the namespace for that. How we are going to change this value while adding the record?

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello all, We want to send an email confirmation token from Angular app and we want to use MVC keyword(AuthServer confirmation page) for that (not separate Angular UI). Before that, I've wanted to try it on HttpApi.Host. We've added Volo.Abp.Account.Pro.Public.HttpApi dependency in HttpApi module. I am able to see the endpoints on swagger UI After that, when we call the send-email-confirmation-token from the HttpApi.Host, I see that there is empty url in the email. To achieve that problem, I've added the AbpUrlOptions to HttpApi.Host module to set the RoorUrl for "MVC" keyword and give the AuthServer url since email confirmation page is here. Swagger authority is set as AuthServer url. When I try it on my local, everything works fine but it does not work for the docker containers. I get the error invalid token even though the link is correct.

How can I solve that problem?