Activities of "sumeyye.kurtulus"

Thank you for providing extra details. This problem is solved and related release will be available today. I can suggest you to upgrade to 9.1 until then. I am also refunding your ticket.

Hello, could you please share your package.json if your problem persists?

No, there will be no new item added since I suggested a patch for the parent route. If you can provide how you have implemented the solution, I can assist you further.

Hello, the new route will not be recognized by the navigation configuration if you did not add it to the routes. Because of this, the navigation bar item is not highlighted.

I can suggest you to patch the navigation item according to the navigated details page manually for the time being as explained here: https://abp.io/docs/latest/framework/ui/angular/modifying-the-menu#how-to-patch-or-remove-a-navigation-element

This will require further configuration based on your requirements, but here is a small workaround example:

import { RoutesService } from '@abp/ng.core';
import { Component, inject } from '@angular/core';

@Component({
  selector: 'app-root',
  template: `
    ...
  `,
})
export class AppComponent {
  private routesService = inject(RoutesService);
  constructor() {
    this.routesService.patch('::Menu:Dashboard', {
      path: '/dashboard/test',
    });
  }
}

import { NgModule } from '@angular/core';
import { RouterModule, Routes } from '@angular/router';
import { DashboardComponent } from './dashboard.component';
import { DashboardTestComponent } from '../dashboard-test/dashboard-test.component';

const routes: Routes = [
  {
    path: '',
    component: DashboardComponent,
    children: [{ path: 'test', component: DashboardTestComponent }],
  },
];

@NgModule({
  imports: [RouterModule.forChild(routes)],
  exports: [RouterModule],
})
export class DashboardRoutingModule {}

You're very welcome! I'm happy to assist and look forward to hearing how it goes. Please don't hesitate to reach out if you need any further support.

Yes, exactly. It depends on how you want to implement the override. You can use the component replacement along with the NavbarComponent which may be shorter and easier. You can also give a path reference in your tsconfig.json as in the screenshot.

Thank you for your clarification. You can use eThemeLeptonXComponents.Navbar key instead of Toolbar and Settings. If you override this component, you can also add your footer to the sidebar.

Can you perhaps just give me a direction to look for the sidebar or to customize this? I do not want to lose the sidebar which is pre-configured

If you do not want to override the whole navbar and create from scratch, you can check the NavbarComponent inside @volo/ngx-lepton-x.core package.

You can integrate the source code to your project by using this command abp add-package @volo/ngx-lepton-x.core --with-source-code.

Hello again, thank you for providing details. This is another problem which is going to be solved in the next release. You can use this style config to overcome this issue for the time being:

.lpx-header-bottom {
  overflow: inherit !important;
}

I am refunding your ticket. Thank you for your cooperation.

• You cannot technically move the footer to the sidebar for the time being. However, I can suggest you to add your custom footer to the Settings component key.

• This approach would serve the hide/show requirement of the sidebar as in here. If you think that this does not cover your case, I can assist further.

if (!this.authService.isAuthenticated) {
    this.replaceableComponents.add({
       component: YourNewToolbarComponent,
       key: eThemeLeptonXComponents.Toolbar,
    });
    this.replaceableComponents.add({
       component: YourNewSettingsComponent,
       key: eThemeLeptonXComponents.Settings,
    });
}

Hello again, I am refunding your ticket. Thank you for your cooperation.