Could this change be the reason for the issue?
Yes, this is likely the reason for this problem. I'll confirm that but, probably this is the reason.
Hi, thanks for reporting this problem. We have already fixed that problem and will release v9.1.3 with the fix (https://github.com/abpframework/abp/pull/22861).
I'm refunding your ticket, so please wait for v9.1.3 to upgrade the ABP Suite, which we will release probably tomorrow or in the next week (as soon as possible).
Regards.
I could not reproduce the problem that you are facing. I've replaced packages with source code for the AuditLogging UI module, and it is successfully added:
Probably there is an outdated .dll in your local machine, this causes the problem. Can you make a hard clean in your solution, and search for all .dlls and try again? Because, i'm unable to reproduce it right now. (I've directly installed your solution, and add it in ABP Suite and then make the source code replacement. If you have additional step, please let me know)
Regards.
Hi EngincanV, i've sent you an email 2 days ago
Sorry for the late response, I got your email, and I'll check and write back asap.
Hi, can you please provide more information? For example, you did not just updated the target framework and also updated the packages, right? Or did you override the role pages or its script etc.?
Hi, I'm unable to reproduce the problem. It successfully generated pages, and I could update my database.
Can you share the content of BaseCountryInfo.cs?
Hi, setting the .tpl files as embedded is not enough. You should also, ensure that your csproj file;
Microsoft.Extensions.FileProviders.Embedded NuGet package<GenerateEmbeddedFilesManifest>true</GenerateEmbeddedFilesManifest> into the <PropertyGroup>...</PropertyGroup> section of your .csproj file.Then, also check that the ConfigureServices method of your module has the following configuration:
Configure<AbpVirtualFileSystemOptions>(options =>
{
options.FileSets.AddEmbedded<UnionManagementModule>();
});
Regards.
Thank for you suggestion. So in option 1 do I need to configure post logout url which goes to OpenIddictApplications tables PostLogoutRedirectUris column? And do you talking about this where I need to configure redirect uri?https://github.com/abpframework/abp/blob/8.3.4/modules/account/src/Volo.Abp.Account.Web/Pages/Account/Logout.cshtml.cs So instead of setting my appplication logged-out path to post redirect logout uri I set auth servers /Account/Logout to same redirect path?
Yes, you're right. In option 1, you should redirect the user to the auth server's /Account/Logout endpoint with a returnUrl parameter that points back to your app.
This ensures the logout happens on the correct domain where the __tenant cookie is set, and then brings the user back to your application.
The return URL (https://application-test.ab.app/logged-out in this case) must be registered in the PostLogoutRedirectUris column of your OpenIddictApplications table — otherwise, the redirect won’t be accepted.
Hi, when you use pro modules, we are using the nuget.abp.io website and the URL structure is: https://nuget.abp.io/{{apikey}}/v3/index.json
By getting and downloading the .nupkg packages, you don't need to login through ABP CLI. The URL, is enough, you can even directly download it through URL.
You can find your apikey from https://abp.io/my-organizations and use it in NuGet.Config file.
Hi, when you define separate connection strings per module, you should either write a connection string for all of them or also define a "Default" connection string, so the other modules can use it:
So, you should either pass the "Default" connection string, so other modules can use it, or you can define the file-management module connection string by following the documentation (and also separate db for your file management module): https://abp.io/docs/latest/framework/fundamentals/connection-strings
Regards.
