Activities of "enisn"

No, there is no Footer.razor file in a new Blazor Server 7.0.0 project.

You create a footer file in your application with the codes that I shared above

On the bottom menu, it doesn't scroll from left to right.

If you add the following CSS into your application you will be able to scroll left to right

.lpx-mobile-navbar {
    width: 100%;
}
.lpx-mobile-nav-tab {
    min-width: 72px;    
    width: auto;
}
.lpx-mobile-nav-tabs {
    width: 100%;
    overflow-x: scroll;
    justify-content: start;
}

It seems your style css isn't loaded. Did you override any logic about bundling or styles of LeptonX?

This way you will not know which account to look at?

You will see payment request was done, but you check your stripe account and there are no funds. How do i know which payment gateway this payment was used to make? Where is this data stored?

This is a custom logic. ABP Payment Module doesn't provide a tenant-based payment option as I said before. Since this is a custom approach, you have to keep that data by your own

Hi

Since we don't know anything about your environment, I can't say something clearly. But it seems it's related to your deployment scenario.

I can only suggest this method in microsoft's document: https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-7.0#when-it-isnt-possible-to-add-forwarded-headers-and-all-requests-are-secure

Also the following article may make easy to understand the situation that you faced: https://codeopinion.com/configuring-asp-net-core-behind-a-load-balancer/

It is good that now the project logo-dark and logo-light images a now accessible - but why not the login-bg image?

You're right, we'll take an action for it and we'll make it easy to customize.

In V7.0.0 there is a new footer component Where is this exposed so it can be customized?

If you create a new project, you'll see there is a file named Footer.razor in your project. But if you migrated from older versions, you need to add that file on your own.

@using Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.TopMenu
@using Volo.Abp.DependencyInjection

@inherits Footer

@attribute [ExposeServices(typeof(Footer))]
@attribute [Dependency(ReplaceServices = true)]

<div class="lpx-footbar-container">
    <div class="lpx-footbar">
        <div class="lpx-footbar-copyright">
            <span>@DateTime.UtcNow.Year©</span>
            <a href="https://leptontheme.com/" target="_blank">Lepton Theme</a>
            <span>by</span>
            <a href="https://volosoft.com/" target="_blank">Volosoft</a>
        </div>
        <div class="lpx-footbar-solo-links">
            <a href="#">About</a>
            <a href="#">Privacy</a>
            <a href="#">Contact</a>
        </div>
    </div>
</div>

In the account layout, it uses MVC layout and you should place Themes/LeptonX/Layouts/Account/_Footer.cshtml file in your application to override footer in Account layout. (Login page)

<div class="text-center pt-2">
    <span class="copyright-text">@DateTime.Now.Year © LeptonTheme by <a href="http://www.volosoft.com" target="_blank">Volosoft</a></span>
</div>

In the latest version of LeptonX MVC package, Only favicon.ico and favicon.svg exists. If you're using v2.0 or later, you should use those files.

Thanks for your reply,

I do not understand this:

But you can remove the first one and add latest one and manage the first one manually.

As I understand you already have that line in the database and can't add a second registry for the same gateway. I mean just add only one that you want to be managed by ABP Payment module, and manage rest of them manually without adding to db

Hi joe@tronactive.com

You marked as you're using blazor with a tiered solution. So, you have 3 different projects whiches are *.Blazor, *.HttpApi.Host and *.AuthServer.

All of them stands for a reason but users can only interact with Blazor and HttpApi.Host project. So, you can update package.json file in those project folders.

By the way, please don't add direct reference to those files, just use resolution parameter of package.json

If you don't have an idea for it, here is an easy usage: https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/#toc-how-to-use-it

Currently, it's not possible because of the design of the module. But you can remove the first one and add latest one and manage the first one manually.

We'll think on this scenario and consider to change the design of Gateway Plans.