Hi all clients in this question, about the npm install problem, Have you tried with yarn install command this behavior ?

Hi,

There is no problem when using yarn. The problem is related to npm.

Thank you for your patience, and I apologize for the delayed response. This problem has been fixed and will be available for the next version. May I know whether you get the same error even if you use the --legacy-peer-deps option?

Hi,

I also get an error when I try with --legacy-peer-deps

Hi again, İ've checked milestones yet we don't have any milestone for 8.3-patch. It seems like the nearest milestone 9.0-patch I'll discuss with team. Yes I'll fixed separately

Hi Masum,

Although the Localization Problem is not resolved, the ticket seems to be closed. Due to company policy, we cannot upgrade to Abp 9. How can we solve these problems in 8.3.4? Can you share the workarounds?

Hi again, I've created internal issue for your problems.

thanks, will it be fixed in version 8.3.5?

Also, has the Arabic problem been fixed or will it be solved separately?

Hello ,

We have created an internal PR, you can follow latest pro releases at here: https://abp.io/pro-releases All problem will be sovled in 8.3.4 Your can write query here https://abp.io/support/questions/8214

Thank you.

Hello,

You said that the problem was solved in version v8.3.4 but the problem still persists

Hi again, no I haven't seen this problem. I'll try to check it

Hi Masum,

I have another issue related to the bugs I previously reported.

When the interface language is set to Arabic, the NavItemsComponent gets misaligned and appears in the center. (There is a similar problem in the footer. It is visible in the screenshots) Additionally, when clicking on the profile picture to open the dropdown, only half of the user picture is visible.

After switching the language back to English, the NavItemsComponent remains in the center until the page is refreshed, at which point it aligns correctly to the right.

Could you please take a look into this issue as well?

Hi again,

Setting Tab

• You don't need to localize setting tab name by your own, just provide localization key to name property like below. In the setting-management component it'll localized

Refresh Token Problem

I'll check it and open issue.

Hi Masum,

Will the issue in the link be resolved in version 8.3.4? I'm asking just to confirm. Thank you!

https://abp.io/support/questions/8283

Hello

I'll check this , Please Question gathered to here https://abp.io/support/questions/8214

Thank you.

Is there any update this issue?

Hi Masum,

I have a new bug. I explain below how to reproduce it. I am also using Lepton Theme

• Add the code below to app.component and create a sample component named MyAppCustomSettingsComponent (content is not relevant).

export class AppComponent {
  constructor(
    private settingTabs: SettingTabsService,
    private localizationService: LocalizationService
  ) {
    this.settingTabs.add([
      {
        name: this.localizationService.instant('::MyAppCustomSettings'),
        order: 1,
        component: MyAppCustomSettingsComponent,
      },
    ]);
  }
}

• In the backend, add "MyAppCustomSettings" localization keys to both English and Turkish localization files. Example: English: "MyApp Custom Settings" Turkish: "MyApp Özel Ayarları"
• Start the project and open the Administration -> Settings page in English. Then, change the page language to Turkish from the top-right.
• Observe the setting names: the custom setting title remains in English, while the other settings appear in Turkish. After refreshing the page, all settings correctly display in Turkish.

Expected Result: All setting titles, including custom settings, should update to the selected language immediately upon changing the language. Actual Result: After changing the language, the custom setting title remains in English, while the rest of the settings display in Turkish. Only after refreshing the page do all settings appear in the correct language.

Hi again, I've gathered all questions here.

I've created an internal PR, you can follow latest pro releases at here: https://abp.io/pro-releases

All problem will be sovled in 8.3.4

Theme Initialization

Theme initialization is about the ThemeLeptonModule class, normally in this class forRoot method needs to fix this problem yet we moved this method's logic to provideThemeLepton function and used in forRoot method because of angular changing strategy to functional an provider way. I couldn't understand why not working this behavior without using function manually

When I provide this function in app.module's providers section the problem is solving yet you still needs to import ThemeLeptonModule without forRootmethod. Also I exposed provideThemeLepton function in 8.3.4 you need to wait for release for this problem :')

Mobile navbar

This problem fixed in theme-lepton package in 8.3.4 don't need to do anything just wait for 8.3.4 version release

OpenIddict application edit modal

Enabled property is useless there is not any releated prop at server side that's why I've removed.

hi, masum

I will check when the new release 8.3.4

There were bugs reported by the test team. I was creating new tickets for each of them, but it might be better to combine them here.

Below is the link to the bug I initially reported. I will add any new issues as comments. Thank you! https://abp.io/support/questions/8283