Activities of "sumeyye.kurtulus"

Hello,

I could not produce the same problem on my end. Can you share the ABP version you have used to create your application along with the suite version?

If you prefer, you can send me a minimal reproducible example. Here is my e-mail address: sumeyye.kurtulus@volosoft.com

Thank you for your cooperation.

Hello,

I see that you are configuring your app to run as a standalone application. ABP will offer full support for this structure starting with the upcoming version 9.3, which will be released soon. You can follow the release updates here: https://github.com/abpframework/abp/releases.

If you are hesitant to upgrade to version 9.3 right away, you may consider using version 9.2, which provides more stability in this regard.

Feel free to reach out if you need any further assistance. Thank you for your cooperation.

Hello,

You should not need to pass these parameters

--target src/app/proxy (since it will already targetted here)
--project MYPROJECT3 (you already have one project registered in angular.json)
--all --force 

You can refer to these documents:

1. https://abp.io/docs/latest/cli#generate-proxy

2. https://abp.io/docs/latest/framework/ui/angular/service-proxies

This command would be enough abp generate-proxy -t ng -url https://localhost:44369

If you think that it does not solve your problem, I can assist you further.

Hello again,

Thank you for providing extra details on your problem.

If the approach I suggested above does not solve your problem, that would be the best if you could provide a minimal reproducible example so that I could assist you further. Here is my e-mail address: sumeyye.kurtulus@volosoft.com

I have also checked the version details, and the sidebar problem should not occur in this version.

Hello,

This problem has been solved in an internal issue and it will be released within the next release. You can follow the details here https://github.com/abpframework/abp/releases.

Thank you for your cooperation.

The problem you mentioned on the sidebar was solved in the previous version https://github.com/abpframework/abp/issues/22301. If you could provide the version for your @volosoft/abp.ng.theme.lepton-x package, I can assist further.

You can let me know if you need further assistance. Thank you for your cooperation.

Hello,

I can suggest you to override the default navigation to the manage profile page as I mentioned here previously https://abp.io/qa/questions/9674/3a1b61b3-1e0a-ab46-a3ae-8dd97adc6a0d

@NgModule({
  providers: [
    {
      provide: NAVIGATE_TO_MANAGE_PROFILE,
      useFactory: navigateToManageProfileFactory,
    },
  ],
})
export class AppModule {}

export function navigateToManageProfileFactory() {
  const windowService = inject(AbpWindowService);
  const routes = inject(RoutesService);

  return () => {
    const { path } = routes.find(item => item.name === eAccountRouteNames.ManageProfile);
    windowService.open(path, 'self');
  };
}

You will also need to update the patch in your component as follows

@Component({
  standalone: false,
  selector: 'app-root',
  template: `
    <abp-loader-bar></abp-loader-bar>
    <abp-dynamic-layout></abp-dynamic-layout>
    <abp-gdpr-cookie-consent></abp-gdpr-cookie-consent>
  `,
})
export class AppComponent implements OnInit {
  private userMenu = inject(UserMenuService);
  private configState = inject(ConfigStateService);

  ngOnInit(): void {
    this.configState.getOne$('currentUser').subscribe(currentUser => {
      if (currentUser?.isAuthenticated) {
        // Patch MyAccount action
        // ⚠️ remove this part and just use the new provider override here
        // this.userMenu.patchItem(eUserMenuItems.MyAccount, {
        //   action: () => {
        //     const { path } = this.routes.find(item => item.name === 'AbpAccount::ManageProfile');
        //     this.router.navigateByUrl(path);
        //   },
        // });

        // Remove unwanted items
        [
          eUserMenuItems.LinkedAccounts,
          eUserMenuItems.AuthorityDelegation,
          eUserMenuItems.ExternalLogins,
          eUserMenuItems.SecurityLogs,
          eUserMenuItems.Sessions,
        ].forEach(item => this.userMenu.removeItem(item));
      }
    });
  }
}

Another issue I'm seeing is that the main menu is not collapsing when I select a different menu item, and the scroll bar is gone, If I expand some items I lose visibility and can't scroll down.

The problem you mentioned on the sidebar was solved in the previous version https://github.com/abpframework/abp/issues/22301 If you could provide the version for your @volosoft/abp.ng.theme.lepton-x package, I can assist further.

You can let me know if you need further assistance. Thank you for your cooperation.

Hello idle session timeout feature is designed to be on the admin configuration. So, it is available for AccountAdminConfigModule rather than AccountPublicConfigModule.

Hello, We have identified the same issue on our end. It will be resolved in the next patch release, which you can follow here: https://github.com/abpframework/abp/releases.

Thank you for bringing this to our attention. I have also issued a refund for your ticket.

Hello, This decision was taken for design purposes previously. However, you can override this behavior by adding these providers to your app.module.ts

@NgModule({
  providers: [
		 // ...
    {
      provide: NAVIGATE_TO_MY_SESSIONS,
      useFactory: navigateToSessionsFactory,
      deps: [Injector],
    },
    {
      provide: NAVIGATE_TO_MANAGE_PROFILE,
      useFactory: navigateToManageProfileFactory,
    },
    {
      provide: NAVIGATE_TO_MY_SECURITY_LOGS,
      useFactory: navigateToMySecurityLogsFactory,
    },
  ],
})
export class AppModule {}

The relative factories should be added as follows:

import { AbpWindowService, RoutesService } from '@abp/ng.core';
import { inject } from '@angular/core';
import { eAccountRouteNames } from '@volo/abp.ng.account/public/config';

export function navigateToManageProfileFactory() {
  const windowService = inject(AbpWindowService);
  const routes = inject(RoutesService);

  return () => {
    const { path } = routes.find(item => item.name === eAccountRouteNames.ManageProfile);
    windowService.open(path, 'self');
  };
}

export function navigateToMySecurityLogsFactory() {
  const windowService = inject(AbpWindowService);
  const routes = inject(RoutesService);

  return () => {
    const { path } = routes.find(item => item.name === eAccountRouteNames.MySecurityLogs);
    windowService.open(path);
  };
}

export function navigateToSessionsFactory() {
  const windowService = inject(AbpWindowService);
  const routes = inject(RoutesService);

  return () => {
    const { path } = routes.find(item => item.name === eAccountRouteNames.Sessions);
    windowService.open(path);
  };
}

You can let us know if you need further assistance. Thank you for your cooperation.