Activities of "EngincanV"

Update: Thank you for scheduling the call. It is approved and will begin in 30 minutes.

I assume this was storing the localizations to redis. Disabling this will have some performance impacts elsewhere?

Hi, typically this should not impact anything in your application if you are not using distributed systems. This feature is introduced to provide a way to store localization entries in a database (a shared database) and use it in distributed systems in an efficient ways. So, if you are not building a distributed system, you can disable it without worry.

Is there any way to know what's going wrong inside of this module?

I'll review the code to identify the cause of this issue. The code is designed to run asynchronously and shouldn't block your application. I'll investigate why it's not behaving as expected.

Regards.

Hi again, sorry for the late response. (Since our support-bot closed the question, it became invisible in my dashboard)

I have checked the localization issue, here are answers to your questions:

Q: Note that, once running, the page title for angular is always "MyProjectName".

If you want to update the page-title then you can do it in the app-routing.module.ts file as below:

const routes: Routes = [
  {
    path: '',
    title: "Homepage title",
    pathMatch: 'full',
    loadChildren: () => import('./home/home.module').then(m => m.HomeModule),
  },
  //...
];

title property allows you to change the page title:

If you want to change the page-title in the application, you can do it in the relevant HTML file:

<abp-page [title]="'::YourLocalizedValue' | abpLocalization">
    //Your HTML code
</abp-page>

Q: Attempt to set "AppName" in the Angular localization. See that this has no effect as getLocalization() can not resolve a defaultSourceName and will not point to ::AppName

Yes, it seems there is a problem as you stated. After defining the localization:

It seems you should use it as ResourceName::AppName:

<abp-page [title]="'::YourLocalizedValue' | abpLocalization">
<div>
  <h1>
    {{ 'Issue8909::AppName' | abpLocalization }}
  </h1>
</div>
</abp-page>

I'll create an issue for that to fix it in our templates, but in the meantime, you can pass the resourceName for a workaround.

Q: Create a microservice template solution with MAUI and Localization. None of the text is localized.

Unable to reproduce this one. Localization seems working as expected.

This is really weird as you said. I'll ask our QA Team to test with Postgresql.

Hi, the related logs are written because of the ABP's External Localization System (https://github.com/abpframework/abp/pull/13845) and coming from the Language Management Module.

If it's not important for you, you can disable it by configuring the AbpExternalLocalizationOptions in your domain module:

Configure<AbpExternalLocalizationOptions>(options => 
{
    options.SaveToExternalStore = false; //true by default
});

Unfortunately I still get the 400 error

Can you share the logs of the auth-server project? (Especially, the error part please)

Hello, Any reply? I think you guys to see it from our code itself, it is blocking our iteration. Can we have a call or something?

Hi, sure. Can you please schedule a meeting from here (and please specify the ticket number)?

I added this code to webconfig in Blazoır and Auth server Project. ERR_BLOCKED_BY_RESPONSE error in iframe fixed. But when we login , we get 400 error.

<system.webServer> <httpProtocol> <customHeaders> <add name="Content-Security-Policy" value="frame-ancestors 'self' https://mydomain.sharepoint.com"/> <remove name="x-powered-by" /> </customHeaders> </httpProtocol> </system.webServer>

The 400 error you're encountering after adding the Content-Security-Policy with frame-ancestors suggests a conflict between your authentication flow and the restrictions imposed by the CSP. Try to expand frame-ancestors temporarily to see if it resolves the 400 error:

• Replace 'self' https://mydomain.sharepoint.com with 'self' * to allow framing from any origin.

<system.webServer>
	<httpProtocol>
		<customHeaders>
			<add name="Content-Security-Policy" value="frame-ancestors 'self' *"/>
			<remove name="x-powered-by" />
		</customHeaders>
	</httpProtocol>
</system.webServer>

If the error resolves then that confirms the original frame-ancestors policy was the cause.

Hi, can you confirm that the relevant users have not been soft-deleted?

Hi, you should follow a step-by-step approach to upgrade to .NET 8. Since you are upgrading from a really early version to v8.0, you should check the related migration guides one by one and update your solution version by version. Otherwise, you may have problems like this one.

For your question, there is an open ticket, which you can check at https://abp.io/support/questions/2916/An-exception-was-thrown-while-activating-VoloAbpIdentityServerGrantsPersistedGrantStore

Regards.