Activities of "armanozak"

Hi,

Yes, this request does not have a body. The request looks fine, this is not about Angular app. Please check your server logs to find the error.

Also second Request header says 204 No Content.

I did not understand that. Is there a second request which does not get en error? Because, 204 is the correct status code this request gets as response from the server. In other words, the response should be 204 instead of 500.

Hi,

It looks like a server error. Can you also send the request body please?

Thanks.

Hi,

Could you please share the request and response of the Http request with the error? You may find them in the Network pane of developer tools.

Thanks.

Ok, I am closing this one then.

Hi,

You can replace the account login logo too.

1. Create a second logo component.

import { Component } from '@angular/core';

@Component({
  template: `
    <div class="account-brand p-4 text-center mb-1">
      <a class="navbar-brand" routerLink="/" [style.background-image]="logoUrl"></a>
    </div>
  `,
})
export class LogoComponent {
  logoUrl = 'url(http://satyr.io/100x50/acdc?text=LOGO)';
}

2. Dispatch AddReplaceableComponent action.

this.store.dispatch(
  new AddReplaceableComponent({
    component: LogoComponent,
    key: eAccountComponents.Logo,
  }),
);

We will discuss your idea of moving the default background style for the default logos to an additional class. We are currently making a few changes about the logos. Therefore, it may or may not make sense. We will see, but thanks for the idea. Much appreciated.

Hi,

Has this isue been solved? Can we close it please?

Hi @talhazengin,

Has this issue been solved?

Hi,

There is an Angular module startup template.

abp new Acme.BookStore -t module-pro -u angular

However, I recommend waiting a few days for ABP v3.0 release, since we made important changes.

Please let me know if this answers your question.

Have a nice day.

Hi,

I cannot reproduce this. Please check the attached animated GIF on what I see when I use the exact code above.

Hi,

There is no way of persisting Lepton settings per module. If a menu on top in a specific module for all users is what you need, then you can use OnInit and OnDestroy lifecycle hooks in the root component of that specific module. An example:

@Component({
  selector: 'app-dashboard',
  templateUrl: './dashboard.component.html',
})
export class DashboardComponent {
  private menuPlacement: number;

  constructor(private layout: LayoutStateService) {}

  ngOnInit() {
    this.menuPlacement = this.layout.getMenuPlacement();
    this.layout.dispatchSetMenuPlacement(1);
  }

  ngOnDestroy() {
    this.layout.dispatchSetMenuPlacement(this.menuPlacement);
  }
}

Does this solve the issue for you?