You can do this by adding the following code to the global.css file under wwwroot:
.lpx-header-top{
padding: 0 20em;
}
By the way, if you want, you can customize the MainHeader as follows:
Create the /Themes/LeptonX/Components/TopMenu/MainHeader/Default.cshml and update its content as follows:
@using Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX.Themes.LeptonX.Components.Common.MainHeaderBranding
@using Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX.Themes.LeptonX.Components.TopMenu.MainHeaderToolbar
@using Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX.Themes.LeptonX.Components.TopMenu.MainMenu
<header>
<div class="lpx-header-top ml-10 mr-10">
@await Component.InvokeAsync(typeof(MainHeaderBrandingViewComponent))
<nav class="lpx-nav me-auto">
<ul class="lpx-nav-menu">
@*TODO: Should we use a contributor for here?*@
@*
<li class="outer-menu-item" tabindex="0"><a class="lpx-menu-item-link lpx-menu-item " href="/">
<span class="lpx-menu-item-icon"><i class="lpx-icon bi bi-house-door-fill" aria-hidden="true"></i></span>
<span class="lpx-menu-item-text">Home</span>
</a>
</li>
<li class="outer-menu-item" tabindex="0"><a class="lpx-menu-item-link lpx-menu-item ">
<span class="lpx-menu-item-icon"><i class="lpx-icon bi bi-star-fill" aria-hidden="true"></i></span>
<span class="lpx-menu-item-text">Favorite Pages</span>
</a>
</li>
*@
</ul>
</nav>
@await Component.InvokeAsync(typeof(MainHeaderToolbarViewComponent))
</div>
<div class="lpx-header-bottom">
<nav class="lpx-nav">
<ul class="lpx-nav-menu">
@await Component.InvokeAsync(typeof(MainMenuViewComponent))
</ul>
</nav>
</div>
</header>
You can now update its content as you wish.
I have reviewed all the information you have sent and at this point we are sure that the problem is not caused by the modules. So we can only focus on the Host application, Blazor WebApp. As far as I understand from the last screen recording you sent, you can't do anything until the Web Assembly side is loaded and you encounter a lot of freezes. Can you create a solution with Blazor Web App UI from scratch in ABP Studio to find the source of the problem? Then we can proceed by comparing Blazor and Blazor.Client projects of this solution with your project. Because the problem does not appear in the startup template. I suspect that somehow the interactivity setting is wrong in the layouts etc. But we should compare the UI projects to be sure.
Super, great to see the problem solved. So, I will close this question and you can create a new question whenever you want.
Alright, you can reopen the question if you have a problem with this.
Great, now that the problem is solved, I'll close this question,
You can open a new question at any time.
Hello,
Try to delete node_modules folder and yarn.lock json file from Angular project.
Run command: yarn
and then try to run again
thanks
Somehow it cannot pull from Nuget. Can you run the following code and send the output to understand the problem:
nuget install Volo.Abp.Studio.Extensions.StandardSolutionTemplates -version 0.9.23
If you do not have nuget.exe installed, you can install it from this link.
Can you try the following code block?
if (AbpAspNetCoreComponentsWebOptions.Value.IsBlazorWebApp)
{
Navigation.NavigateTo(AuthenticationOptions.Value.LogoutUrl, forceLoad: true);
}
else
{
Navigation.NavigateToLogout(AuthenticationOptions.Value.LogoutUrl);
}
Hello again,
I intuitively had a few ideas after reviewing your code. Since I can't be completely sure, we will proceed with a little trial and error, sorry for that, but I think we will succeed as a result.
I see that you put the client application behind Nginx as below. Actually there is no need for that.
When I create a Blazor Wasm project from scratch, appsettings.json is mapped as follows:
Obviously this seemed like it could be a problem.
Also, could you try my suggestions regarding from-ingress and the custom middleware I mentioned in my previous message, not in Blazor but in the AuthServer application instead? I somehow suspect that the following code is not working.
if (!configuration.GetValue<bool>("AuthServer:RequireHttpsMetadata"))
{
Configure<OpenIddictServerAspNetCoreOptions>(options =>
{
options.DisableTransportSecurityRequirement = true;
});
Configure<ForwardedHeadersOptions>(options =>
{
options.ForwardedHeaders = ForwardedHeaders.XForwardedProto; // this line
});
}
context.Services.ForwardIdentityAuthenticationForBearer(OpenIddictValidationAspNetCoreDefaults.AuthenticationScheme);